Skip to content

English for software engineers in meetings and client calls

Updated

Software engineers who work in English as a second language lose the most credibility on small things: prepositions (“depends from”, “on production”), the tense of a status update (“I am testing since the morning”), and estimates buried under hedges. Lead stand-ups and estimates with the fact, and turn technical work into what changes for the listener.

The technical vocabulary is the easy part: you use it every day, and much of it is the same in every language. What gives a second-language engineer away in a stand-up or a client call is the small grammar around it, and answers built the way a design doc is built, with the conclusion at the end.

For your role, in this meeting · graded against your role and the meeting type

Stand-ups

A stand-up is a status update, and status updates live in two tenses: the past simple for what is done, and the present perfect continuous for what started earlier and is still going.

I already fixed it yesterday, and now I am testing since the morning.

I fixed it yesterday, and I’ve been testing it since this morning.

Estimates without the hedging

Give the number first, then the condition that would change it. Three hedges in front of an estimate make it sound like a guess, even when it is a careful one.

I think maybe it will take around two weeks or so.

Two weeks. If the API change slips, three.

By, until and in

By is a deadline, until is a period that ends, and a version number takes no article. All three come up in almost every planning conversation.

The bug is in the version 2.3, we will fix it until Friday.

The bug is in version 2.3. We’ll fix it by Friday.

Incidents: what happened, what it affected, where it is now

Literal translations show most under stress. Say what failed, what it affected and the current state, in that order.

The system fell down at night.

The service went down overnight. Checkout was affected for forty minutes, and it’s back up.

Explaining to non-engineers: consequence first

A client does not buy the refactor. They buy what changes for them. Say that first, and keep the technical reason for whoever asks. The page on English for client calls goes further.

We need to refactor the payment module because of technical debt.

Changes to payments take us three weeks today. After this work, they’ll take one.

A betterput report knows your role and the kind of meeting, so a stand-up and a client call are not graded the same way, and each fix quotes your own sentence.

Common questions

Do developers need business English or technical English?
Mostly neither in the textbook sense. The technical vocabulary you already have. What helps is the spoken English of meetings: tenses for status updates, prepositions, and answers that start with the conclusion.
How can a software engineer improve spoken English at work?
Work from your own meetings. Export the transcript of a stand-up or a client call, read your own lines, and look for the patterns that repeat. A tool such as betterput does that reading for you and keeps count across meetings.
Is my accent a problem on client calls?
Rarely, if people understand you. What a client notices is a missing answer or a number buried at the end. A transcript cannot show your accent, and in most meetings it is not what costs you.

Now see how your English came across

Paste a meeting transcript into betterput and get your clearest English fixes, your talk share and your hedging. Your first full report is free, and the check without an account takes about thirty seconds.

One report a month is free, with no card. Pro is $15 a month for ten. Trying it without an account stores nothing.

Related