/explore
|
You are here 
|
slack.engineering | ||
| | | | |
nindalf.com
|
|
| | | | | I share my experience and lessons learned from a recent tech job search, including tips on preparing for interviews and negotiating job offers. | |
| | | | |
programmingzen.com
|
|
| | | | | Why I ask basic questions. Discover a less stressful tech interview process that effectively identifies talented candidates. | |
| | | | |
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. | |
| | | | |
davidalfonso.es
|
|
| | | [AI summary] A review of an open source guide for aspiring software engineers covering project management and career development. | ||
