The Interview: Selling Your Achievements – inversion for emphasis
About this lesson
Students use inversion with negative adverbials in this C1 English for IT lesson plan to sell their achievements at a job interview without bragging.
- Grammar
- Inversion after negative and limiting openers (Rarely do we deploy on a Friday), conditionals without if (Had I known…) and so or such at the front.
- Topic
- A behavioral interview for a senior backend role at a fictional payments startup, answered in STAR form, with track record, buzzword and humblebrag.
- Activities
- A job ad to read, an interview to hear, self-checking drills, a recruiter chat and boxes of STAR questions, then a project note to write and an answer to record.
What's inside
Chapter 1Warm-up: The Hot Seat
Chapter 2Reading: The Job Ad, Decoded
Chapter 3Listening: Ethan Meets Priya
Chapter 4Grammar: Never Have I Sounded So Sure
- Study the scheme: inversion for emphasisGrammar schemeTry it
- Choose the correct answer: what does it mean?QuizUnlock
- Choose the correct optionChoose the optionUnlock
- Drag the words into the gapsDrag and dropTry it
- Fill in the gaps: rewrite each sentence with an inversionFill in the gapsUnlock
- Fill in the table: conditionals without ifFill in the tableUnlock
Chapter 5Speaking: Your Turn in the Hot Seat
Chapter 6Homework: Sell It, Don't Oversell It
Vocabulary
10 words and phrases from the lesson, each with a picture and audio in edio.
+7 more with pictures and audio in the lessonMore words
- high-stakes
- buzzword
- quantify your impact
- stakeholder buy-in
- toot your own horn
- humblebrag
- learn the hard way
Grammar: inversion for emphasis
Inversion puts a negative or limiting phrase first, and then the auxiliary jumps ahead of the subject, as in a question: Never have I seen such a clean cutover. The order sounds formal and emphatic, which is why a candidate saves it for the points an interviewer should remember. Formal conditionals invert too, without if: Had I known about the bug…
Inversion for emphasis
Put a negative or limiting phrase first, and the auxiliary comes before the subject, as in a question.
Do, does, did, or the auxiliary you have
Present simple verbs take do or does, past simple ones did: Never did we lose a single payment. Perfect, continuous and modal verbs move the auxiliary they already have, and be swaps with its subject. When the phrase isn't first, the order stays normal: We rarely deploy on Fridays.
The pattern
Negative or limiting phraseauxiliarysubjectmain verb
Rarely do we deploy on a Friday.
Never have I seen such a clean cutover.
Not only did Ethan fix the timeouts, but he also stopped the double charges.
Which auxiliary?
- Present simple → do / does: Seldom does a deploy fail twice in a row.
- Past simple → did: Never did we lose a single payment.
- Perfect, continuous or modal → move the auxiliary you already have: Never have I seen… Under no circumstances should you…
- be as the main verb → no do: Rarely is the root cause that obvious.
- Phrase not first → normal word order: We rarely deploy on Fridays. I have never seen that.
Never, not only, only after: the openers
Not only takes but… also later, no sooner pairs with than, and hardly or scarcely with when. After only after, only when or not until, the main clause inverts, not the time phrase: Only after the rollback did we find the bug.
Negative and limiting openers
| Opener | Emphatic | Plain |
|---|---|---|
| Never / Rarely / Seldom | Seldom do we roll back a release. | We seldom roll back a release. |
| Not only … but … also | Not only did I lead the migration, but I also trained the on-call team. | I led the migration and also trained the on-call team. |
| Little | Little did we know that the cache was hiding the bug. | We had no idea that the cache was hiding the bug. |
| Under no circumstances / At no time | At no time was card data exposed. | Card data was never exposed. |
| Only after / when / by … | Only after the rollback did we find the bug. | We found the bug only after the rollback. |
| Not until … | Not until the canary failed did we notice the leak. | We didn't notice the leak until the canary failed. |
| No sooner … than | No sooner had we shipped the fix than an alert fired. | As soon as we shipped the fix, an alert fired. |
| Hardly / Scarcely … when | Hardly had I joined when the pager went off. | I had only just joined when the pager went off. |
Only… / Not until…: invert the main clause
Keep the time or method part in normal order and invert the main clause: Only when we added tracing did the pattern become clear. Only by sharding the table were we able to scale.
Inverted conditionals: had, should, were
A formal condition can drop if and start with had, should or were: Had I known about the bug…, Should you need anything else…, Were we to lose the primary region… The negative keeps not after the subject: Had we not caught it, never Hadn't we.
| With if | Inverted (more formal) |
|---|---|
| If I had known about the bug, … | Had I known about the bug, … |
| If we hadn't caught it in staging, … | Had we not caught it in staging, … (never: Hadn't we) |
| If you (should) need anything else, … | Should you need anything else, … |
| If we were to lose the primary region, … | Were we to lose the primary region, … |
So and such at the front
So + adjective or adverb can come first, then the inverted verb and a that clause: So successful was the migration that we switched off the old ledger early. Such was + a noun works the same way: Such was the load that we doubled the number of pods.
- So successful was the migration that we switched off the old ledger early.
- So quickly did the queue grow that the pods ran out of memory.
- Such was the load that we doubled the number of pods.
- Plain: The migration was so successful that we switched off the old ledger early.
One or two per answer
Inversion is formal, so save it for your strongest points: one or two per interview answer, never five in a row. Most slips put the auxiliary after the subject (Not only I did lead…) or mix up the partners: No sooner… than, Hardly… when.
Typical mistakes
Not only I did lead the migration, but I also trained the team.
Not only did I lead the migration, but I also trained the team.
The auxiliary comes before the subject.
No sooner had we shipped the fix when an alert fired.
No sooner had we shipped the fix than an alert fired.
No sooner … than.
Hardly had I joined than the pager went off.
Hardly had I joined when the pager went off.
Hardly / Scarcely … when.
No sooner we shipped the fix than an alert fired.
No sooner had we shipped the fix than an alert fired.
No sooner + had + subject + past participle.
Don't overdo it
Inversion is formal and emphatic. In an interview, use one or two per answer, for your strongest points. Five in a row sounds pompous, like a press release.
Try the inversion exercises
Try them yourself: these are the same exercises your students do in edio.
What's in the lesson
- 12 auto-checked exercises
- 3 games
- 2 teacher-checked tasks
- 1 real-life document
- 1 grammar scheme
- 1 set of word cards
- 1 audio clip
- 1 picture
- 1 transcript
The main objectives of this lesson are to:
- stress a point with a negative or limiting opener and inverted order: Rarely does a week go by without a schema change.
- use not only… but also, no sooner… than and hardly… when: Not only did we cut checkout errors, but we also made refunds faster.
- drop if from a formal conditional: Had I checked the dependencies first, I'd have caught it. Should you have any questions, email me.
- answer a behavioral interview question in STAR form, with one or two inversions for the strongest points
Lesson 14 is the middle of Retros, interviews and AI, the final unit of English for IT C1 · Across the Company, which moves from a retro to a job interview to a team policy. Lesson 3 gave emphasis with cleft sentences, and lesson 4 set conditions with provided and unless; inversion now does both. Lesson 15 then closes the course with formal rules. At an interview, one emphatic sentence about a real result beats a list of adjectives.
Students spin a wheel of interview questions, learn ten words with pictures and audio, from track record to learn the hard way, and match them to meanings. The job ad for a senior backend engineer gives the stack, the interview steps and what to send instead of a cover letter. In the AI-voiced interview, Priya asks Ethan about a fix under pressure and a mistake, and students match each STAR stage to his first answer. After the scheme come five exercises that check themselves, ending with a table that rewrites if-clauses without if. Students then answer a recruiter's LinkedIn messages in a chat and open boxes of Tell me about a time when… questions.
Homework begins with two self-checking exercises: inverted or normal word order, and a memory game of verbs and phrases. Students then write the project note the job ad asks for, or a LinkedIn About section, with exactly two inversions, and record a STAR answer about something they delivered. Both go to the teacher for review.
- Grammar:
- inversion · negative adverbials · conditional inversion
- Topic:
- job interviews · STAR method · career · self-presentation
Teaching tips
- Start from plain achievements: students write three flat sentences about their own work, such as We seldom roll back releases, then upgrade only the strongest one with an inversion.
- Run a bragging check: pairs read their STAR answers aloud, and the listener raises a hand at any humblebrag, buzzword or third inversion in one answer.
- For one-to-one clients facing a real interview, take the ad they are applying to and turn each requirement into a Tell me about a time when… question to answer in STAR form.
- Pause the interview after each STAR stage: students note the situation, task, action and result, and guess the next stage before they hear it.
Liked it?
Teach the whole lesson in edio
23 exercises in 6 chapters, ready to teach. edio is an online platform for language schools and teachers: ready-made interactive lessons, live classes, homework and student progress in one place.
Start a free trial
7 days, no credit card.
Open the lesson
Find it in the library of 621 ready lessons. Teach it as it is, or copy any chapter into your own lessons.
Teach it live or as homework
Students work in their own accounts, in sync with you during the lesson, and the practice exercises check themselves.
The whole course: English for IT C1 · Across the Company
15 lessons at C1 for people who build software, in American English, with definitions instead of translations. The people of Kestrel Cloud, a fictional payments startup, write updates, reviews, RFCs and postmortems, explain tech to non-tech colleagues and negotiate scope. Real cases include the CrowdStrike outage and the xz backdoor.See the course
Unit 1 Talking to the team
async updates, code review and plain explanations: the future perfect, hedging, cleft sentences
Unit 2 Shipping and incidents
estimates, releases and outages: conditionals without if, phrasal verbs, modal perfects
Unit 3 Security and design
advisories, trade-offs and RFCs: passive reporting structures, concession and contrast, nominalization
Unit 4 Docs, metrics and meetings
READMEs, dashboards and follow-ups: participle clauses, describing trends, reporting verbs
Unit 5 Retros, interviews and AI
looking back and ahead: wish and would rather, inversion, formal obligation and permission
Lesson 13The Retro: What Went Wrong This QuarterWish, would rather and it's high time
Lesson 14 · you're hereThe Interview: Selling Your AchievementsInversion for emphasis
Lesson 15AI at Work: Writing the Team's RulesObligation and permission in formal rules











