How to use cracking the coding interview

How to use cracking the coding interview

Data structures and algorithms

Most of the technical questions that you will face in your coding interviews relate to data structures and algorithms.

If you don't know what data structures are, you must first build a solid foundation in computer science before you are ready for the next steps.

That is, if you are unfamiliar with terms like linked lists, trees, charts, binary search, and dynamic programming how to use cracking the coding interview (to name a few), then you have work to do!

A strong understanding of data structures and algorithms helps you write efficient programs that can run faster and use resources more efficiently.

Writing functional code is one thing, writing functionally correct code is an entirely different matter.

Interviewers value candidates who can analyze code, detect performance bottlenecks, and perhaps find better solutions.

Basic CS

Data structures and algorithms are not the only technical questions you may have in an interview.

In fact, they are not my favorite questions when interviewing a candidate.

Let's face it, these questions are so common that even below-average candidates wait and do very well on them.

The type of question that I personally don't like is about the basics of computer science.

In my own experience, these are the questions that distinguish one exceptional candidate from another who only remembered the answers to common interview questions.

The questions in this category are very diverse.

These may include questions about networks, operating systems, distribution systems, and system design.

But as soon as I ask them to write the code for a graphics search algorithm first, they write the most clean, perfect, and error-free code. So don't be that guy!

In all honesty, these questions are not asked as often as they should and I hope that changes.

However, if asked and it has shown a complete lack of knowledge, it is definitely a red flag and can significantly reduce your chances.

If you don't have years and years of experience, your resume doesn't matter so much as your answers to the coding questions you'll be asked.

As soon as you start to gain more professional experience, the impact of your resume gradually begins to increase.

Make sure your resume is complete and honest.

Also, be prepared to answer any questions related to projects and groundwork you have participated in.

Questions are not used most of the time to break the ice at the beginning of the interview.

First, let me define what constitutes behavior problems.

I am going to define behavior problems as any non-technical question.

These questions often do not have a significant impact on the hiring decision.

However, I must say that your general demeanor and the way you communicate is very important.

At the end of the day, we are human beings. Our psychology and human interactions influence our judgments and decisions.

Your interviewers should know that you are someone they can comfortably communicate with and work with.

If your competitor doesn't like your behavior, it doesn't matter how great you write the code.

You will probably get negative feedback.

I've seen this before?


I saw that superstars are rejected because they don't allow the interviewer to talk to them.

I have also seen cases where candidates were rejected because they were extremely arrogant.

Unsurprisingly, I saw cases where normal candidates were hired because all the interviewers enjoyed communicating with them.

Okay, now talk about resources.

What resources will help you prepare?

Most of the good resources available focus on the technical aspects of the interview.

They provide a large collection of coded interview questions and answers.