For engineers and technical teams

English conversation lessons for engineers

Engineers often read and write technical English very well. Speaking is different. In a meeting, you need to explain a complex problem in simple words, quickly, to people who are not engineers. These private lessons help you do that with confidence.

I teach civil, mechanical, electrical and software engineers, and people in IT and manufacturing. We practise your real situations: project updates, design reviews, calls with suppliers and clients, and explaining delays.

What we practise

Situations engineers practise with me

Explaining a technical problem simply

Describing what went wrong, why, and what happens next — for managers and clients, not other engineers.

“Basically, the part is wearing out faster than we expected, so we need to replace it sooner.”

Project updates and stand-ups

Giving a short, clear update on progress, risks and blockers.

“We're on track for the first phase, but there's a risk on the second one.”

Explaining delays and bad news

Telling a client or manager about a delay without sounding defensive.

“I'm afraid we're looking at a two-week delay. Here's why, and here's what we're doing about it.”

Design reviews and technical discussions

Giving your opinion, asking questions and disagreeing with a design politely.

“Have we thought about what happens if the load is higher than this?”

Calls with suppliers and contractors

Asking for specifications, checking details and agreeing deadlines.

“Just to confirm, you can deliver all 200 units by the end of March?”

Job interviews and career moves

Talking about your projects and your role in technical interviews in English.

“On my last project, I was responsible for the testing and quality side.”

Language you'll learn

Technical English for speaking, not just reading

Explaining clearly

  • Simple structures: problem → cause → effect → solution
  • Linking words: because of this, as a result, which means
  • Describing processes and sequences out loud

Meetings and teamwork

  • Giving updates and talking about risks
  • Polite disagreement and suggestions
  • British vs American words: lift / elevator, aluminium / aluminum, earth / ground (electrical)
Example plan: project engineer Level B1+ · 8 of 25 lessons
  1. Introducing yourself and your project
  2. Explaining a technical problem to a non-engineer
  3. Giving a two-minute project update
  4. Talking about risks and options
  5. Explaining a delay to a client
  6. Disagreeing in a design review
  7. Supplier call: specs and deadlines
  8. Interview practice: describing a past project
An example only. Your plan is built from your diagnostic, so it will fit your real work.
How it works

How lessons work

  1. Free diagnostic

    30 minutes on video. Tell me about your work. I check your speaking and find your gaps.

  2. Your plan

    I build a lesson plan from your real situations. You get a preview before you pay anything.

  3. Weekly lessons

    Private one-hour lessons. Lots of speaking, clear corrections, and new phrases for your work.

Read more about how lessons work and the price →

Questions

Questions from engineering learners

Is this good for software engineers and IT?

Yes. For software and IT, we often practise stand-ups, explaining bugs, code and architecture discussions, and talking to non-technical colleagues.

I read English well but freeze when I speak. Is that normal?

Very normal, especially for engineers. Reading and speaking use different skills. The fix is regular speaking practice on your real topics, which is what my lessons are.

Can we use my real project documents?

Yes. Share a report, a diagram or a presentation (with private details removed), and we practise explaining it out loud.

I also teach: English conversation practice · English for finance professionals · English for medical professionals · English for sales professionals · English for legal professionals

Book your free diagnostic