Week 21 — Interview stories and self-advocacy¶
This week
Grammar: Narrative tenses for stories about your past work · Vocabulary: Achievement verbs (spearheaded, orchestrated, streamlined) · Idioms & phrasal verbs: Interview idioms (hit the ground running, go the extra mile) · Speaking: Mock behavioural answers with STAR · Writing: Resume and profile bullet points · Soft skill: Self-advocacy without arrogance
Difficulty: high (C1+). Every exercise has a timer. Work to it: interviews are timed, and precision under a clock is the skill being trained. Answers are collapsed; commit to an answer before opening.
Day 1 — Grammar: Narrative tenses for stories about your past work¶
⏱ 30 min · Mon · 5 min rule, 15 min exercise (timer), 5 min check, 5 min use it.
Rule in 60 seconds¶
A work story has a foreground (the events, in order) and a background (the situation around them, and what happened before). Each layer gets its own tense.
| Layer | Tense | Use | Example |
|---|---|---|---|
| Events in order | Past simple | Completed actions that move the story | We rolled back the release and paged the vendor. |
| Background / interrupted action | Past continuous | Something in progress when an event happened; scene-setting | We were migrating billing when the vendor announced the deprecation. |
| Earlier than the story's "now" | Past perfect | The action happened before another past moment, and matters to it | The release failed because nobody had tested the rollback. |
| Duration or cause before a past point | Past perfect continuous | Stress on the length or the visible effect of an activity | She had been leading the team for three years before she became a director. |
| Repeated past habit | used to / would | Situations that no longer hold / repeated actions | We used to deploy by hand. Every Friday we would freeze the branch. |
Exceptions and limits
- Stative verbs (know, have [own], believe, want, understand, belong) are rarely continuous. Say "I knew the codebase," not "I was knowing."
- would describes repeated actions, not states. "We would have a monolith" is wrong; "we had a monolith" is right.
used toworks for both. - The past perfect is not a "more past" decoration. Use it only when the order would otherwise be unclear or when the earlier event explains the later one. If the order is obvious from before/after/once, past simple is normal: "After we deployed the patch, we watched the error rate."
- A finished time marker forces past simple. In 2021, last year, when I joined, two years ago cannot go with present perfect: "I led the migration last year," not "I have led the migration last year."
The error fluent speakers make: telling the whole story in present perfect ("I have led... I have built... I have reduced..."). It sounds like a CV list, not a story, and it is wrong the moment you attach a finished time. In an interview, use present perfect only for the bridge to today ("I've led four migrations, and the one I'll describe was the hardest").
Exercise¶
Timer: 15 minutes. Items 1-2 and 4 and 7 and 10 are error correction; 3, 5, 8 are choose-the-best; 6 is a transformation; 9 is a rewrite.
- Correct: When I have joined the team in 2021, the pipeline is failing every night.
- Correct: By the time the incident call started, the on-call engineer already rolled back the change.
- Choose: We (migrated / were migrating) the billing service when the vendor announced the API deprecation.
- Correct: I was knowing the codebase well, so I took the lead on the fix.
- Choose: She (was leading / had been leading) the platform team for three years before she became a director.
- Combine into one sentence with a cause: The release failed. We had not tested the rollback.
- Correct: When I would join the company, we would have a monolith and a single database.
- Choose: I realized that I (didn't attach / hadn't attached) the runbook, so I sent it immediately.
- Rewrite as a coherent past narrative (5-6 sentences, using at least one past continuous, one past perfect): I join company 2019. Team is small. We deploy manually, 2 hours. Nobody automate. I write pipeline. Deploy time drop to 10 minutes.
- Correct: I have led the migration last year and it saved us two million dollars.
Answers and explanations
- When I joined the team in 2021, the pipeline was failing every night. Finished time marker ("in 2021") plus a story: past simple for the event, past continuous for the background state of affairs.
- ...the on-call engineer had already rolled back the change. The rollback happened before the call started, so past perfect. (In casual speech "already rolled back" is heard, but in a timed interview, marking the sequence is the point.)
- were migrating. The migration was in progress (background); the announcement interrupted it (event).
- I knew the codebase well... Know is stative, no continuous.
- had been leading. The point is duration before a past moment (becoming a director). "Was leading" would place the leading at the same time as becoming a director.
- The release failed because we hadn't tested the rollback. Past perfect for the earlier cause. "...because we didn't test..." is acceptable in casual speech but loses the sequence.
- When I joined the company, we had a monolith and a single database. "When I would join" is not English; would cannot express a single past event, and cannot express a state (have).
- hadn't attached. The omission preceded the realization; the runbook was not attached at that earlier point. "Didn't attach" implies the not-attaching and the realizing were simultaneous.
- Model: I joined the company in 2019. The team was small, and we were deploying manually, which took two hours. Nobody had automated it because everyone was busy firefighting. I wrote a pipeline in my first month, and deploy time dropped to ten minutes. Note: past simple carries the story, past continuous the ongoing manual routine, past perfect the earlier non-action.
- I led the migration last year and it saved us two million dollars. "Last year" blocks present perfect. Alternative bridge: "I've led four migrations. Last year I led the one that saved two million."
Use it¶
Write or say three sentences about a real project: one background (past continuous), one earlier cause (past perfect), one outcome (past simple). Example frame: "We were [ongoing situation] when [event]. It happened because we hadn't [earlier action]. So I [action], and [result]."
Day 2 — Vocabulary: Achievement verbs (spearheaded, orchestrated, streamlined)¶
⏱ 30 min · Tue · 10 min table, 5 min collocations, 10 min cloze, 5 min use it.
| Word | Part of speech | Meaning | Example |
|---|---|---|---|
| spearhead | verb | To lead an initiative from the front, usually a new or difficult one. Implies taking responsibility for direction, not just participating. | She spearheaded the move from batch reconciliation to event-driven settlement across three regions. |
| orchestrate | verb | To coordinate many people, systems or events so they work together as a whole. Stresses coordination, not personal execution. | He orchestrated a zero-downtime cutover involving six teams and two external carriers. |
| streamline | verb | To make a process or system simpler and more efficient by removing unnecessary steps. | We streamlined the onboarding flow by removing four manual approvals, which cut lead time from nine days to two. |
| galvanize | verb | To shock or inspire people into action, often a team that was stuck or indifferent. | The outage galvanized leadership into funding the resilience roadmap. |
| institutionalize | verb | To make a practice a permanent, standard part of how an organization works. | We institutionalized blameless postmortems by adding them to the definition of done for every Sev-1. |
Collocations and word family¶
- spearhead an initiative / a migration / a push / an effort; spearhead is a verb only (the noun form is "spearhead" but rare in business).
- orchestrate a rollout / a cutover / a response / a campaign; noun: orchestration; also the tool sense (workflow orchestrator).
- streamline a process / operations / a workflow / onboarding; adjective: streamlined; noun: streamlining.
- galvanize support / a team / the organization into action; noun: galvanization (rare).
- institutionalize a practice / a process / knowledge; noun: institutionalization; adjective institutional.
- Register note: in a resume, verbs should match your real role. Spearheaded = you led it; contributed to / helped deliver = you were part of it. Overclaiming is the most common way strong candidates lose credibility in follow-up questions.
Exercise¶
Timer: 10 minutes. Fill each gap. Some gaps use review words from earlier weeks.
- After the audit, the CTO wanted to ______ the change-approval process; it involved seven sign-offs for a config tweak.
- She ______ the response to the customs-system outage, coordinating support, engineering and three carriers.
- I volunteered to ______ the effort to move the monolith's order module into its own service.
- The near-miss ______ the team into finally fixing the flaky integration tests.
- To ______ postmortems, we made them a mandatory step in every incident ticket template.
- Which is stronger evidence of leadership on a resume: "helped with" or "spearheaded"? Explain in one sentence, and say when the stronger verb becomes a risk.
- Review: we chose to ______ the risk of the migration by running both systems in parallel for a month. (mitigate / de-risk / champion)
- Review: a good staff engineer will ______ blocked teams instead of waiting to be asked. (unblock / assess / prioritize)
Answers and explanations
- streamline. Removing unnecessary steps from a process.
- orchestrated. Many parties to coordinate.
- spearhead. Leading a new initiative.
- galvanized. A jolt that produces action.
- institutionalize. Making a practice permanent.
- Spearheaded signals ownership and direction, but it becomes a risk when you did not lead: an interviewer will ask "How did you decide the approach?" and you will have no answer.
- de-risk (best) or mitigate. Both work; "mitigate the risk" is fine; "de-risk the migration" is the more natural collocation for a project. Champion does not fit.
- unblock. To remove obstacles for others.
Use it¶
Say aloud, then write, three sentences using three of the five verbs about your real work. Check each: could you answer two follow-up questions about it? If not, downgrade the verb.
Day 3 — Speaking: Mock behavioural answers with STAR¶
⏱ 30 min · Wed · 5 min structure, 10 min prep (notes only), 3 x 90 s answers, 5 min self-check.
Prompt. Answer each in 75-90 seconds. Timer visible. Record on your phone.
- "Tell me about a time you disagreed with a senior stakeholder on a technical decision."
- "Tell me about a project that didn't go as planned."
- "Tell me about a time you had to influence a team you didn't manage."
Structure: STAR with time budgets.
| Part | Share | What goes in it | Trap |
|---|---|---|---|
| Situation | 10% (8 s) | One sentence: where, when, what was at stake | Long backstory |
| Task | 10% (8 s) | Your specific responsibility ("I was accountable for...") | Describing the team's task |
| Action | 55% (45 s) | What you did: 3 verbs, each with a why. Use "I", not "we" | "We" everywhere; interviewer cannot see your contribution |
| Result | 25% (20 s) | A number or an observable change, plus what you would do differently | "It went well" |
Signposts: "The situation was...", "My role was...", "I did three things...", "As a result...", "Looking back...".
Pronunciation micro-drill: the three -ed endings. Past tense and past participles end in one of three sounds.
- /t/ after voiceless sounds: launched, pushed, mapped, fixed, checked (one syllable, ends in /t/).
- /d/ after voiced sounds: rolled, scaled, moved, ensured, owned (one syllable, ends in /d/).
- /ɪd/ after /t/ and /d/: escalated (ES-ca-LAY-ted), decided (de-CI-ded), wanted, needed, spearheaded (SPEAR-head-ed).
Say five times each without adding a syllable to worked, asked, launched. Then say the sentence: "I decided, I escalated, I pushed, I fixed, and we launched." The two -ed syllables in "decided" and "escalated" must be audible; the other three must not add a syllable.
Self-check
- Each answer finished inside 90 seconds.
- I said "I" for actions, at least five times per answer.
- The Result contained a number or an observable change.
- I used past simple for events and at most one past perfect for an earlier cause.
- The -ed endings in decided / escalated had the extra syllable; worked / asked / launched did not.
Day 4 — Idioms & phrasal verbs: Interview idioms (hit the ground running, go the extra mile)¶
⏱ 30 min · Thu
| Expression | Meaning | Example |
|---|---|---|
| hit the ground running | Start a new job or task and be productive immediately, without a long learning period. Neutral, very common in interviews. | With my experience in carrier integrations, I can hit the ground running on your customs platform. |
| go the extra mile | Do more than is required. Neutral, positive; overused, so back it with an example. | When the vendor missed the deadline, I went the extra mile and wrote the adapter myself over the weekend. |
| get a lot of bang for your buck | Get excellent value or results relative to the size of the investment or team. Informal, mostly US. | Our team of four gets a lot of bang for its buck; we ran the entire tracking stack. |
| a jack of all trades | Someone who can do many different jobs reasonably well, often used of small-team generalists. Neutral to informal. | In the early days I was a jack of all trades: architect, on-call, and release manager. |
| step into the breach | To take action to help in a difficult situation, often by doing someone else's job when it is suddenly needed. Neutral to slightly formal. | When our tech lead left, I stepped into the breach and ran the incident process until we hired a replacement. |
Exercise¶
Timer: 10 minutes.
- Match the situation to the best expression: (a) A two-person team supports a system used in 40 countries. (b) You joined mid-project and shipped in week two. © You handled tasks outside your job description. (d) The manager resigned and you took over. (e) You covered SRE, product and QA for a year.
- Fill: "My onboarding was quick; I was able to ______ the ground ______ from day one."
- Fill: "I don't just meet deadlines; I ______ the extra ______."
- Choose the best: "When our lead left, I (stepped into the breach / stepped out / backed down) and took over the roadmap."
- Rewrite more idiomatically: "Our team is small but we deliver a lot."
- Rewrite more idiomatically: "I quickly started to be productive after joining."
- Which sounds the least natural in an interview: "I go the extra mile every single day" or "Last quarter, I went the extra mile by..."? Explain.
- Choose: "I joined a startup where I was (a jack of all trades / a trade jack) as the only backend engineer."
Answers and explanations
- (a) get a lot of bang for your buck; (b) hit the ground running; © go the extra mile; (d) step into the breach; (e) a jack of all trades.
- hit / running.
- go / mile.
- stepped into the breach. Step out means to leave; back down means to withdraw from a position.
- "Our team gets a lot of bang for its buck."
- "I hit the ground running."
- The first: a general claim with no evidence. Idioms in interviews are only credible attached to a specific story; "last quarter... by..." is the model.
- a jack of all trades. "A trade jack" is not a real expression.
When NOT to use them
Do not stack idioms: two in one answer is charm, four is a script. Avoid go the extra mile as a self-description; let the story prove it. In writing (resume, profile), replace idioms with facts: not "hit the ground running" but "shipped the first production feature in week two." Non-native interviewers may not know bang for your buck; watch their face and add a plain restatement if needed.
Day 5 — Writing: Resume and profile bullet points¶
⏱ 30 min · Fri · 5 min read, 15 min rewrite, 10 min compare.
Bad draft (five bullets from a Staff Engineer resume):
- Responsible for the migration of the payments service to microservices architecture
- Worked with multiple teams to improve system performance
- Helped in reducing costs by using cloud optimization techniques
- Was involved in incident management and on-call rotation
- Team player who is passionate about delivering high quality software in a fast paced environment
Task. Rewrite each bullet to (a) start with a strong past-tense verb (from this week or others), (b) include a scale or a number (invent plausible ones for the exercise; in real life use your true numbers), © show your specific action and its outcome, (d) be one line (maximum 25 words), (e) contain no clichés (team player, passionate, fast-paced). Bullet 5 should be replaced by a claim with evidence, or cut.
Model answer and what changed
- Spearheaded the migration of the payments service (2M transactions/day) from a monolith to nine services, cutting deploy time from 2 hours to 12 minutes.
- Orchestrated a six-team performance initiative that reduced p99 checkout latency from 1.8 s to 420 ms.
- Cut cloud spend by 31% ($1.2M/year) by right-sizing compute and moving cold data to tiered storage.
- Redesigned the on-call rotation for 14 engineers and introduced blameless postmortems, reducing mean time to recover from 95 to 38 minutes.
- Institutionalized design reviews across four teams, resulting in a 40% drop in Sev-1 incidents over two quarters.
What changed and why
- Verb first, and in the past tense. "Responsible for", "worked with", "helped in" describe a duty or presence; a strong verb describes your act. (Current role bullets may use present tense; keep the tense consistent within a role.)
- Number, scale, outcome. Each bullet has a size (2M transactions/day, 14 engineers) or a result (31%, 420 ms). Recruiters skim for numbers.
- Your action, not the team's. "Was involved in" is invisible. "Redesigned" and "introduced" say what you did.
- Parallel structure. All bullets follow verb + object + measurable result; this is easy to scan.
- Cliché removed and evidence added. Bullet 5 is replaced by an evidenced claim; "passionate about quality" claims cannot be checked, "40% drop" can.
Day 6 — Speaking record: Interview answers, 2-minute talk¶
⏱ 30 min · Sat · 5 min prep, 2 min record, 5 min replay and score, 15 min shadowing, 3 min log.
Prompt. Record a two-minute answer to: "Tell me about the achievement you are most proud of in your career, and what it shows about how you work." Use STAR for the first 90 seconds and spend the last 30 seconds on "what it shows" (the pattern behind the story). Include at least two achievement verbs from this week, one past perfect, one past continuous.
Structure. 0:00 hook sentence ("The most demanding thing I've done was..."); 0:10 Situation + Task; 0:25 Action (three moves); 1:15 Result with number; 1:30 Lesson, tied to how you'd work in the target role.
Rubric (score each 1-4; total /24)
| Criterion | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| Clarity | Listener lost the point | Point clear only after effort | Clear main point; some detours | Immediately clear, no detours |
| Structure | No visible structure | Partial STAR | Clear STAR; timing uneven | STAR with proportional timing and a bridge |
| Fluency | Frequent long pauses or restarts | Regular hesitation, some self-correction | Occasional hesitation, recovers well | Smooth, deliberate pauses only |
| Grammar accuracy | Errors obscure meaning | Frequent errors in tense | Few errors, all recoverable | Almost error-free; correct narrative tenses |
| Vocabulary range | Repetitive, basic | Some precise words | Varied, mostly precise | Precise and varied; verbs match the claim |
| Pronunciation | Hard to follow | Understandable with effort; -ed and stress issues | Clear; minor stress issues | Clear, natural stress and -ed endings |
Shadowing task (15 min). Pick a TED talk in which the speaker tells a personal story (past tense narration is exactly what you need). Choose a 60-second passage, listen to it three times, then speak along one sentence behind the speaker, copying the pauses and stress. Then repeat without the audio and record. Also good: a BBC Learning English "6 Minute English" episode; follow the transcript on the page.
Log your score: Week 21 record: __/24 · weakest criterion: ______ · recording file: ______ in your log.
Day 7 — Soft skills + weekly review: Self-advocacy without arrogance¶
⏱ 30 min · Sun · 10 min scenario, 10 min recap, 10 min self-score and error log.
Scenario. You led the redesign of the tracking-event pipeline last year; it cut delivery-status latency by 70%. In a calibration prep chat, your manager says, "The committee thinks it was a team effort and that Priya's group did the hard part." You believe your part was decisive, but Priya's team did do real work. The promotion case depends on this.
Task. Write a 150-word response you would say or send to your manager. Constraints: assert your specific contribution with evidence; credit the other team by name; ask for a concrete next step; no defensiveness, no comparing yourself to Priya.
Model response and annotation
Thanks for telling me directly; I'd like to make the picture more precise. The pipeline was a shared effort, and Priya's team owned the ingestion layer, which was essential. My part was the design decision to move from polling to event streaming, which I proposed, prototyped and defended in the architecture review; I also led the cutover plan and the rollback drill. The 70% latency reduction comes from that design, and the review notes and benchmark are in the RFC. Could I send you a one-page summary that separates the two contributions, with links? And if it would help the committee, I'm happy to ask Priya to confirm the split. My aim is an accurate picture, not a bigger share of credit.
Techniques used: (1) Acknowledgement first removes the fight ("shared effort... essential"). (2) "My part was" + three concrete verbs (proposed, prototyped, defended) is I-statement evidence. (3) A number and a document make the claim checkable, not boastful. (4) Offering a third-party confirmation signals confidence; arrogance avoids being checked. (5) A closing statement of intent frames the ask as accuracy, not rivalry. (6) A concrete next step (one-page summary) makes it easy for the manager to help.
Weekly recap (20 items)¶
Answer aloud first; then open the answers.
- Which tense sets the background of a story and which moves it forward?
- Correct: I have joined in 2020.
- Correct: We were knowing the risks.
- When is past perfect necessary, not decorative?
- Why is "we would have a monolith" wrong?
- Difference between had worked and had been working?
- Define spearhead.
- Define orchestrate and give a collocation.
- Define streamline.
- What does galvanize imply about the team's starting state?
- Define institutionalize and give an example.
- Hit the ground running means?
- Go the extra mile: why is it risky as a self-description?
- Complete: Our team of four ______ above its ______.
- A jack of all trades means?
- Difference between step into the breach and step in?
- What are the four STAR components and the target time share for Action?
- Pronounce: decided, worked, escalated, asked (which have an extra syllable?).
- Why should a resume bullet start with a past-tense verb?
- Name two techniques for self-advocacy without arrogance.
Answers
- Past continuous (background) and past simple (forward-moving events).
- I joined in 2020. (Finished time marker.)
- We knew the risks.
- When the sequence would be unclear, or when the earlier event explains the later.
- Would describes repeated actions, not states; and "a monolith" is a state.
- Had worked = completed earlier action; had been working = emphasizes duration or the visible effect.
- To lead an initiative from the front.
- To coordinate many people or systems; orchestrate a cutover / rollout.
- To make a process simpler and more efficient.
- That they were stuck, indifferent or divided before.
- To make a practice permanent; institutionalize blameless postmortems.
- To be productive from the start.
- It is a claim with no evidence; use it only after a specific example.
- punches above its weight.
- To have many different roles at once.
- Step into the breach = take on an urgent, unfilled responsibility, often suddenly; step in = intervene, often temporarily and less urgently.
- Situation, Task, Action, Result; Action around 55%.
- decided and escalated (/ɪd/); worked and asked have no extra syllable.
- It shows what you did (action), and lets recruiters scan; nouns like "responsible for" describe duty.
- Acknowledge others first and give specific evidence (a number, a document); also offer verification and a concrete next step.
Self-score¶
- I can tell a 90-second story using at least three narrative tenses correctly.
- I know which of my resume verbs I could defend under follow-up questions.
- I used 2 or more achievement verbs in speaking without hesitation.
- My Day 6 recording scored 16/24 or above (20+ target).
- My Day 7 response contained a fact, a number and a next step.
Error log prompt. Write down your top 3 recurring mistakes from this week (for example: present perfect with a finished time, missing -ed syllable, "we" for "I"), each with a corrected sentence. Add them to your master error log; Week 23 uses it.