Essential Do’s and Don’ts for Technical Interview Success

1. Before the Interview

Prepare pen, paper, and headphones.

Find a quiet place with a stable internet connection.

Check that camera and audio work properly.

Prefer Hangouts/Skype over a phone call for easier sharing of links and text.

Use a programming language you are comfortable with.

Familiarize yourself with the coding environment (e.g., CoderPad, CodePen) and configure shortcuts, auto‑completion, and indentation.

Prepare answers to common interview questions.

Prepare thoughtful questions to ask the interviewer at the end.

Dress comfortably; casual attire is usually acceptable.

Stay calm and composed.

2. Self‑Introduction

Introduce yourself in a few sentences within one or two minutes.

Highlight interests relevant to the position you are applying for.

Speak enthusiastically and smile to make your voice more engaging.

Avoid spending too much time on the introduction, as it reduces coding time.

3. Getting the Problem

Repeat the problem statement to the interviewer.

Clarify any implicit assumptions; many problems are deliberately underspecified.

Confirm input format and constraints (e.g., well‑formed, non‑empty).

Use a small example to ensure you understand the problem.

Explain a high‑level approach, even if it is a brute‑force solution.

Iteratively improve and optimize the approach, reducing redundant work and caching repeated calculations.

State and discuss the time and space complexity of your method.

If stuck, recall similar problems you have seen and how they were solved.

Do not ignore any information provided; every detail can be important.

Avoid jumping straight into coding without the interviewer's permission.

If you are uncertain about your approach, voice that uncertainty.

4. During Coding

(Illustrative image omitted for brevity.)

5. After Coding

Review the code carefully as if you are seeing it for the first time.

Check for errors.

Generate additional test cases, including edge cases.

Step through the code with those test cases.

Identify opportunities for refactoring.

Restate the time and space complexity.

Discuss trade‑offs and how you would improve the solution given more time.

Announce that you have finished coding before moving on to the next steps.

If you disagree with the interviewer, argue politely; they are unlikely to be wrong but may have a different perspective.

6. Closing the Interview

Ask thoughtful, company‑specific questions (a separate list of good questions can be prepared).

Thank the interviewer.

Optionally inquire about your performance, though this can feel awkward.

If you have no questions, simply end the interview.