/explore
|
You are here 
|
www.ryngonzalez.com | ||
| | | | |
iferminm.gitlab.io
More than writing code |
|
| | | | | ||
| | | | |
seanvoisen.com
A growing collection of articles, books, blog posts and other resources about design engineering. |
|
| | | | | ||
| | | | |
craigjamieson.com
|
|
| | | | | ||
| | | | |
adamsitnik.com
Interviewing people is not an easy job to do. You want to find the person which is going to get things done, enjoy working with given project, fit into the team and be happy about the money you can offer. As an interviewer, you are also being judged by the candidate. You very often create the first impression of the company. So you also need to make a good impression. Nobody wants to work with mean or incompetent people! In this blog post, I am describing my way of conducting the interview. In my career, I have interviewed a hundred developers and hired over a dozen of them. So my experience is not very reach, it's limited to "my sample". Disclaimer: After joining Microsoft I don't interview candidates anymore. This post is my personal approach build upon th... |
|
| | | |||
