Explore >> Select a destination
|
You are here 
|
alexgolec.dev | ||
| | | | |
interviewing.io
|
|
| | | | | Why are people so bad at gauging their own interviewing performance? We investigated and dig into the data to see what we can learn. | |
| | | | |
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. | |
| | | | |
cassidoo.co
|
|
| | | | | Interviews are scary, but they don't have to be. When you're on the spot, it's best to be prepared. Let's prepare you. | |
| | | | |
alexeymk.com
|
|
| | | The new VP wants us to double engineering's headcount in the next six months. If we have a chance in hell to hit the hiring target, you seriously need to reconsider how fussy you've become. | ||
