Explore >> Select a destination
|
You are here 
|
www.hillelwayne.com | ||
| | | | |
yolken.net
|
|
| | | | | Having switched jobs a few times over the last few years, I've done a a lot of software engineering interviews. In my most recent job search, for instance, I did around eight phone screens followed by six on-sites. | |
| | | | |
code.dblock.org
|
|
| | | | | When I joined Microsoft in '99 I was taught how to properly interview candidates. I was shown the wheel of competencies, a kind of a wheel of fortune where a color represents the candidate's technical skill, ability to solve complicated problems or to communicate with their peers. Each slice included broad interviewing suggestions, which often gave birth to elaborate puzzles. What could possibly be the best way to figure out whether the candidate is capable of thinking out of the box? Ask them why the potholes are round. Can they crank complex working code on a deadline? Ask them to implement a memory allocator in 30 minutes or less in C. | |
| | | | |
better.engineering
|
|
| | | | | Our approach to hiring and training software engineering intern | |
| | | | |
fluffyandflakey.blog
|
|
| | | Three days ago I gave a presentation on React.js at the TucsonJS meetup. The goal was to provide a high-level overview of whatReact is talk about why someone ought to be interested in applying it. At the end of the talk I gave a live coding demonstration where we iterated a design for a blogging... | ||
