I got rejected from 37 international jobs. Then I changed how I practiced English.

I keep a spreadsheet. Column A is the company name. Column B is the role. Column C is how far I got. Column D is what I think went wrong.

Thirty-seven rows. Thirty-seven international companies. Thirty-seven rejections.

The pattern in Column C is always the same: Resume screen — passed. Technical test — passed. First interview — rejected.

I am a senior product designer from Kyiv. I have eight years of experience, a portfolio that has won awards, and client work for companies most people in tech would recognize. I relocated to Warsaw after February 2022 and immediately started applying for remote positions at international companies — the kind that pay in dollars or euros, run their standups in English, and post on LinkedIn about being "globally distributed."

My English is B2, trending toward C1. I can read documentation, write design specs, and follow a product meeting without subtitles. My grammar is solid. My vocabulary is professional. On any written English test, I perform well.

But something happens to me in interviews that no test can measure. The moment a hiring manager says "Tell me about yourself," a version of me shows up that I barely recognize. Hesitant. Flat. Professional in the way that a hospital corridor is professional — functional, sterile, and impossible to remember.

I know exactly what I want to say. I have rehearsed it. But the rehearsed version lives in my notes app, and the live version comes out stripped of every quality that makes me worth hiring.

The gap between what I know and what I show

Here is the thing nobody warns you about when you start applying for international remote work: the interview is not a language test. It is a performance. And performance in a second language follows completely different rules than competence.

Evelina Galaczi at Cambridge Assessment demonstrated that communicative competence in professional settings depends on four integrated skills: linguistic range, discourse management, interactive communication, and pronunciation (Galaczi & Taylor, 2018). You can have strong linguistic range — grammar, vocabulary — and still fail on discourse management, which is the ability to organize your thoughts coherently in real time, and interactive communication, which is the ability to respond naturally, build on what the other person says, and maintain conversational flow.

I had two out of four. The two that tests measure. The two that interviews don't care about.

My resume demonstrated that I could do the job. My interview demonstrated that I couldn't talk about doing the job. And in a remote company where 90% of collaboration happens through speaking — standups, design reviews, stakeholder presentations, one-on-ones — that distinction is everything.

Interview number 12: the one I still think about

A product design lead role at a Series B startup in Amsterdam. Remote-first. The hiring manager, a British woman named Claire, was warm and encouraging. She asked good questions. She gave me time to answer. Everything about the setup was designed to help me succeed.

"Walk me through a project where you had to push back on a stakeholder's direction."

I had the perfect story. A project from 2021 where a VP wanted to redesign the onboarding flow based on a competitor's approach, and I used research data to argue for a different direction. In Ukrainian, I could tell this story in three minutes with tension, resolution, and a punchline about the VP eventually presenting my approach to the board as if it were his idea.

In English, on camera, with Claire watching, what I said was approximately: "We had a project where the stakeholder wanted to change the onboarding. I showed research that the current approach was better. We kept the current approach."

Three sentences. No tension. No stakes. No evidence that I can navigate organizational complexity, which was the entire point of the question.

Claire nodded politely. I could see her typing something. The rejection email came two days later. "We were impressed with your portfolio but felt the communication style wasn't quite the fit for our collaborative team dynamic."

Communication style. Not my English. Not my grammar. My style. The way I communicate when I'm nervous, under-practiced, and trying to sound professional in a language where my professional register is the only register I have.

"Your English is a suit you never take off"

Dr. Almut Koester at the University of Birmingham studies workplace discourse. Her research on relational talk in professional settings revealed something that reframed my entire understanding of what interviews actually measure (Koester, 2006).

Professional communication, she found, is never purely transactional. Even in the most task-focused workplace conversations, roughly 30-40% of the talk serves a relational function — building rapport, signaling competence, establishing trust, projecting personality. The small talk before the meeting starts. The way you frame a disagreement. The anecdote you use to illustrate a point. The humor you deploy to defuse tension.

"Most non-native speakers," she told me, "develop excellent transactional English. They can convey information accurately. What they often lack is the relational register — the ability to sound like a person, not a report."

That was me. My English was a suit I never took off. I could deliver information. I could not deliver myself.

In an interview, delivering yourself is the entire job. A hiring manager already knows from your resume what you can do. The interview exists to answer one question: what would it be like to work with this person every day? And to answer that question, you need more than correct English. You need personable English. English with warmth, with specificity, with the kind of micro-signals that make someone think "I want this person on my team."

What 37 rejections taught me about what I was actually missing

