How to Use This Book
Each chapter follows the same structure, so once you're familiar with it, you can move through the book efficiently or jump directly to the chapter you need most.
Every chapter opens with a real-world scenario and a short interview excerpt — read these first, even if you're tempted to skip to the expressions lists. The language means more once you've seen it used in context.
You'll then find key vocabulary, useful expressions (organized by what you want to do, not by grammar), language patterns, and a communication strategy section explaining the thinking behind the language. Each chapter also flags a common mistake, offers Say This, Not That comparisons, and closes with practice exercises, a role-play, and a Kognixr Challenge — a more demanding, realistic task.
You don't need to complete every exercise type in every chapter to benefit from it. If you're short on time, prioritize the scenario, the Useful Expressions, and the Role-Play — that combination gives you the fastest route to real spoken confidence.
The Reference Section at the back is designed to be used long after you've finished the book — as a quick lookup when you're preparing for a real interview.
Introduction
Most professionals who read this book already have the experience the job requires. That's rarely the problem an interview reveals. The problem is usually that years of real, substantial work don't automatically translate into a clear, confident answer when someone asks about them in English, under time pressure, with a stranger watching.
You know your own achievements. You understand your own value. What often gets lost is the language that carries that understanding across to someone else — the specific phrases for describing responsibility without sounding like a job description, for claiming credit without sounding boastful, for admitting a weakness without undermining your candidacy, for saying "I don't know" without sounding unprepared.
That functional language — the how of interviews, not just the what — is what this book teaches. You'll follow a small recurring cast of professionals, including Renata Souza, an FP&A manager from São Paulo preparing for her first English-language interview for an international role, and a wider set of specialists and career-changers across later chapters. The language is drawn from how real interviews actually go, including the hesitations, the follow-up questions that go somewhere unexpected, and the moments where a candidate has to think on their feet — not textbook English cleaned of all its texture.
By the end, the goal isn't that you'll sound like a native speaker. It's that you'll be able to walk into an interview in English and represent your own experience the way you already can in your own language: clearly, credibly, and with the confidence that comes from knowing exactly what you want to say.
The Learning Framework
Throughout this book, you'll notice the same five-part rhythm running underneath almost every chapter and every interview: Prepare → Present → Support → Adapt → Close.
You prepare your professional story and the language you're likely to need, in advance. You present that story clearly when the interview opens. You support your claims with specific evidence — achievements, numbers, examples — rather than general statements. You adapt in real time to follow-up questions, unexpected turns, and the parts of the conversation you couldn't fully predict. And you close the interview deliberately, asking good questions and following up afterward, rather than letting the conversation simply end.
This isn't a rigid formula to recite. It's a way of noticing that good interview communication has a shape — and once you can see that shape, it gets easier to know what to do at any stage, in any interview, in any language.
CH. 01 |
What Makes Professional Interview English Different
An interview isn't a conversation and it isn't a speech — it's something in between, with its own rhythm. This chapter is about recognizing that rhythm so you stop measuring yourself against the wrong standard.
LEARNING OBJECTIVES By the end of this chapter, you will be able to: ✓ recognize how interview English differs from everyday workplace English ✓ answer at the right length — not too short, not padded ✓ sound direct and natural instead of memorized ✓ judge your own answers against a clearer standard than "good English" |
◆ Real-World Scenario
Renata Souza has interviewed for jobs before — twice in Portuguese, at companies in São Paulo where she has spent her whole career in financial planning and analysis. Tomorrow is different: a first-round video interview for a Finance Manager role at a consumer goods company headquartered in the Netherlands. The job would be a real step up. Her English is genuinely good — she reads reports in English every week and handles calls with regional offices without difficulty.
Still, she's nervous in a way that surprises her. She calls Grace Adeyemi, a friend from a previous company who now works in talent acquisition for a European tech firm and has sat on the other side of hundreds of interviews.
◆ Interview Excerpt
Renata I keep rewriting my answer to "tell me about yourself." I've written maybe six versions and I still don't like any of them.
Grace What does version six sound like?
Renata Honestly? It sounds like an essay. Very correct, very complete, and completely unlike how I actually talk.
Grace That's the thing nobody tells you — interview English isn't about being more correct than usual. It's actually closer to how you'd explain your work to a smart colleague at lunch, just with the sloppy parts cleaned up.
Renata So less formal than I've been making it.
Grace Less formal, and shorter. You don't need to explain your entire career history. You need one clear paragraph that makes them want to ask a follow-up question.
Renata That's hard for me to judge. How do I know if an answer is too short or too long?
Grace (thinking for a second) Time yourself. If "tell me about yourself" takes you past ninety seconds, you're probably including detail they didn't ask for. If it takes you fifteen seconds, you've probably left out the part that actually matters — what you're looking for now.
Renata And the memorized feeling — how do I get rid of that?
Grace Stop writing full sentences. Write down four or five ideas in the order you want to say them, and let the sentences come out differently each time you practice. If it's word-for-word, it'll sound word-for-word.
◆ Understand the Communication
Renata's instinct — to write a careful, complete, grammatically correct answer — is exactly what produces the problem she's trying to avoid. Interview English rewards clarity and direct answers over completeness and formality. A technically flawless paragraph that answers a slightly different question than the one that was asked, or that takes three times longer than it needs to, reads as less confident than a shorter, plainer answer that lands directly.
Grace's advice points at two separate skills that often get confused: language accuracy and interview register. Renata's grammar was never the issue. The issue was that she was applying the wrong register — the register of a written report — to a spoken, interactive situation. Interview English sits closer to confident spoken English than to formal written English, even though the vocabulary is professional and the structure is more careful than casual conversation.
Notice also that Grace doesn't tell Renata to memorize a better script. She tells her to prepare ideas, not sentences, and to let the wording vary. This is the difference between preparation and memorization, and it's a distinction this book returns to often: prepared candidates sound natural because they know what they want to say, not because they've rehearsed exactly how to say it.
◆ Key Vocabulary
TERM | MEANING | EXAMPLE |
register | the level of formality appropriate to a situation | "Interview register is more formal than a chat with a colleague, but less formal than a written report." |
to land (an answer) | for an answer to feel clear, direct and convincing | "That answer really landed — it was short and specific." |
to pad (an answer) | to add unnecessary detail to make an answer longer | "I padded my answer with details nobody asked about." |
follow-up question | a question that asks for more detail on something just said | "A good opening answer usually invites a follow-up question." |
to rehearse | to practice saying something, often word-for-word | "I rehearsed my introduction so many times it stopped sounding like me." |
to come across as | to give a particular impression | "Long answers can come across as unprepared, not thorough." |
to the point | direct, without unnecessary detail | "Her answer was short and to the point." |
small talk | brief, informal conversation before the main discussion begins | "There was two minutes of small talk before the first real question." |
◆ Useful Expressions
Answering directly without sounding abrupt
• "The short answer is yes — and here's the context."
• "In a word, yes. Let me explain why."
• "There are two parts to that, so let me take them in order."
Signaling you're about to be concise
• "To keep this brief —"
• "The headline is this:"
• "If I had to summarize it in one sentence —"
Inviting a follow-up instead of over-explaining
• "That's the short version — happy to go into more detail if it's useful."
• "I can expand on any part of that if you'd like."
• "Let me know if you want me to go deeper on the numbers."
◆ Language Patterns
A small set of structures does most of the work of sounding direct rather than rehearsed. Notice that none of these require complex grammar — they work because of what they do, not how they're built.
1. Lead with the answer, then explain. — "Yes, I have managed a team before. For the last two years, I've led a group of five analysts."
2. Signal length in advance. — "There are two reasons for that, and I'll keep both brief."
3. Offer to expand rather than assuming you should. — "I can walk through the details if that's useful, or keep it high-level."
These patterns aren't a script. They're small tools you can reach for in the moment, which is exactly what makes them more useful than a memorized paragraph — they work no matter what the actual question turns out to be.
COMMUNICATION STRATEGY Judge your answers by length and directness, not just grammar. Most professionals preparing for an English-language interview focus almost entirely on grammar and vocabulary. Those matter, but they're rarely what separates a strong answer from a weak one. What usually separates them is whether the answer is the right length and whether it actually addresses the question asked. Before you worry about a more sophisticated word, check whether your answer is direct, proportionate, and free of unnecessary padding. |
COMMON MISTAKE Writing and memorizing full answers in advance. It's tempting to prepare by writing out complete, polished paragraphs and learning them closely to word-for-word. The result usually sounds exactly like what it is — a recited text, not a response. It also tends to fall apart the moment the interviewer asks the question slightly differently than expected. Prepare ideas and structure instead of sentences, and practice saying them a different way each time. |
◆ Say This, Not That
Less effective: "So, I have been working in the field of financial planning and analysis for approximately seven years now, and during this time I have had the opportunity to develop a wide range of skills across various areas of financial management, including budgeting, forecasting, and variance analysis, which I believe have prepared me well for a role such as this one..."
More effective: "I've spent the last seven years in financial planning and analysis, most recently leading the forecasting process for a retail business with operations across three countries. What's brought me here is wanting to apply that experience somewhere with a bigger international footprint."
◆ Practice
Exercise 1 — Recognition
Which of the following answers to "Do you have experience managing a budget?" is the strongest opening line? Choose the best option and explain briefly why.
1. "Well, that's an interesting question, because budgets can mean different things in different organizations, so let me first clarify what I mean by budget management..."
2. "Yes — I've managed an annual budget of around four million reais for the past three years."
3. "I think so, yes, I mean I've been involved in some budget-related work, though it wasn't always the main part of my role."
Exercise 2 — Completion
Complete the sentence with an appropriate directness marker: "________, I've led cross-functional projects with teams in four different countries."
Exercise 3 — Application
Time yourself answering "Tell me about yourself" out loud, without writing anything down first. If it runs past ninety seconds, identify one detail you could cut.
ROLE-PLAY Situation: You've just been asked, "Can you tell me a bit about your background?" by an interviewer you've never met. Objective: Answer in under ninety seconds, leading with what's most relevant to the role, without reading from notes. Participants: You (Role A) and a colleague (Role B) who times your answer and gives one piece of feedback on length. Communication challenge: Resisting the urge to explain your entire career chronologically. Useful language to consider: to keep this brief, the short version is, happy to go into more detail. |