Job interview basics — answering the classics

A US job interview follows a fairly predictable script. There are seven or eight classic questions you’ll hear at almost every first-round interview, plus a behavioral round (Tell me about a time when…). Knowing the structure of the answers — not memorizing them, but knowing the structure — is what separates a confident candidate from a nervous one.

This lesson gives you the questions, the formulas, and the AmE-specific cultural conventions: how long to talk, what not to say, when to ask about salary, and how to follow up.

The interview opener — Tell me about yourself

This is almost always the first real question. It’s not an invitation for your life story — it’s the recruiter’s way to hear you talk about your work in 60-90 seconds.

The structure (Present-Past-Future)

1. Present — what you do now: I’m currently a [role] at [company], where I [main responsibility].
2. Past — relevant background: Before that, I [worked at / studied at] X, where I [relevant experience].
3. Future — why this role: I’m now looking for [the kind of opportunity this role offers] — which is exactly why this role caught my eye.

Example answer

Sure! I’m currently a backend engineer at FinCo, where I lead a team of three on payments infrastructure. Before that, I spent three years at a startup building real-time data pipelines, which is where I really got interested in distributed systems. I’m looking to join a larger company where I can work on consumer-scale products, and your team’s work on the payments platform is exactly the kind of problem I want to be solving.

That’s about 60 seconds. Don’t go over 90.

What to avoid

• Don’t start with I was born in… — interviewers don’t need biographical history.
• Don’t list every job. Pick the ones that matter for THIS role.
• Don’t go past 90 seconds — you’ll lose them.

Why are you interested in this role / company?

This question tests whether you’ve done your homework on the company. Generic answers fail.

Structure

• One specific thing about the company (mission, recent news, product, culture).
• One specific thing about the role (responsibilities, team, scope).
• One thing about you (why this matches your trajectory).

Example

A few things drew me to this role. First, your team’s recent work on [specific product / initiative] caught my attention — I read [Engineering blog post / article] and the approach to [X] is exactly the kind of problem I want to be working on. Second, the role’s mix of hands-on engineering and mentorship fits where I am in my career. And finally, the company’s commitment to [specific value] aligns with what I’m looking for in my next move.

What are your strengths?

Pick two or three strengths, with examples. Don’t list adjectives.

Phrases

• I’d say my biggest strength is [X]. For example, [story].
• One thing my managers tend to highlight is [X]. At [company], I [example].
• I’m particularly strong at [X]. A recent example: [story].

Example

I’d say my biggest strength is breaking down ambiguous problems. At my current company, when our team was asked to design a new fraud detection system from scratch, I was the one who led the early scoping — I built the requirements doc, ran stakeholder interviews, and turned a vague brief into a 6-week plan. The system is now live and catching about 30% more fraud than the old one.

What’s your biggest weakness?

The trap question. The wrong answers are obvious: I’m a perfectionist, I work too hard, I care too much — these are clichés that interviewers see through immediately.

The right approach

Pick a real weakness. Show growth — what you’ve done about it.

Structure

1. State the weakness honestly (and pick something not catastrophic for the role).
2. Acknowledge the impact.
3. Describe what you’ve actively done to address it.

Examples

I used to struggle with delegating — early in my management career, I’d take on too much myself because it felt faster. The downside was that I’d burn out and my team didn’t grow. I started using a weekly delegation review with my mentor, and over the past year I’ve intentionally handed off entire projects to my reports. It’s been hard but the team is stronger for it.

Public speaking has historically been a weakness for me. Last year I joined a Toastmasters group and now lead the team’s monthly demo, which has been uncomfortable but is improving fast.

What NOT to say

• I’m a perfectionist. — cliché.
• I work too hard. — cliché.
• I have no real weaknesses. — red flag.
• A weakness that disqualifies you for the role (I’m bad at meeting deadlines for a project manager role).

Where do you see yourself in 5 years?

Show ambition + alignment with the company’s trajectory. Don’t say running my own company (signals you’ll leave).

Structure

• Growth in role / scope.
• Skills you want to build.
• Alignment with the company.

Example

In five years, I’d like to be leading a larger team — ideally on a product where I can see direct user impact. I want to keep deepening my expertise in [domain] and ideally take on more of the cross-functional, strategic side of engineering leadership. I’d love for that growth to happen here, in a place where the technical problems are this interesting.

Behavioral questions — the STAR method

Tell me about a time when… / Walk me through a situation where… — these test how you actually behaved in past situations. Use the STAR method:

Common behavioral questions

• Tell me about a time when you handled a conflict at work.
• Tell me about a time you failed.
• Walk me through a difficult project you led.
• Describe a situation where you had to convince someone of something.
• Tell me about a time you had to deal with an unhappy customer.
• Tell me about a time you missed a deadline.

Example STAR answer

(S) Last year at FinCo, our team had two senior engineers who were openly disagreeing on a system design. Tension was affecting the whole team’s productivity. (T) As tech lead, I needed to resolve it before our quarterly deadline. (A) I scheduled separate 1:1s with each, then a structured working session with both — using a written design doc as the focal point so we were arguing about the artifact, not each other. I also brought in a neutral senior engineer for a tiebreaker on the most contested decision. (R) We landed on a hybrid design that incorporated both their best ideas, shipped on schedule, and the two now collaborate well. The doc-based approach is now how we resolve design disputes on my team.

Why are you leaving your current job?

The cardinal rule: never trash-talk a current or previous employer. Interviewers assume you’d talk about them the same way later.

Safe framings

