/explore
|
You are here 
|
preemchro.me | ||
| | | | |
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. | |
| | | | |
blog.goodstuff.im
|
|
| | | | | [AI summary] The author critiques whiteboard coding interviews in tech, arguing they are ineffective for assessing real-world coding skills and team collaboration, and suggests alternative methods like the 'Lunch Problem' technique for better candidate evaluation. | |
| | | | |
www.susanjfowler.com
|
|
| | | | | In today's post, I want to share some of the things I've learned about how to structure and run these types of interviews. If you're here because you want to know how to ace the architecture interview, you should keep reading, because I think the best ways to prepare for these things is know how interviewers think about them. | |
| | | | |
www.techradar.com
|
|
| | | Democratizing software development through AI-driven vibe coding | ||
