You became an engineer because you love numbers, right? So why do you also have to learn how to write and present?

If you're here, you're probably an engineer looking to improve your English, or you're a fellow word nerd. Either way, this one's for you. This article covers:

• The mindset shift that might be holding you back
• A structure that does most of the writing work for you
• Concrete tips for speaking up, even when your English is far from perfect

"I'm Bad at English."

This is a very common sentiment from my engineers. If you struggled with English in school, it's hard to break that belief now, even years later.

Let me tell you about my friend Christian Urich. We went to high school together in Austria. Christian struggled with English in school — his class was pass/fail, and he barely passed. His English teacher actually told him to never speak English again, and not to tell anyone she'd taught him.

Christian followed that advice for a while. He got his master's-equivalent in structural and computational engineering in Austria, then started working in structural engineering. But while doing his PhD at the University of Innsbruck, he realised he wanted more. He landed a job in sustainable urban development, working with mathematical and computational modelling — not exactly wordy work.

What he didn't expect was how international the work would get. He was on a European project, started working with Australians, and got interested in what they were doing. Long story short: he now lives, works, and teaches in Australia — in English.

Once "bad at English," he now communicates clearly and confidently at the office, in the classroom, and at home. His secret wasn't talent. It was following a structure.

"Won't I Have a Receptionist?"

I'm including this one because my own professor said it. He told us we were in charge of numbers and design — someone else could handle the words. Our receptionist, presumably.

That mindset came from a specific place and time: German and Austrian engineering firms in the '90s. If you want the full picture of how that compares to English-speaking firms, I've written about it here. Short version: it barely holds up anywhere anymore, including at home.

How to Succeed in Technical English Writing

If you're working with firms that expect document-based engineering, you need to write short, engaging one-page reports that interpret your numbers, not just present them.

That report needs to cover the important parts of your project in a way anyone can follow. Here's the good news: you don't need to be a good writer to write well. You're not writing an essay or a novel. You're writing a report, and every report follows a structure.

Christian calls this a recipe. Someone else usually gives you the recipe. You just put the ingredients together. At minimum, your report needs:

• Your aims
• How you achieved them
• Your conclusions

Ask yourself: will the reader understand this? Could they explain it to someone who isn't an engineer? If yes, you've done your job. Writing reports and summaries doesn't need to be technical. It needs to be clear for your audience.

For most of my non-native English-speaking engineers, one simple structure, used consistently, produces effective reports every time. If you're not sure which format to use, look at past projects or ask a colleague for theirs. You can adjust it as you go.

You're the expert. You're not just good at calculation and design — you can turn those numbers into action. Communicate your findings clearly, and you're set.

How to Speak Business English

Speaking and presenting can feel intimidating, especially in a language as inconsistent as English.

I've seen engineers go quiet in meetings because they're worried their English isn't good enough. That's the worst thing you can do. As Christian puts it: "It doesn't matter how good or bad your English is. It is what it is." What matters is that you're communicating your ideas. Even broken English gets your point across.

A few things to remember next time you have to speak up:

• It's fine if your English is broken. Most of us have been there.
• Don't apologise, and don't hold back. You're good at your job, and you have something worth sharing.
• People are more forgiving than you think. They hired you for your engineering, not your grammar.
• Your ideas matter more than your accent or your word choice. Say them anyway.

FAQ

Want a coach who's also an engineer to help you build that structure and that confidence? Book a free 15-minute call and let's talk about what's actually holding you back.

Want more from Christian? Catch our full conversation on the podcast, Let the Drawings Speak.

Original Post from 23 May 2022; latest update: 19 August 2026.