Fluent Start speaking

Workplace situation · Hiring and exits

The job interview

Tell your story with results, or run an interview that is fair, warm and sharp.

Case study: Karan's résumé readout

Karan, a Java developer in Hyderabad with six years at a large services firm, got a final round with a fintech in Austin. Asked to tell them about himself, he recited his résumé from his tenth marks onward for four minutes. Asked about a hard problem, he said "we" eleven times and never said what he did. His friend Pooja interviewed for the same role a week later. She gave a 60 second pitch, told one STAR story where she cut batch job time from 3 hours to 40 minutes, and asked two sharp questions about the team's on-call load. She got the offer.

Takeaway: An interview is a story, not a recitation. Lead with what you did, prove it with numbers, and ask real questions.

Many of us were taught to be modest and to say "we" to show we are team players. Global interviewers need to hear "I" to know what you personally did, and they read a lack of questions at the end as a lack of interest.

Answering as candidate (you are Candidate)

Goal: Leave Megan with a clear picture of what you did, what you're good at, and why you want this role.

Step by step

  1. Pitch in 60 seconds. Present, past, future: what you do now, one or two highlights, why this role.
  2. Tell STAR stories. Situation, Task, Action, Result. Spend most of the time on your actions and the result.
  3. Say I, not we. Credit the team, then be specific about your part.
  4. Ask real questions. Two or three questions about the team, the work and how success is measured.

Say this, not that

I'm a backend engineer with six years in payments, and right now I lead a team of four on our settlement platform.I did my schooling in Vijayawada, then my B.Tech from...Start with the present. Nobody needs your tenth marks.
The situation was that our nightly batch was taking three hours and delaying reports for the business.
What I did was profile the job, find two slow queries, and move the heavy step to parallel workers.We did a lot of optimization."I" tells them what you can do for them.
As a result, the job dropped from three hours to forty minutes, and the reports went out before nine.End every story with a number or a visible outcome.
What does success look like for this role in the first six months?No questions, everything is clear.Good questions show genuine interest and judgment.

Model conversation

Megan
Thanks for joining, Pooja. To start, tell me a bit about yourself.
You
Sure. I'm a backend engineer with six years in payments. I currently lead a team of four on our settlement platform, and I'm looking for a product company where I can own a system end to end.
Megan
Great. Tell me about a hard technical problem you solved.
You
Our nightly batch took three hours and delayed business reports. I profiled it, fixed two slow queries and moved the heaviest step to parallel workers. It now runs in forty minutes.
Megan
Nice. What was the hardest part?
You
Honestly, convincing the ops team to let us change a job nobody had touched in years. I ran it in parallel for a week to prove it was safe.
Megan
That's a good answer. What questions do you have for me?
You
Two, if that's okay. What does success look like in the first six months, and what does on-call look like for this team?

Rehearse this side out loud

Interviewing a candidate (you are Interviewer)

Goal: Put the candidate at ease, get real evidence of their skills, and leave them wanting the job.

Step by step

  1. Open warmly. Introduce yourself, explain the format and the time, and say they can ask questions.
  2. Probe with structure. Ask for one specific example, then dig: what did you do, why, what happened.
  3. Rescue the "we". When they say "we", kindly ask what their part was.
  4. Sell the role. Save ten minutes to answer questions honestly and share what makes the team good.

Say this, not that

Thanks for joining, Karthik. We'll spend about forty minutes on your experience, and leave ten for your questions.Okay, let's start. Tell me about yourself.A clear agenda calms nerves and gets better answers.
Can you walk me through one specific time you had to debug a production issue?Are you good at debugging?Yes or no questions get rehearsed answers. Examples get evidence.
You mentioned the team did that. What was your part in it?Many candidates are modest. Help them show you what they did.
That's helpful. What would you do differently if you did it again?
Let me tell you a bit about why I enjoy working on this team.Strong candidates have options. The interview is also your pitch.

Model conversation

You
Hi Karthik, thanks for joining. I'm the engineering manager. We'll talk about your experience for forty minutes and keep ten for your questions. Sound good?
Karthik
Yes, sounds good. Thank you.
You
Great. Tell me about a time you debugged a tricky production issue.
Karthik
We had a memory leak in our order service. We found it was a cache that never expired, and we fixed it.
You
Nice. You said we found it. What was your part specifically?
Karthik
I took the heap dumps, compared them over six hours, and spotted the cache map growing. Then I added an expiry and a size limit.
You
That's exactly what I wanted to hear. We've got ten minutes left. What would you like to know about us?
Karthik
How do you decide what the team works on each quarter?

Rehearse this side out loud

Practice it out loud

Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.

Practice both sides

Related situations