/explore
|
You are here 
|
blog.colinbreck.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... |
|
| | | | | ||
| | | | |
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... |
|
| | | | | ||
| | | | |
xdg.me
A story of how I tried to reinvent the interview process. Highlights: humane take-homes; developing good coding questions; a guide for interviewers. |
|
| | | | | ||
| | | | |
www.rastergrid.com
[AI summary] The article discusses how GPUs leverage the SIMD paradigm to achieve high computational throughput and efficiency, exploring programming model implications. |
|
| | | |||
