I was taught proper German grammar at home. By the time I got to primary school in Tyrol, I knew some of the rules better than my teacher did. I corrected her. More than once. It annoyed her (also more than once).

What I didn't realise growing up was that knowing the rules cold and communicating well are not the same skill. At home, I switched between three regional dialects depending on who was in the room. At work, formal German. Later, English. I'm still doing it, just with more languages.

That's the thing about grammar. It matters, but not the way most engineers assume. You don't need to out-grammar your old teacher. You need people to understand you fast, take you seriously, and not get stuck on a small error while you're explaining something that actually matters.

So let's skip the guilt trip. Here's where grammar genuinely earns its keep for an engineer working in English, and where it genuinely doesn't.

First impressions are fast, and grammar is part of the read

Before anyone judges your ideas, they judge your writing. That's not fair, and it's not really about you. It's just how a first email or a first Slack message works: someone reads it in ten seconds and forms an opinion before they've thought about it.

Grammar mistakes don't make you look stupid. They make you look rushed, or like you didn't check your own work before hitting send. In a first message to a client or a new stakeholder, that's the impression you're fighting.

Here's the part that actually matters: this is a written-communication problem, not a speaking problem. Nobody's counting your grammar mistakes in a meeting. They're listening to whether you're clear. But in an email, a proposal, or a report, the reader has time to notice, and a first impression built on sloppy writing is hard to undo later with better spoken English.

Confusing grammar makes people stop following you

Some grammar mistakes are cosmetic. Others actually break the sentence, and the listener has to stop and work out what you meant, right there in the meeting.

That's the real cost. Not "this sounds unprofessional." It's "I lost you for three seconds while I figured out what you meant," and in a client meeting, three seconds is enough to lose the thread* of the whole argument.

Tense is the most common culprit, because it changes what you're actually saying, not just how it sounds. "I sent the report" and "I will send the report" are not interchangeable if someone's asking whether it's done yet. Get that wrong and you're not sounding imperfect, you're giving the wrong information about a real deadline.

Modal verbs cause a different kind of damage: tone, not facts. I know someone who mixes up "may" and "can," because in her first language, one word covers both permission and possibility. So instead of "yeah, we can totally do that," it comes out as "we may do that." Technically fine grammar. But it sounds like she's granting permission instead of agreeing, and in a meeting that reads as arrogant, even though she means the opposite.

People easily forgive grammar mistakes, especially if they hear your accent. But a first impression stays. So worry less about your tenses, and more about whether your grammar is quietly making you sound rude.

Technical writing doesn't get a follow-up question

A meeting has back-and-forth. If someone doesn't understand you, they hopefully ask. A report, a spec, or a set of instructions doesn't get that chance. Whoever reads it next might be in a different time zone, or reading it two years later, with no way to ask what you meant.

That's why grammar matters more in writing than in speech. Not because writing is more formal. Because it's the only version of what you said that survives the conversation.

An ambiguous instruction in a spec doesn't just confuse someone. It gets built the way it was written, not the way you meant it. A missing "not," or the wrong tense in a safety note, isn't a style problem. It's the kind of mistake that gets found much later, and usually not by you.

So the bar for technical writing isn't "sounds professional." It's "still makes sense to someone with zero context, next year, with no one around to ask."

Grammar mistakes get remembered longer than you'd think

Nobody keeps a scorecard of your tenses. But mistakes add up into a general impression, and that impression decides who gets handed the client-facing report, and who gets asked to have theirs checked first.

This is where grammar actually threatens your career. Not in one missed email, but over months. Managers remember who they can trust without a second read. Clients remember who explained a delay clearly, and who left them confused. When a promotion or a bigger project comes up, "communicates clearly in English" is quietly part of the decision, even if nobody says it out loud.

The good news: you don't need perfect grammar to be that person. You need to be consistently understood, and to know which mistakes are actually costing you.

Use a grammar checker. Just don't outsource the whole report.

Grammarly, or the checker built into Word or Google Docs, genuinely helps. Turn one on and let it catch typos and slips while you write, instead of proofreading everything yourself afterwards.

What it can't do: tell you whether a sentence sounds confident or rude, or whether a report says what you actually meant. And it's not a reason to let AI draft the whole thing. A generated report has none of your judgement in it, and your judgement is usually the part people are actually paying for.

Where to actually focus your energy

You don't need to master every rule in English grammar. You need to know which mistakes cost you something, and which ones don't. That's it. That's the whole article.

If you want a second pair of eyes on your own patterns, specifically the ones you can't hear in your own written and/or spoken communication, book a free 15-minute call, and we'll figure out where your actual gaps are, not the ones a textbook assumes you have.

Language notes

lose the thread — to lose track of what someone is explaining, usually because you got distracted or confused partway through

FAQ