/explore
|
You are here 
|
danielabaron.me | ||
| | | | |
yolken.net
|
|
| | | | | Having switched jobs a few times over the last few years, I've done a a lot of software engineering interviews. In my most recent job search, for instance, I did around eight phone screens followed by six on-sites. | |
| | | | |
simpleprogrammer.com
|
|
| | | | | Software Engineers do the complex work so that we can enjoy efficient software solutions. They're creating the systems behind the digital tools we use at work or in our personal life. This takes strong logical thinking and problem-solving skills, as well as a deep knowledge of computer science and programming. It's a challenging, but exciting [...] | |
| | | | |
www.danhacks.com
|
|
| | | | | [AI summary] A comprehensive guide listing resources and techniques to help software engineers prepare for coding interviews, covering data structures, algorithms, and practical practice tools. | |
| | | | |
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... | ||
