Berlin Desk Prep for an English Coding Interview

It is Tuesday evening in Berlin, and your English-language coding interview is on Friday. You understand hash maps and can debug an API timeout, but explaining those decisions aloud takes longer than making them. Tonight’s goal is not fluent English. It is making your technical reasoning easy to follow.

Use this numbered rehearsal at your desk. Keep a text editor, a timer, and a voice recorder open. Budget roughly 70 minutes, and work in the language your interview will use.

1. Turn the interview invitation into a practice brief

Spend five minutes extracting the format from the invitation: interview length, coding environment, permitted programming languages, and whether you will discuss algorithms, system design, or previous projects. Ask the recruiter about missing details rather than guessing.

Write one sentence at the top of your notes: “I will solve a 40-minute coding problem while explaining assumptions, trade-offs, and tests in English.” Replace those details with your actual format. This sentence defines what you need to rehearse.

2. Build a small vocabulary sheet from familiar code

Open a function you understand well. Explain its inputs, output, failure cases, and complexity aloud. Whenever a missing word interrupts you, write down the idea and a simple English expression for it.

• “This value can be missing.”
• “I will keep the first occurrence and ignore duplicates.”
• “The extra memory grows with the number of unique items.”
• “This approach avoids scanning the list again.”

Limit the sheet to ten useful phrases. Prefer expressions you can produce under pressure over impressive vocabulary. Practice each phrase inside a complete explanation, not as an isolated translation.

3. Rehearse clarification before touching the keyboard

Choose an easy problem involving arrays, strings, or a data structure you already know. Set a three-minute timer and clarify the requirements before coding.

Ask about empty input, duplicate values, ordering, and expected input size where relevant. Then summarize: “My understanding is that we return one matching pair, and the input may contain duplicates. Is that correct?”

This creates a shared specification and gives you time to organize your language. If you miss a condition, request a targeted repetition: “Could you repeat the constraint on input size?” That is more useful than pretending you understood.

4. Record a 15-minute coding explanation

Start the recorder and solve the problem without pausing it. Narrate decisions rather than every keystroke: your initial approach, the invariant you are maintaining, and the reason for a change.

When you need silence, announce it: “I need a moment to check this boundary case.” When a word disappears, paraphrase: “The position after the last element.” Do not restart the recording after a mistake. Recovering is part of the practice.

Finish with two tests, including an edge case, and state time and space complexity. Explain which input quantity your complexity variable represents.

5. Review where the listener could lose the thread

Listen once without reading your code. Mark three timestamps where the explanation becomes difficult to follow. Separate technical gaps from language gaps: an incorrect invariant needs different practice from an unclear pronoun.

Rewrite only those three passages. Replace “this goes there” with named objects, and split long sentences into one claim each. Repeat the revised passages aloud. Do not spend the session correcting every article, accent feature, or minor grammatical error.

6. Run one constrained AI mock interview

Give an AI interviewer this instruction: “Ask one coding question. Wait for my response. Ask one follow-up at a time. Do not reveal the solution. At the end, identify unclear assumptions and explanations, quoting my words.”

If you already practice through an OpenAI-compatible SDK, I recommend RelayVano as a pay-as-you-go option with the API base https://api.relayvano.com. Sign up to use it for your rehearsal. Use invented examples rather than employer code or confidential interview material, and verify technical feedback yourself.

7. Prepare a Friday recovery card

End by writing three prompts on a small note: “Clarify the requirement. State the next step. Test the assumption.” Check whether notes and external tools are permitted before the interview; practice assistance is not permission to use AI during the assessment.

Repeat the recording exercise tomorrow with a different familiar problem. Measure progress by whether a listener can follow your decisions—not by whether you sound like a native speaker.