Solidifying a new role
A global team, a new title, meetings that now expect you to speak up. You want to own it, not just survive the calls.
For Japanese engineers on English-speaking teams
Built around the standups, design reviews and meetings you actually have to speak in — your real work, rehearsed out loud.
Native Australian English speaker · One-to-one · In your timezone
Who it's for
For engineers who already read and write English well, and want to speak it with confidence at work.
A global team, a new title, meetings that now expect you to speak up. You want to own it, not just survive the calls.
You're good at your job; your English is what holds you back. You stay quiet where you have something to add, and you sense it's limiting the roles open to you.
Either way, the practice is pitched at your technical context — and conducted entirely in English.
The method
You bring the real situations from your work and we practise them out loud. What I listen for is a set of patterns in how Japanese engineers speak English — worked fastest wins first.
None of these are careless mistakes. Each is a predictable result of Japanese and English being built differently — your first language doing its job where its rules don't apply. That is exactly why focused practice moves them.
Why first: these move fastest. You will feel the difference within weeks.
"Um", "uh", "like", "basically" — sounds that fill the gap but carry no meaning.
"So, basically, the issue is in the database layer.""The issue is in the database layer."
Silence in the middle of a thought, not at a natural break.
"We need to update the… authentication module.""We need to update the authentication module."
Repeating a word, or abandoning a sentence and restarting it.
"The the server crashed after the deploy.""The server crashed after the deploy."
Why next: knowing the rule doesn't change live speech. These need repetition, once fluency is steady.
Dropping "a", "an" or "the" where English requires one.
"We found bug in authentication flow.""We found a bug in the authentication flow."
Leaving off the "-s" where a noun should be plural.
"We have three server running in production.""We have three servers running in production."
Starting with the verb, leaving out "it", "I", "we" or "they".
"Is already merged into main.""It is already merged into main."
Why last: the deepest layer. We train your ear before your mouth — and I'll be honest, it's the long game.
Swapping the English /l/ and /r/ sounds, in either direction.
"We need to deproy the update.""We need to deploy the update."
Slipping a vowel into an English consonant cluster, adding a syllable.
"The su-cript runs every night.""The script runs every night."
Putting the emphasis on the wrong syllable of a word.
"We need to DE-velop a new API.""We need to de-VEL-op a new API."
About
Twelve years in software — helpdesk to infrastructure to security to leading multinational teams — so the conversation stays real no matter what you bring.
The program
Every session is prepared in advance and reviewed afterwards.
A representative path — tailored to your role and goals.
If your company has a self-development budget, this may qualify. Tell me what your finance team needs — invoice, receipt, program description — and I'll send it.
Backed by a 30-day money-back guarantee — see below.
Guarantee
Try it for 30 days. If it's not right for you, tell me and I'll refund you in full — no awkward questions. And because you pay monthly, stopping is simply a matter of not paying again: your real commitment on day one is one month, not ninety days. The risk should be mine, not yours.
FAQ
We meet one-to-one over video for live English conversation, in your timezone. You bring the real situations from your work and we practise them out loud.
It's aimed at engineers who already read and write English well and want to improve their speaking. Not a beginner course, not grammar drills.
You start with a free intro call, and you're covered by a 30-day money-back guarantee — so you can decide before you pay, and change your mind after you start. See the guarantee above.
One hour a week for twelve weeks, plus light preparation before each session — designed to fit around a full-time job.
Get started
Book a free 20-minute intro call to see whether it's a fit.
Not ready to book? Just email me — I answer every one myself.