English for the Job Interview — A Plan for Immigrants

You got the callback. Interview is Friday. You needed your English yesterday, and right now — even more. This isn't "advanced English". This is interview English. Separate game. A 2-week plan: 7 standard questions, ritual answers, what NOT to say.

Who this is for

• You got the callback and the interview is in 1-2 weeks
• Or you're prepping "just in case" because you've got applications out
• Or you've been to 2-3 interviews and you keep getting stuck in the same place

You have a working B1-B2. You understand the questions. You can answer, but the answer sounds like a translation, not like live speech. And the interviewer hears it — faster than you'd think.

Why interview English ≠ just "good English"

Interviews are a ritual with ritual answers. Knowing the ritual is half the win.

School / Duolingo teach you to speak correctly. The interview asks you to speak ritually:

• "Tell me about yourself" — this isn't an invitation to your autobiography. It's a 90-second format with three signals.
• "What's your weakness?" — not a trap. A check on whether you know the ritual.
• "Why this company?" — a check on whether you spent 5 minutes on the website.

Ritual = rhythm + structure + pacing. Not content. You'll prep the content. Rhythm is a skill.

7 questions you'll get in 90% of interviews

1. "Tell me about yourself"

Format: 60-90 seconds. Three blocks:

• Who I am right now (brief — you're rated on smooth opening)
• What I've been doing lately, and why it fits the role (2-3 facts, not biography)
• Why I'm here (why this company, this role)

Don't say: "I was born in..." / "I graduated from... in 2014" / "I have 12 years of experience as a..."

Say: "I'm a [role]. Recently I've been [working on X, leading Y]. I'm interested in [this role] because [Z]." — and stop.

2. "Why this company / role?"

The ritual: show you READ. Not "I love your products" (empty). Better: "Reading your engineering blog, I noticed your team is moving toward [X]. That overlaps with what I built at [previous job], which is why this role caught my attention."

3. "What's your biggest weakness?"

The ritual: an honest weakness + what you do about it.

• Bad: "I'm a perfectionist" (cliché, everyone reads as dodge)
• Better: "I tend to over-explain in writing. I've been compensating by drafting + cutting one paragraph before sending."

Specific. Safe. Shows metacognition.

4. "Tell me about a time when... [behavioral]"

This is STAR: Situation → Task → Action → Result.

"At [previous job], we had [situation]. My responsibility was [task]. I [action]. As a result, [measurable outcome]."

Prep 4-5 STAR stories in advance. Have leadership, conflict, failure, ambiguity, and deadline covered.

5. "Why are you leaving your current job?"

The ritual: positive forward, not negative back.

• Bad: "My manager doesn't appreciate me"
• Better: "I'm looking for more [scope / impact / a chance to ship at scale], and this role looks like the right step."

6. "What's your salary expectation?"

The ritual: DON'T name a number first if you can avoid it.

"Based on the market data for this role in [location], I'd expect somewhere in the [X to Y] range. But I'm open to discussing once I learn more about the full package."

If they push — give a range, not a point. Always range.

7. "Do you have questions for us?"

You MUST have 3-5 questions. Having none = "I don't care".

Strong ones:

• "What's the biggest challenge the team is facing right now?"
• "What would success look like in the first 90 days?"
• "How would you describe the team's communication style?"
• "What's something about the role that doesn't show up on the job description?"

The 2-week plan

Week 1: rhythm + content

Daily (20 min): watch one mock interview on YouTube in your field. Don't just watch — listen for the rhythm. How they start? Where the pauses? What's the intonation?

3× a week (30 min): record yourself answering "Tell me about yourself". Listen back. What sounds like translation? Rewrite. Record again.

Collect: 4-5 STAR stories from your background. Write each one out. Trim to 60-90 seconds.

Week 2: simulation + polish

Daily: one mock-interview session — Tandem / mentor / ChatGPT Voice / Pramp. Don't "study" — do.

Last 2 days: no new content. Re-read your STAR stories. Sleep.

What NOT to do

• Don't imitate a native accent. Accents are the norm in US tech. Work on clarity, not a copy.
• Don't apologize for your English at the start. "I apologize for my English" frames you down. Your English is your tool, not your apology.
• Don't use foreign-language idioms translated literally. "We caught the bull by the horns" from your native language may not exist in English.
• Don't memorize answers as a script. Sounds scripted → interviewer checks out. Prep the rhythm, not the text.
• Don't skip "Do you have questions for us?" It's the most underrated section. This is where you take initiative back.

How Deep In does this

Interview content is a separate YouTube category and Deep In's sweet spot:

• Mock interview channels — search "software engineer behavioral interview", "UX designer interview prep" — dozens of channels with real questions and answers.
• TED Talks on work / communication — eloquent, structured, train your rhythm.
• Lex Fridman / Diary of a CEO — interviews with leaders — listen for how they phrase under pressure.
• Recruiting podcasts — industry-specific.

Take any — Deep In transcribes, you tap a phrase: "'Walk me through' = walk-step-by-step, casual, no theory required. Use this pattern when asked about a process."

Not a course. Not "50 interview phrases". Adaptive work with real interview format in your field.

Common questions

Should I pay for an interview coach? Depends. For senior roles at $200k+ comp — yes, $300-500 on 3-4 coach sessions is worth it. For entry/mid — Pramp (free) + Deep In + 1-2 mocks with a friend is enough.

How do I prep technical interviews when English is its own problem? Prep the technical part in your native language, then translate the key explanations. Record yourself. Listen — does it sound like a native explaining? If not, simplify.

I bombed an interview because of my English — what do I do? You probably didn't "bomb because of English". You bombed because of missing ritual. English was the symptom. Prep the ritual; the language catches up in process.

How do I ask for a question to be repeated if I didn't catch it? "Could you rephrase that?" — neutral, safe. Don't apologize. It's a normal request even for native speakers.

Ready to start? Join the Deep In waitlist →