• I’m looking for the next step in my career — more [scope / responsibility / impact].
• I’ve learned a lot at [current company], and I’m ready for new challenges.
• I’m looking for a role where I can [specific growth].
• My current company has been a great place to learn, but the kind of work I want to do next isn’t available there.
• I’m looking for an environment where [X] — and that’s exactly what attracted me here.

What to avoid

• My manager is terrible. — even if true.
• The company is going downhill.
• They underpay me. — talk about growth, not money.
• I just hate it there. — too negative.

The salary question

You’ll likely be asked: What are your salary expectations? The pro move is to deflect early, anchor later.

Deflection phrases (early in process)

• I’d love to learn more about the role first before talking numbers. What’s the range you have in mind for this position?
• I’m open — what’s the range for this role?
• I’d want to make sure the role is a good fit first. Could you share the budgeted range?
• I’m focused on the right opportunity. Salary will follow if everything else aligns.

When you have to give a number

• Based on my research and experience, I’d be looking for a range of [X to Y].
• I’m targeting [X], but I’m flexible based on the full package.

Closing the interview — your turn

The interview almost always ends with Do you have any questions for us? Always have questions. No, I think you covered everything signals low interest.

Smart questions to ask

• What does success look like in this role in the first 90 days?
• What are the biggest challenges someone in this role would face?
• What’s the team culture like?
• How would you describe your management style? — to a hiring manager.
• What’s the career path from this role?
• What do people who succeed here have in common?
• What are you most excited about for the team in the next year?

What to AVOID asking in the first interview

• How much vacation do I get?
• How often do you work late?
• Can I work fully remote? — unless the role is advertised as such.
• How quickly can I be promoted?
• Anything that’s easily answered by Googling.

Closing phrases

• I’d love the opportunity to work with this team.
• Is there anything I can clarify about my background?
• When can I expect to hear back? — fine to ask.
• What are the next steps?
• Thanks so much for the conversation — I really enjoyed it.

After the interview — the thank-you email

Send a thank-you email within 24 hours of every interview. This is US convention; not sending one is a small but real negative.

Template

Subject: Thanks for today / Thank you — [Your Name]

Hi [Interviewer’s Name],

Thank you for taking the time to speak with me today about the [Role] position. I really enjoyed learning more about [specific topic from the conversation], and I’m even more excited about the opportunity to join [Team / Company].

Please let me know if there’s anything else I can share that would be helpful.

Best, [Your Name]

Keep it short — three to five sentences. Reference one specific thing from the conversation so it feels personal.

Mini-dialogues

Dialogue 1: salary deflection

Recruiter: Before we go further — what are your salary expectations? You: I’d love to learn more about the role and the team first. Could you share the budgeted range for this position? Recruiter: It’s between $140K and$175K base. You: That’s helpful — that range works for me. I’d want to talk through the full package once we get further along.

Dialogue 2: handling weakness

Interviewer: What’s your biggest weakness? You: I used to struggle with saying no — I’d take on every project people asked me about, and end up overcommitted. About a year ago I started keeping a weekly priorities list and saying let me get back to you before agreeing to new things. It’s helped a lot, though I still have to be intentional about it.

Dialogue 3: closing the interview

Interviewer: That’s all my questions. Do you have any for me? You: A couple. First, what does success look like in this role in the first 90 days? And second, what are you most excited about for the team this year? (after their answers) You: Thanks so much for taking the time. I really enjoyed the conversation — I’d love the opportunity to work with this team. What are the next steps?

Register table — same intent, three levels

AmE interview phrases worth memorizing

• Tell me about yourself — the universal opener.
• Walk me through… — Walk me through a project / a challenge / your background.
• The STAR method — Situation, Task, Action, Result.
• What does success look like in this role? — strong closing question.
• I’d love the opportunity to… — warm closing.
• What are the next steps? — fine to ask.
• Could you share the range for this role? — salary deflection.
• Thanks so much for the conversation. — thank-you email opener.

Common Russian-speaker mistakes

1. Multi-minute Tell me about yourself answers: keep it 60-90 seconds. Practice it.
2. Trash-talking previous employers: even subtle complaints reflect badly. Frame your move as growth, not escape.
3. Saying I’m a perfectionist: the most overused fake-weakness in interview history.
4. Asking only about salary / vacation / remote work in the first interview: makes you sound only money-motivated. Save these for round two or post-offer.
5. Translating Я хочу… as I want…: in formal interview English, I’m looking for / I’d love / I’m interested in sound more polished.
6. Skipping the thank-you email: not sending one is a quiet negative. Send within 24 hours.
7. Saying I’m new in this country as a defense for weak English: don’t apologize for your language; let the strength of your answers carry it.
8. Using we in STAR answers: interviewers want to know what YOU did. Use I, even when describing team work — I led, I proposed, I delivered.

Summary

• Tell me about yourself = 60-90 seconds, Present-Past-Future structure.
• Why this role = specific company knowledge + role fit + your trajectory.
• Strengths = 2-3 with examples, not adjective lists.
• Weakness = real one + what you’ve done about it. NEVER I’m a perfectionist.
• 5 years = growth + alignment + ambition (not “running my own company”).
• Behavioral = STAR method (Situation, Task, Action, Result). Use I, not we.
• Why leaving = never trash-talk; frame as growth.
• Salary = deflect early, anchor later. What’s the range?
• Closing = always have questions. Send a thank-you email within 24 hours.

You’ve completed Module 6 — Functional language. Next module: Reading skills — text types and strategies.