The book “Cracking the Coding Interview” helps you to survive the famous ‘technical interview’. Major tech companies like Google, Amazon etc. use these types of interviews to figure out if you can program.
Overall even with the book your chances are slim of passing the interview. - In any case most of the questions are the usual university preparation questions for the most broadest subjects in the field of computer science. So a lot of theoretical stuff and low-level programming skills. - The questions are in a way stupid - but what do you expect? they are questions that an HR person can ask you that have no merit or value in your day to day work.
Basically prepare yourself for this:
The book however is a really good starting point And it is nice that for every topic there is a short introduction about what is important and how to approch questions from that topic.
The HR person will look for four things:
- Analytical Skills
- Coding Skills
- Technical Knowledge
- Culture Fit / Communication
“Prior experience” - is not needed, you put that already on your CV.
Of course the entire process is riddled with tons of mistakes and false negatives - simply because the process does not figure out if you can actually do the job. However the few people that survive the process - are probably candidates you can position anywhere in your large corporation.
Whiteboards are used to focus on ‘what is really important’ - translation: it is easier and quicker to set up an whiteboard than an actual IDE. Get ready to get maybe judged for making minor typos even though ‘the interviewer does not care’ - subconsciously he is judging you.
Before the Interview
Get the right experience
- Try to take classes with big programming projects
- Internships: Try to get some work experience
- Build something in your spare time (=> Github)
Write a great resume
Keep your resume to 1-2 pages, HR People spend very little time reading it. But it needs to be perfect so they dont throw it out due to small things.
Write strong bullet points
Use the formula: “Accomplished X by implementing Y which led to Z”
Leave out stuff
You are applying for a programming job, you probably know how to use Office etc. be conservative which programs you list Same is true for all the programming languages, list those that are relevant and are widely used.
Be aware of the stigmas that are associated with languages. Some languages like Visual Basic while they are used and even if you know the language on an expert level it is mostly seen as that you have less experience than a language like Java/Python etc.
Certifications - Usually a waste of paper and most people do not see it as relevant. (in the field of computer science)
Prepare your past projects ask yourself for each project
- What where the Challenges?
- What went wrong?
- What did you enjoy?
- Who lead the project? Did you lead the project?
- How did you resolve conflicts?
- What would you do differently?
During this phase of the interview try to create a dialog about how your new employer deals with certain issues. You need to interview the company if the company would fit to you or not.
Focus on you not your project, however you still need to show that you can work well with others.
When you are talking about your past projects you should use the SAR principle
Ensure that during your stories you can show
And of course sprinkle in shows how you succeeded.
Well you need to get the book for all the questions, but about 90% of the book are questions on various topics with well written answers.
The book is really useful when you are applying for big US-Tech companies. However for German-Tech companies the advice in the book is rather limited as they do not use the ‘technical-interview’ in the hiring process. (It produces too many false negatives and developers are rare)
It only helps you if you are attempting to pass the “technical-interview” and you basically need about 1 year of training prior to your actual interview to pass the interview. Basically the ‘technical-interview’ is a skill only needed to get into a couple of companies.
If that is not your goal your time is much better spent contributing to open source and creating your own projects as you will learn more ‘day-to-day’-skills.
Despite all of that it is a very interesting overview of questions you may encounter in an interview. Get the book at Amazon