|
You are here |
freakingrectangle.wordpress.com | ||
| | | | |
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. | |
| | | | |
loudwhisper.me
|
|
| | | | | [AI summary] The author recounts their experience of failing a coding test during a job interview for a Platform Security Engineer position, criticizing the process for being irrelevant to their role and highlighting issues with the tech recruitment system. | |
| | | | |
henrikwarne.com
|
|
| | | | | For the past few months, I have been interviewing with several companies. In all cases, one or more coding tests were included. I have also been on the interviewing side, evaluating a coding test. Here are my thoughts on the process. Are coding tests needed? When I started out as a software developer, nobody did... | |
| | | | |
astrid.tech
|
|
| | | [AI summary] A blog post detailing the author's experience applying for and securing a Production Engineering internship at Facebook, covering the interview process, challenges faced, and insights gained. | ||