Which engineering personas are available on /practice/engineering?

Three native English-speaking engineering personas stand by today: a junior developer walking through code-review feedback with a senior engineer, a senior engineer running a blameless incident retrospective after a production outage, and a tech lead facilitating a cross-team standup between backend and product. Each stays in character through the technical, the ambiguous, and the consequential — and each parks on a single carefully-chosen phrasing when the moment in the code review, the retro room, or the standup matters.

Is the first branch free?

Yes. The junior developer in the code review is free to start — you run the first branch without a paywall and the transcript is yours. The full branching tree on the senior engineer running the retrospective and the tech lead facilitating the standup unlocks on Pro; if you start one on a Free plan, you get a 24-hour preview window so you can feel the next branch before deciding to upgrade.

How does the branching dialogue work in practice?

Each persona adapts to what you actually say. Tap a choice from the beat the persona offers, the persona replies in character, and the next beat appears with three or four fresh options — right there on the page. Difficulty is shown per persona (B2 junior dev → B2 tech lead → C1 senior engineer) so you can rehearse the code-review register before you walk into the retrospective voice of the senior engineer or the standup cadence of the tech lead.

Live today — three personas, free first branch

Practice the engineering conversationswhen the wording has to land.

Code review, incident retrospective, cross-team standup — native English-language engineering personas rehearse the moment with you.

You walk into an engineering moment — a junior dev walking through code-review feedback with a senior, a senior engineer running a blameless incident retrospective, or a tech lead keeping a cross-team standup on track. Pick the persona you need to rehearse today.

Start with the code review Talk to the team

See every conversation:Browse all 11 scenario tracks

Or jump back to:HomeAcademicAviationCustomer serviceFinanceHospitalityIT supportLegalMedicalMilitarySalesHR

First branch freeStart with the junior dev on the code review — no paywall, no preview window.Full tree is ProUnlock every branch on the senior engineer and the tech lead.

3: engineering personas
B2: to C1 (CEFR)
FREE: first branch
10 min: per session

Why GlobalLingo, not generic tutoring

The engineering conversation is the curriculum.

Every other app teaches you 100 languages. We teach the three engineering English conversations that matter in an English-speaking team — the code-review moment where one precise question unblocks the next commit, the retro where the timeline has to land without assigning blame, and the standup where every blocker needs exactly one owner and one date.

Practice the conversation that comes back in the next sprint

Generic tutors drill vocabulary. We rehearse the code-review conversation: the PR comment you walk through beat by beat, the design question you ask before moving the validation layer, the closing confirmation that settles who needs a second pass. The phrase that lands matters more than the grammar you walked in with.

Try it

Personas that hold the blameless frame

Each persona holds its register through the technical, the ambiguous, and the high-stakes. The senior engineer running the retro never names a person to blame — only the gap in the timeline. The tech lead at the standup never answers every question — only moves ownership to one name and a date. The junior dev never over-hedges — only asks the one precise question that unblocks the next commit.

Try it

Real transcripts you can send to your manager

Every session saves a full transcript — see which phrasing held up under review pressure, mark it 1–5, and start a fresh session the next day to try the wording you wish you had. Start with the junior dev on the code review for free; open the full engineering tree on Pro.

Try it

Pick a persona, start branching

Junior dev. Senior engineer. Tech lead.

Each persona speaks English, stays in character, and adapts to what you actually say. Tap a choice, the persona replies in character, the next beat appears with three fresh options — until you reach the end of the scene. The junior dev on the code review ships free — start it without a paywall; the rest of the engineering track opens on Pro.

Loading personas…

Your first practice

Watch. Read. Choose. Review.

Every session follows the same four beats — designed so the engineering register actually sticks, even when you only have ten minutes between PRs.

Persona · Junior developer, code review

English · inline comments + design feedback · 10 min a day

Practice shape

Watch

See the persona's opening line — the exact phrasing a real English-speaking junior developer, senior engineer, or tech lead opens with on a code review, an incident retro, or a cross-team standup.

Read

Read the role brief: who the persona is, what they will ask, how they will respond when you are precise and when you slip on a design decision, a timeline detail, or a blocker assignment.

Choose

