Interview Preparation: The Whole Sequence

The short answer. Prepare four things and you have covered most of what any interview will ask. One: a ninety-second self-introduction. Two: six stories from your own work, written in STAR form, that between them cover a success, a failure, a conflict, a deadline, a leadership moment and a change you drove. Three: the role-specific technical questions for your field. Four: three questions to ask them. Everything else is delivery.

Interviews look unpredictable and are not. The same five categories of question turn up in almost every process, and preparation is mostly a matter of knowing which category you are in.

The five kinds of question you will face

1. Behavioural. "Tell me about a time when..." The interviewer is looking for evidence that you have done the thing before. Answer in STAR: situation, task, action, result. Most of your preparation time belongs here, because these questions are the ones you can genuinely rehearse.

2. Technical or functional. Domain knowledge for your field: SQL and system design for engineers, journal entries and reconciliations for accountants, dosage and pharmacovigilance for pharma roles, classroom management and lesson planning for teachers. Predictable from the job description, and the reason the interview question sets exist.

3. Situational or hypothetical. "What would you do if..." Testing judgment on a scenario you may not have faced. Answer by stating how you would decide rather than performing certainty: what you would find out first, what would change your answer, and what you would do with each outcome.

4. Application-based. A problem, a case, a dataset, a take-home, a live exercise. Testing whether you can apply the knowledge under observation. Think aloud. The reasoning is usually being marked more heavily than the answer.

5. Motivational and cultural. Why this role, why this company, why leaving, where you see yourself. These sound like small talk and are not. Vague answers here undo strong answers elsewhere, because they suggest you are applying everywhere identically.

The self-introduction

"Tell me about yourself" is the first question in almost every interview, and it sets the frame for everything after it. Ninety seconds. Present, past, future.

Present: what you do now, in one line. Past: the two or three steps that got you here, with evidence. Future: why you are in this room.

For an experienced candidate:

> I am an operations analyst at [Company], where I handle dispatch planning for a 40-vehicle fleet across Maharashtra, Gujarat and Goa. I started on the customer-support side four years ago, moved into ops when we were scaling into tier-2 cities, and the work I am proudest of is rebuilding the delivery-exception workflow, which brought exceptions down about 22% in two quarters. I am looking to move into supply chain analytics in a product company, which is why this role interested me: it is the same problem with better data behind it.

For a fresher:

> I graduated in B.Com from Christ University this year. Through my final year I interned in accounts payable at [Firm] for eight months, processing around 400 vendor invoices a month in Tally and SAP, and I worked on clearing a backlog of about 900 unmatched entries before the year-end close. That is where I found I actually enjoy reconciliation work, which most people find tedious. I am looking for a junior accounts role where AP is the core of the job rather than a rotation.

What to avoid: starting with your date of birth and your family, reciting your entire education from Class 10, saying "I am a hardworking person and a quick learner", and running past two minutes. Write yours down, say it out loud six times, and stop rehearsing it after that so it does not sound recited.

Six stories, in STAR form

Prepare six stories from your own experience and you can answer almost any behavioural question, because most of them are variations.

1. A result you are proud of.
2. A failure, and what you changed afterwards.
3. A disagreement with a colleague or a manager.
4. A deadline or a crisis under pressure.
5. A time you led, influenced or taught without formal authority.
6. A change you drove, and how you got people to accept it.

For each, write four lines:

• Situation: the context, in one sentence.
• Task: what you specifically had to do.
• Action: what you did, in detail. This is the longest part and the part people rush.
• Result: what came of it, with a number where one honestly exists.

Two rules that fix most weak answers. Say "I" rather than "we" when describing your actions; the interviewer is assessing you, not your team. And do not end on the situation. An answer that describes a problem vividly and never says what you did is the most common failure in behavioural interviews.

The failure story is the one people prepare least and it is asked constantly. Pick a real failure with a real consequence, take responsibility without over-apologising, and spend most of the answer on what you changed. A failure story with no lesson is a complaint; a fake failure ("I work too hard") is transparent.

The day itself

Before

• Research the company properly: what it sells, who its customers are, and one thing that happened recently. Fifteen minutes is enough to be visibly better prepared than most candidates.
• Re-read the job description and your own resume. You will be asked about lines on your resume that you wrote a year ago.
• Carry printed copies of the resume, and your ID.
• For a video interview: test camera, microphone and network beforehand, sit with light in front of you rather than behind, use a plain background, and have a phone-based fallback ready.
• Plan to arrive ten to fifteen minutes early. Not forty-five, which creates an awkward wait for the interviewer.

During

• Greet the interviewer, sit when invited, and put the phone away entirely.
• Listen to the whole question before answering. Take a two-second pause; it reads as considered, not slow.
• Ask for clarification when a question is ambiguous. It is a strength, not a weakness.
• Give specifics: numbers, names of tools, scale, timelines.
• Say "I do not know" when you do not, and follow it with how you would find out. Every interviewer has heard someone bluff, and it is worse than not knowing.
• Do not criticise a current or previous employer. The interviewer hears how you will speak about them.
• Do not raise salary in a first-round interview unless they raise it.

After

• Send a short thank-you email within a day, three or four lines, referring to one specific thing discussed.
• Follow up once if you have heard nothing by the date they gave you, or after a week if they gave none.

"Do you have any questions for me?"

Saying no is the most common and most expensive mistake at the end of an interview. It reads as indifference, and it wastes the one part of the process where you are the one gathering information.

Prepare three, ask two, and make them questions you actually want answered.

Good:

• What does success in this role look like in the first six months?
• What is the biggest challenge the person in this role will face?
• How is the team structured, and who would I work with most closely?
• What made the last person in this role successful, or unsuccessful?
• How are decisions made when the team disagrees?
• What is the review or feedback cycle here?

To avoid in a first round: salary, leave policy, working hours, appraisal timing, and anything answered on the first line of the company's About page. Compensation is an appropriate conversation later in the process, usually with HR or at offer stage.

If you genuinely have no questions left because they were all answered, say that, then ask one anyway: "You have covered most of what I wanted to ask. The one thing I would still like to understand is..."

The rest of the preparation is role-specific

The technical half of the interview is domain work, and it is worth practising against real question sets for your own field rather than generic lists. The published sets cover BPO, customer service, front office, accounts payable, business development, supply chain, real estate, pharma, pharmacovigilance, quality assurance, medical representatives, company secretary, computer networks, Salesforce (admin, integration and QA), Python for data engineering, MBA admissions and student interviews. They are collected under interview preparation.

Prepare the four things at the top of this page, then spend the remaining time on the question set for your role. That order is deliberate: the behavioural answers transfer to every interview you will ever take, and the technical ones only transfer to this one.