~/coding-interview/tips-for-coding-interview.md

How to nail your Coding Interview

// TL;DR

Don't jump to optimal solutions — start brute force, communicate your thinking, ask clarifying questions, and walk through examples before coding.

How to nail your Coding Interview

Here are some tips while giving your coding interviews.

1. Never try to jump to the optimal solution first

WHenever interviewer asked you a question. Normally candidates jump to the most optimal solutions straight away. Never do that, even if you know the answer. Manytimes it happens that people just remembers the optimal solution, and when asked in interview on how they come up to this solution, or what are your thought process? They have no clue.

Remember, always start with the brute force algorithm. You can just discuss with your interviewer that this is the simplest approach, and there can be better solutions to this. Discuss them one by one. When you give issues in the naive solution, your interviewer understood that you have knowledge about the topic.

2. Clear the problem statement first before starting solving

Always try to speak the problem statement and clarify any confusion. Do not assume anything. Speak everything, whatever you are assuming. Many candidates just start writing solution, and when asked about specifics. They messed it completely. Not everything is implicit. Try to expand the problem and clear every single details before solving the problem.

3. Bug free code

Interviewer often asked about writing a production ready code. You should be able to come up with an error free code with almost all edge cases handled.

4. Speak your mind

Interviewer loves to hear your thought process. They don’t like a perfect solution with no explanation given. Often candidates failed to explain their solution which clearly states that they have memorize the solution.

5. Most Important, Don’t give-up

It is very important to keep thinking, and speak your mind out. Never ever, give up. Keep up the thinking ON. Interviewer is there to give some hints too. Many times, interviewer gave a super hard problem, and want to see how you are thinking about it. Its not always expected to come up a super optimized solution.

$ subscribe --weekly

One deep dive a week, in your inbox

System design, AI engineering, trading systems and interview prep. Tested code, real numbers. Free, and you can unsubscribe any time.

or read it on gyanbyte.substack.com

Share

Related Posts

What FAANG companies expect in their interview from candidates

What FAANG companies expect in their interview from candidates

Its every software engineer’s dream to work with the big FAANG companies…

Magical usage of Bitwise operators - Get optimized solutions for many arithmatic problems

Magical usage of Bitwise operators - Get optimized solutions for many arithmatic problems

Introduction I will list some of the interesting usage of bitwise operators…

How to prepare for your next Coding Interview

How to prepare for your next Coding Interview

Here are some tips while preparing for your coding interviews. 1. Do study or…

Coding Interview - Useful Terms Cheatsheet

Coding Interview - Useful Terms Cheatsheet

Big-O notation In simpler terms, its kind of a unit to measure how efficient an…

List of Sorting Algorithms

List of Sorting Algorithms

This topic is one of the most common studied. When somebody started preparation…

Coding Interview Cheatsheet

Coding Interview Cheatsheet

Latest Posts

How to Stay Valuable as a Software Engineer in the AI Era: A Practical Playbook

How to Stay Valuable as a Software Engineer in the AI Era: A Practical Playbook

In the previous article I argued that AI is not killing software engineering…

How to Review AI-Generated Code: A Checklist for Catching What the Model Missed

How to Review AI-Generated Code: A Checklist for Catching What the Model Missed

A few months back I approved a PR that was almost entirely AI-generated. It…

How to Debug AI-Generated Code: Understand First, Fix Last

How to Debug AI-Generated Code: Understand First, Fix Last

In the last article I wrote about reviewing AI code before it goes in. This one…

The Future of Software Engineering: What AI Changes, What Stays, and Where the Jobs Go

The Future of Software Engineering: What AI Changes, What Stays, and Where the Jobs Go

Every few weeks somebody sends me a scary headline — “AI will replace all…

The Transactional Outbox Pattern: Never Lose an Event Again

The Transactional Outbox Pattern: Never Lose an Event Again

This is one of those patterns that looks like nothing until you get burnt once…

Event Sourcing, Explained: Store What Happened, Not Just the Final State

Event Sourcing, Explained: Store What Happened, Not Just the Final State

Here is a question I like to ask in interviews: your bank account shows a…