I can recommend this book as it is the one I used when I was preparing for my first coding interview.It was an interview for a software internship job and I was so excited to get the job.It took me over a fortnight to get through most of the problems and solutions, but it was worth it.I did the interviews and I appreciate that even the time I spent studying this book.One thing to mention here, this book provides solutions in Java.It is not difficult to translate the cracking the coding interview: 189 programming questions and solutions 6th edition solutions into the language of your choice, even if you are not a Java expert.LeetCode
is an online resource that contains tons of coded interview questions and solutions.
I encourage you to visit their website and check out their problems to get a general idea of what they are like.
Another cool thing about Leetcode is that you can integrate your solutions into almost any popular programming language.
Leetcode will run your code against a set of inputs and notify you if it passes all test cases or not.
It will also let you know if your code is taking longer to run than expected (indicating that your code could be further optimized).
Leetcode also has a forum where like-minded people discuss problems and solutions for each of the site's problems.
You can try many questions for free on the site, but your premium subscription is $ 35 per month.
While I haven't personally used their premium service, I often use their free service to keep my coding skills sharp.These are the resources I would recommend.Now I want to give you an idea of what the interview process is like.What are the steps to take to receive your offer letter?Third: Telephone interviewsThis is the first round of interviews you will have to go through.
Your recruiter will contact you and schedule a time for some response telephone interviews.
The purpose of these interviews is to check on bad candidates early in the process.
This is why interviews are sometimes referred to as "Phone Screen".
Each telephone interview usually lasts between 45 minutes and an hour.
What to Expect at Your Telephone Interviews
What usually happens is that your interviewer will call you on the phone and ask you some questions about programming.
You can solve these problems in a shared document that you and your interviewer can view and edit.
It is crucial to know in advance that you are going to write your code in a generic word editor, not an IDE.
No syntax highlighting, no automatic finishing, no fancy features out there.
How to prepare for your telephone interviews
These types of questions will not be different from the ones we have already discussed.
But because the purpose of these interviews is to check on poor candidates in a limited amount of time, expect your interviewer to jump right into question coding.
There is no time for a long resume or behavior problems.
Steve Yegge wrote an excellent article on what to expect from potential candidates during his phone interviews.
some tips to help you.
• Find a quiet place and get headphones. You need a quiet place so that you can give the interviewer and the questions your full attention. Believe me, a small alteration can negatively affect its performance. You also need headphones, as both hands will be busy writing code. Don't trust your speakers!
• Practice writing code in normal text editors (not IDE). You will be surprised how many programmers rely heavily on IDEs to write synthetically correct code.
• Think out loud. This is crucial! I understand that you probably don't speak in real life when you're thinking, but for phone interviews, this is the only way your interviewer can judge your thought process.
• Ask clarifying questions. Sometimes your interviewer will give you an incomplete problem to see if you can ask for clarification problems. Always ask questions if something is unclear or missing. If you are going to make assumptions