Tap a choice from the persona's opening beat. The persona replies in character and the next branching beat appears with three or four fresh options, each one a different framing to test in the review room, the retro, or the standup.

Review

Replay the transcript, see which branches you reached, and start a fresh session the next day to try a clearer, more direct rephrase — engineering English rewards deliberate practice.

Live today

Start practicing the engineering conversation that matters.

Pick the junior dev on the code review to start free — the first branching beat is yours the moment you land. Open the full engineering tree on Pro and the senior engineer on the incident retrospective and the tech lead on the cross-team standup all open up the same day.

Start with the code review Talk to the team

Or email us directly at globallingo@polsia.app — we read everything. GlobalLingo is built on Polsia.

four skills, engineering-shaped

What you'll learn to say — and what you'll understand when they say it back.

The same four-skill scaffold that powers every GlobalLingo conversation persona — adapted for engineering encounters where technical vocabulary, register across seniority levels, precision under ambiguity, and cross-team English all have to line up in the same exchange.

Technical vocabulary in context

The code-review vocabulary (inline comment, design issue, service layer, validation), the retro vocabulary (blameless, timeline, alert threshold, runbook), and the standup vocabulary (blocker, owner, shipped, in review) — drilled inside a real back-and-forth, not in isolation.

Direct with the junior dev, measured with the senior engineer, facilitative with the tech lead — three voices in three rooms. The picker lets you rehearse each so register stops being something you have to think about mid-sentence when the senior walks into your PR.

Precision under ambiguity

A vague PR comment, an unclear retro update, a blocker with no owner — practicing engineering English means modeling precision: ask the one question that unblocks the next step, name the exact timestamp, assign the blocker to one person. The persona models staying in character when the exchange gets technical.

Cross-team English

The standup that keeps backend and product aligned, the retro that surfaces a system failure without assigning blame, the code review that lands a design critique without derailing the relationship — real cross-team English rewards the same deliberate practice as any other register.

The three personas on this page

One for every engineering moment where phrasing has to land.

Code review

The code-review voice — acknowledge first, ask one precise question per ambiguous comment, confirm next steps before closing the thread. Direct, professional, no over-hedging.

First branch freeStart

Incident retrospective

The retro voice — blameless frame first, timeline next, two concrete action items on the last beat. Measured, accountable, post-mortem-document register.

Full branching treeStart

Cross-team standup

The standup voice — format reminder first, updates round next, one owner per blocker on the last beat. Calm, direct, facilitator register — moves the conversation forward.

Full branching treeStart

What the branches feel like

A vague PR comment becomes a clear fix or a sharp question. A rushed retro update becomes a structured timeline.

The persona reads what you say and decides what comes next. Every vague phrasing is a moment to find a more precise one — every direct, on-register reply unlocks the next beat.

Vague PR comment → a clear fix or a sharp question

A thin "this could be cleaner" triggers the junior dev to slow the cadence and ask one precise question before moving the validation layer — which layer, which direction, which constraint. The next beat forks: propose the fix, ask for a clarifying example, or confirm the design before the next commit.

Rushed retro update → a structured timeline and two action items

When a team member gives a vague "it was sometime in the afternoon" the senior engineer pulls the exact UTC timestamp from the alert log and names the twenty-minute gap nobody wants to discuss. The next beat forks: surface the gap, assign a runbook owner, or lower the alert threshold before next on-call.

Keep practicing the engineering vocabulary

The branching beat opens a door. Sora and the pronunciation coach hold it open.

The persona gives you the moment; the rest of GlobalLingo keeps the engineering vocabulary in your mouth. Run Sora between branches to lock the code-review phrasing in, and let the pronunciation coach score it phoneme-by-phoneme.

Sora — the AI tutor

Sora listens, replies, and quietly scores your accent. Run a fifteen-minute session between branches to keep the engineering vocabulary in your mouth — the code-review phrasing the junior dev anchors on, the retro framing the senior engineer stays blameless with, the standup cadence the tech lead moves blockers through.

Open Sora

Pronunciation coach

Phoneme-by-phoneme scoring against a native curve. The plosive /k/ that closes "runbook," the schwa that lets you park on "retrospective" without over-articulating it, the stress that lands "blameless" as the frame-setter not the accusation — the coach surfaces exactly the syllables you missed.

Open pronunciation