Interview Prep Guide

By VetriMarg · 24 Sep 2026

Research the company and role, properly

"I read about your company on your About page" is not research. Spend 30 to 45 minutes before any interview reading their most recent news or product launches, understanding what the team you're interviewing for actually owns, and looking up the interviewer on LinkedIn if you know their name in advance. This isn't about flattery. It's what lets you ask a sharp, specific question later instead of a generic one.

The STAR method for behavioural questions

"Tell me about a time you dealt with conflict" gets answered badly by most candidates because they ramble. Structure every behavioural answer the same way:

• Situation. One or two sentences of context.
• Task. What you specifically needed to do.
• Action. What you actually did, in detail. This is the longest part.
• Result. The outcome, with a number or concrete change if you have one.

Prepare 4 or 5 real stories in advance that can flex to cover conflict, failure, leadership, and a project you're proud of. Most behavioural questions are variations on these four themes.

Technical or case interview prep

If the role involves a technical or case round, practice out loud, not just in your head. Talking through your reasoning while solving a problem is a skill of its own, separate from solving the problem itself. Time yourself on practice questions so the real interview's pace doesn't catch you off guard.

Questions to ask them

Never say you don't have any questions. It reads as disengagement. Good questions are specific to what you've heard in the interview so far. "You mentioned the team is rebuilding the onboarding flow. What's driving that?" is far stronger than a generic "what's the culture like?"

Day-of logistics

For virtual interviews, test your camera, mic, and lighting the day before, not five minutes before. For in-person, know exactly how you're getting there and build in 20 minutes of buffer. Arriving flustered costs you more composure than almost any single interview question.

After the interview

Send a short thank-you note within 24 hours. A few sentences referencing something specific from the conversation, not a generic template. It's a small signal, but it's one most candidates skip, which makes it noticed when you don't.