Ever felt like you should know every rule of English grammar, every verb tense, every exception, on top of actually doing your job as an engineer? You don't need to. That pressure to know it all is usually what gets in the way, not what helps.

Learning to Say No

For years, I did it all myself. Accounting, legal matters, branding, no matter how tired or overworked I already was. I'm an engineer by training, and somewhere along the way I'd decided that meant I had to solve every problem on my own.

I don't do that anymore. I have an accountant with a postgraduate degree and a company lawyer who's better at contracts than I will ever be. Saying no to doing everything myself hasn't made me less capable. It's made me better at the part of the job that actually matters, because I'm not stretched across everything I could technically handle.

That's the same trap I see engineers fall into with English. If you could technically work something out yourself, given enough time and enough grammar books, you assume you should. But "could" and "should" aren't the same thing, and the gap between them is where a lot of unnecessary stress lives.

You Just Need a Reliable Source

I ran a poll in my Instagram stories a while back, a simple yes/no: do you know all 12 verb tenses in English? Every single person who answered said no. Including the native speakers.

So if native English speakers don't have all 12 tenses on hand, why would you, working in your second or third language, think you need them?

You don't need to know it all. You need to know where to look, and which parts actually matter for your work.

Here's the shortcut: for most international projects, five tenses will get you through almost everything. For written reports, you can get by on three. That's it. Everything else is detail you can pick up as it comes up, not a prerequisite you need before you're allowed to start.

The same logic applies beyond tenses. Instead of reaching for a general grammar book when you're stuck, reach for the standard reference book or code in your own industry (e.g. the RIBA used in the UK), but the English version. It's already written in the vocabulary you use daily, and it teaches you the language your job actually requires, not the language a textbook assumes you need.

Don't Be Afraid to Ask for Help

Asking for help works in two directions, and most engineers underuse both.

First: your colleagues. Most people have real patience for someone who's brave enough to work in a second or third language. When you're struggling to find the right word, having trouble following a fast conversation, or not quite sure what was just decided, say so. That's not a weakness you're exposing. It's information your colleagues need to communicate with you properly, and most native speakers will adjust once they know. They can't adjust their side of the conversation if they don't know there's a gap to close.

Second: a professional coach. This is the same principle as the accountant and the lawyer from earlier in this article, just applied to English. You don't have to find the fastest way to build Technical or Business English by trial and error, on your own. Someone whose entire job is understanding that process can get you there faster, and let you spend your energy on the actual engineering.

Neither of these is a fallback for people who "can't manage on their own." They're just the more efficient path, and the one every capable professional already uses in every other part of their job.

Ready to Stop Doing This Alone?

You don't have to build your English skills from scratch, any more than you'd build your own accounting system from scratch. If you want a reliable source built specifically around your work, not a generic course, book a free 15-minute discovery call. We'll figure out what you actually need to focus on first.

Book your free 15-minute call

---

FAQ