/explore
|
You are here 
|
slack.engineering | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
www.elidedbranches.com
Technology, startups, programming, technical management and software architecture |
|
| | | | | ||
| | | | |
programmingzen.com
Why I ask basic questions. Discover a less stressful tech interview process that effectively identifies talented candidates. |
|
| | | | | ||
| | | | |
simpleprogrammer.com
Software Engineers do the complex work so that we can enjoy efficient software solutions. They're creating the systems behind the digital tools we use at work or in our personal life. This takes strong logical thinking and problem-solving skills, as well as a deep knowledge of computer science and programming. It's a challenging, but exciting [...] |
|
| | | |||