I went through my rejection emails. Every single one that included feedback mentioned some variation of:

"Communication style." "Cultural fit." "Presence in the interview." "Struggled to elaborate." "Answers felt rehearsed."

Not one mentioned grammar. Not one mentioned vocabulary. Not one mentioned accent.

They were rejecting the performance, not the person. But because the performance was the only version of me they ever saw, the performance was the person to them.

Bonnie Norton's research on identity and language learning frames this precisely (Norton, 2013). Language learners don't just learn grammar — they negotiate identity in every interaction. When the gap between who you are and who you sound like is too wide, the result is what Norton calls "non-participation" — a withdrawal from the conversation that protects the self but costs the speaker everything.

I was non-participating in every interview. Protecting my sense of competence by saying less, hedging more, and stripping every answer down to the safest possible version of the truth. And it was costing me jobs, income, and a career trajectory I had earned but couldn't access.

The salary I calculated I was losing

I did the math one evening in my apartment in Warsaw, and the number was uncomfortable.

The international remote roles I was applying for paid between 70,000 and 110,000 euros per year. The local Polish-language roles available to me paid between 25,000 and 40,000 euros. Even averaging conservatively, the gap between what my skills were worth internationally and what I could access locally was at least 40,000 euros per year.

Over five years — the span of a typical career chapter — that gap compounds to 200,000 euros. Not because I lacked the skills. Not because I lacked the English. Because I lacked the ability to perform my competence live, in real time, in front of someone who was deciding whether to pay me what I was worth.

Forty thousand euros a year. That was the price of not being able to answer "tell me about yourself" without sounding like I was reading from a script.

My friend Katya's impossible interview

Katya is a backend engineer from Kharkiv. We relocated around the same time. Same level of English. Same frustration with interviews.

She got hired at a Dutch fintech three months before me. When I asked her what changed, she showed me her phone.

"I practice interviews every morning," she said. "Fifteen minutes. The tutor asks me behavioral questions and doesn't let me give scripted answers."

She was using Loku. Not the vocabulary drills I'd tried years ago in other apps. Loku's conversation practice — real-time speaking with AI tutors who simulate actual workplace interactions. Job interviews. Salary negotiations. Design critiques. The exact conversations I was failing at in real life.

"The first time I tried the interview scenario," Katya said, "I gave the same robotic answer I always give. The tutor stopped me and said: 'That's what you'd write in an email. Tell me like you're explaining it to a friend over coffee.'"

That distinction — email English versus coffee English — was the gap I'd been trying to close for two years without knowing it had a name.

The first week: discovering I had a voice

I started with the job interview scenarios. The tutor, Sage, asked me the question I had failed at with Claire: "Tell me about a time you pushed back on a stakeholder."

My first attempt was the same three-sentence summary I'd given in every interview. Clinical. Safe. Forgettable.

Sage responded: "I can tell that was a bigger story than you're giving me. What was actually at stake? What did it feel like when the VP pushed back?"

Nobody in a language class had ever asked me what something felt like. Grammar textbooks don't have exercises for emotional specificity. But interviews live and die on emotional specificity — on whether the hiring manager can feel the tension in your story, can sense the stakes, can picture the moment.

I tried again. Slower this time. I talked about how the VP's face changed when I showed the data. How the room got quiet. How my colleague kicked me under the table because she thought I was going too far. How the VP said "interesting" in the tone that means "I hate this but I can't argue with it."

It was messy. My grammar slipped. I reached for words. But it was a story. It had a person in it. For the first time in my English-speaking career, I sounded like someone you'd want to hear more from.

What changed in week two

Paul Nation's research on fluency development identifies a critical threshold: when learners shift from accuracy-focused to meaning-focused production, their speaking rate increases and their hesitation patterns change (Nation, 2007). Specifically, they stop pausing before content words (which signals word-retrieval difficulty) and start pausing between clauses (which signals natural thought organization).

I noticed this shift without knowing the science behind it. By week two, I was no longer searching for words mid-sentence. I was pausing in different places — natural places, the places where native speakers pause. Not because I'd memorized where to pause, but because I'd practiced enough real-time production that my brain was reorganizing its output patterns.

The scenarios helped enormously. Not just interviews — salary negotiations where the tutor played a hiring manager offering below my range. Design critiques where I had to defend a decision under pressure. One-on-ones where I had to give difficult feedback to a direct report.

Every scenario was a conversation I would actually have in an international role. And every one of them was a conversation I had never practiced in English. I had practiced ordering food. I had practiced asking for directions. I had never practiced saying "I believe I'm worth 15% more than your offer, and here's why."

