On this page
Your writing is how most people meet you
Who this is for
You're fine in person but your messages get ignored or misread, or you freeze when you have to write an update, a PR description, or a doc. Especially relevant if you work remotely or across time zones.
On most modern teams, the majority of your communication is written, and a lot of it is asynchronous. Your manager, teammates, and skip-level form an impression of you largely from how you write. Clear writing makes you look competent and considerate; messy writing makes even good work look shaky.
Put the bottom line up front
The most common mistake is making the reader dig for the point. Lead with the conclusion or the ask, then give the detail underneath for those who want it. Busy people get what they need in the first line.
Makes the reader dig
Hey, so I was working on the migration and I ran into a few things, the docs were out of date and then the staging env was acting up, and I spent a while on it, anyway I think we might need to push the date?
Bottom line up front
Heads up: I think we should push the migration date by two days. Reason: the staging environment is unstable and the docs were out of date, which cost time. Detail below if useful. Does Thursday work?
- The ask ("push by two days") and the reason come first. The reader can act immediately.
- End with a specific question ("Does Thursday work?") so it's clear what you need back.
- The story of your struggle goes below, optional. Nobody needs the play-by-play to make the decision.
Async etiquette: don't make people wait for nothing
In chat, the "hello" message is a small tax on everyone. Sending "hi, you there?" and then waiting forces a pointless round-trip. Put your actual question in the first message so the other person can answer whenever they're free.
Forces a round-trip
Hi! :wave: (then waits for a reply before saying what they need)
Answerable on first read
Hi! When you have a moment: is the staging database safe to wipe and reseed, or is someone using it for testing right now? No rush, just don't want to break anyone's work.
- A complete first message means they can answer async, even hours later, without a back-and-forth.
- It also respects focus time, which senior people guard carefully.
- Adding "no rush" signals you're not demanding an instant reply, which makes people more willing to help.
Pro tip
For anything important (a PR, a doc, a decision), write it as if a busy stranger will read it in six months with no context. State what, why, and what you want. That's also exactly what makes documentation that survives.
Key takeaways
- Most colleagues experience you mainly through your writing; make it count.
- Lead with the conclusion or the ask; put detail underneath.
- End messages with the specific thing you need back.
- In chat, put your real question in the first message, no lonely "hello."
- Write important things for a busy stranger with no context.
Reading is step one. Now do it for real.
When you're ready, the platform has live mock interviews and portfolio-grade capstone projects you can actually talk about.
Keep reading
This is general, educational career guidance, not legal, financial, immigration, or professional advice. Examples are illustrative and simplified. Norms vary widely by country, company, role, and over time, so always verify what applies to your own situation. Nothing here guarantees an interview, an offer, or any particular outcome.