The English of real tech work.
Many people in tech read English all day: documentation, error messages, pull requests. Speaking it is different. A daily stand-up, a bug you have to explain on a call, or a manager who asks why the release is late all need fast, clear spoken English.
These lessons focus on the language of real tech work. Each one gives you the phrases that teams actually use, a model conversation, the mistakes that learners in tech make most often, and a short task where you use the language for your own job.
The lessons
The daily stand-up
Give a clear stand-up update in under a minute: yesterday, today, and blockers.
B1 IntermediateExplaining a bug
Explain a bug so clearly that a developer can reproduce it the first time.
B1 IntermediateCode review comments
Give and answer code review feedback that is clear, specific, and friendly.
B2 Upper intermediateExplaining tech to non-technical people
Explain a technical problem in plain language, focused on what it means for the listener.
B2 Upper intermediateEveryday tech words
Use the core verbs of tech work naturally, with the right collocations and phrasal verbs.
B1 Intermediate
Three tips
- Short and specific beats long and complete. In a stand-up, one clear sentence about a blocker is worth more than two minutes of background.
- Learn the verbs, not only the nouns. You probably know "deployment" and "merge". The sentences come from verbs like roll back, ship, reproduce, and push.
- Practice explaining your work to someone outside tech. It is the skill that gets people promoted.
Need English for your next stand-up or client call?Practice with Thomas in a one-on-one lesson. He'll role-play your real meetings with you and help you explain your work clearly.
Book a lesson with Thomas