Interview number 38: the one that changed everything

A senior product designer role at a Berlin-based SaaS company. Remote. The hiring manager was a Canadian named Josh, direct and fast-talking.

"Tell me about yourself."

I didn't reach for my script. I started talking. About growing up in Kyiv designing posters for my school's theater productions. About discovering that design could be a career and not just a hobby. About the war changing everything, and Warsaw becoming home, and how relocating forced me to rebuild not just my life but my professional identity from scratch.

Josh leaned forward. "That's a hell of a story," he said. "Most people give me a career timeline. You gave me a reason to care."

For the behavioral questions, I told stories. Real ones. With details and tension and the occasional joke about stakeholder politics being the same in every language. When he asked about conflict resolution, I told the VP onboarding story — the full version, with the under-the-table kick and the VP's face and the quiet room.

The call ran 15 minutes over schedule. Josh apologized for taking so much time. I had never had an interviewer apologize for talking to me too long.

The offer came four days later. Senior Product Designer. Fully remote. The salary was 85,000 euros.

Eighty-five thousand. More than double what I'd been making locally. Not because my skills had changed. Not because my portfolio had improved. Because I had finally learned to sound like the designer my portfolio said I was.

What I wish I'd known before rejection number one

The international job market doesn't test your English. It tests your ability to perform competence, build rapport, and project personality through English. These are three separate skills, and none of them develop through grammar study, vocabulary apps, or passive exposure.

They develop through production practice. Through speaking in realistic, high-pressure scenarios where someone responds to you naturally and doesn't let you hide behind safe, rehearsed answers.

Michael Byram's model of intercultural communicative competence identifies five components: knowledge, attitudes, skills of interpreting, skills of discovery, and critical cultural awareness (Byram, 1997). Traditional language learning addresses the first. Interview performance requires all five. You need to know how direct to be with a Dutch manager versus a Japanese one. You need to read the room. You need to adapt your register in real time. These are not grammar problems. They are performance problems, and they respond to performance practice.

Fifteen minutes a day with structured speaking scenarios gave me what eight years of English study never had: the experience of hearing myself be compelling in English. Of telling a story and seeing someone lean in. Of making a case and feeling it land.

The spreadsheet, updated

I added three columns to my spreadsheet after the Berlin offer. Column E: what I would have said six months ago. Column F: what I actually said. Column G: what changed.

The pattern in Column G is always the same: I stopped summarizing and started storytelling. I stopped hedging and started owning. I stopped performing "professional English speaker" and started being a professional who speaks English.

Column A now has 41 rows. Rows 38 through 41 all reached the final round. Two made offers. I accepted one.

The difference between row 1 and row 41 was not my English level. My English level barely changed. The difference was that I finally built the output channel that my input had been missing for years.

The Slack message I sent on my first day

Day one at the Berlin company. The team Slack had an introduction channel. Most new hires wrote two sentences: their name, their role, and something generic about being excited.

I wrote a paragraph. About the theater posters. About Warsaw. About how I'd applied to this company specifically because their design system had a detail I'd noticed in their public-facing product — a micro-interaction on their pricing page that most users would never notice but that told me the design team cared about craft.

Three people replied within the hour. My new manager DM'd me: "Best intro I've seen in two years. Welcome aboard."

It was the kind of message I would have written in Ukrainian without thinking. Six months ago, I would have written it in English too — in text, where I had time. But I wouldn't have said it in a standup. I wouldn't have pitched it in a meeting. I wouldn't have trusted that my live English could carry the same warmth and specificity as my written English.

Now I could. Because I had practiced. Not grammar. Not vocabulary. The skill of being myself out loud, in English, in real time.

What my career is worth now

I sit in my Warsaw apartment, working for a German company, in English, earning a salary that would have been impossible twelve months ago. My next performance review is in three months. I am already preparing for the conversation where I ask for a raise — not by memorizing phrases, but by practicing the conversation with a tutor who pushes back and makes me defend my value proposition under pressure.

If you are reading this with a browser tab open to LinkedIn jobs, filtering for "remote" and "English-speaking team," and feeling the familiar dread of another interview where you'll sound like a worse version of yourself — I want you to know: the gap is not your English. The gap is between the English you know and the English you perform. And that gap closes faster than you think.

Loku offers a two-minute quiz that builds a personalized speaking plan based on your goals. It takes 15 minutes a day. That's what closed the gap for me.

Stop preparing for interviews. Start practicing them.

Results may vary. Tessera does not provide career or financial advice.