Interview Tips

Walk into every interview
fully prepared

From first-round screenings to final panel interviews — this guide covers everything: preparation, common questions, technical rounds, and salary negotiation.

⏱ 20 min read💬 6 common Q&As with sample answers💻 Technical interview section

Step 1

Before the interview

Research the company thoroughly

Know the product, recent news, competitors, and the hiring manager's LinkedIn. Interviewers can tell immediately who researched and who didn't.

Re-read your own resume

You will be asked about every line. Know exact dates, metrics, and the story behind each role. Stumbling on your own resume is a red flag.

Prepare your STAR stories

For every major achievement on your resume, prepare a Situation-Task-Action-Result story. Most behavioural questions map directly to these.

Prepare 5 smart questions to ask

Questions about team dynamics, success metrics for the role, and tech stack signal genuine interest. "What does success look like in 90 days?" is always good.

Do a technical dry run

For video interviews, test camera, mic, lighting, and internet 24 hours before. For in-person, arrive 10 minutes early and find the room in advance.

Common Questions

Questions you will definitely be asked

"Tell me about yourself."

Format: Past → Present → Future

Structure this as a 90-second narrative: where you came from → what you've built expertise in → why this role excites you. This is not a resume recitation — it's your pitch.

"What is your greatest weakness?"

Format: Real weakness + Concrete action taken

Pick a real weakness that does NOT disqualify you for the role. Then show what you've done to address it: "I used to struggle with public speaking, so I joined Toastmasters. I've now presented to audiences of 200+."

"Why do you want to leave your current job?"

Format: Growth focus, never negative about employer

Stay positive. Focus on what you're moving toward, not what you're escaping. "I've learned a lot at X, but I want to work on problems at greater scale / in a different domain / with more ownership."

"Describe a challenge you overcame at work."

Format: Situation → Your action → Measurable result

STAR format is ideal here. Pick something where you took clear initiative and had measurable impact. Avoid blaming others — focus entirely on what YOU did.

"Where do you see yourself in 5 years?"

Format: Growth ambition aligned with company trajectory

They want to know if this role is a stepping stone or a destination. Be honest about wanting to grow into leadership or deepen expertise — but connect it to what this company can offer. Don't say 'in your position'.

"What is your expected salary?"

Format: Range based on research, not a single number

Research market rates first (see our Salary Guide). Give a range: "Based on market data and my experience level, I'm looking at ₹18–22 LPA, but I'm open to discussing the full package." Never anchor too low.

Step 2

During the interview

Use the STAR framework

Situation → Task → Action → Result. This structure prevents rambling and shows clear thinking. Aim for 90-second answers on behavioural questions.

Pause before answering

It's professional to say 'That's a great question — let me think for a moment.' A thoughtful 5-second pause beats a rushed, confused answer.

Mirror the interviewer's energy

Match their pace and formality level. If they're conversational, be conversational. If they're formal, stay professional. Reading the room is a core skill.

Quantify everything

Don't say 'I led a large team'. Say 'I managed 8 engineers across 3 time zones.' Numbers make your experience concrete and memorable.

Address gaps proactively

If you have a career gap or an apparent weakness, address it before they ask. Owning the narrative is far stronger than being put on the defensive.

Tech Rounds

Technical interview strategies

Think out loud

Interviewers want to evaluate your reasoning process, not just the final answer. Narrate your approach: "My first instinct is X, but let me consider the edge cases..."

Clarify before coding

Ask: 'What constraints apply? What's the expected input/output? Should I optimise for time or space?' This shows engineering maturity.

Start with a brute-force solution

State the naive O(n²) solution first, then optimise. 'A working solution first, then we optimise' is how senior engineers think.

Test with edge cases

After your solution, say: 'I'd test this with an empty array, a single element, and a very large input.' Interviewers love candidates who think about edge cases.

Recover gracefully from mistakes

If you hit a wall, say: "I think I'm approaching this wrong — let me step back." Staying calm under pressure is a core trait they're evaluating.

Your resume gets you the interview.
Your prep gets you the offer.

Make sure your resume clears the ATS first — then use these tips to close the deal.

Walk into every interviewfully prepared