Explore >> Select a destination
|
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. | |
| | | | |
programmingzen.com
|
|
| | | | | Why I ask basic questions. Discover a less stressful tech interview process that effectively identifies talented candidates. | |
| | | | |
blog.janestreet.com
|
|
| | | | | We're busy preparing for our software engineering fall hiringseason. Over the years we'vedone our best to make our interview process more transparent tocandi... | |
| | | | |
www.altexsoft.com
|
|
| | | A dive into the machine learning pipeline on the production stage: the description of architecture, tools, and general flow of the model deployment. | ||
