Professional email guide for developers

Writing Professional Emails in English: A Guide for Software Developers

How to write emails that are clear, polite, and appropriate for your workplace, whether you are following up on a PR, escalating a bug, or asking for help.

Developers write more emails than they think. Access requests, status updates, bug reports to non-technical stakeholders, follow-ups on unanswered questions, escalations. Each one is a small professional moment.

In English, the difference between a good email and a bad one is rarely about grammar. It is about tone: how direct you are, how you open, how you close, and whether the other person feels respected. These are things you pick up slowly if nobody teaches them to you explicitly.

The emails developers actually write

Access request

Example

Hi Sarah,

I am joining the payments team next week and will need access to the production dashboard. Could you add me to the payments-team group in AWS?

Thanks,
Alex

Tip

State who you are, why you need it, and what exactly you need. Do not make them guess.

Following up on an unanswered email

Example

Hi Carlos,

Just following up on my email from Monday about the API rate limits. Let me know if you need any additional context from my side.

Thanks,
Alex

Tip

One follow-up is professional. Two is the limit. Keep it short and assume good faith.

Reporting a bug to a non-technical stakeholder

Example

Hi Maria,

We found an issue affecting the checkout flow. Users who add more than 10 items to their cart are seeing an error when they try to pay. We are working on a fix and expect to deploy it by end of day. I will update you when it is live.

Let me know if you have any questions.

Best,
Alex

Tip

No technical jargon. Explain the impact, not the cause. Tell them what you are doing and when.

Asking for help

Example

Hi Jordan,

I am working on the authentication refactor and running into an issue with token refresh. I have checked the docs and tried a few approaches but I am stuck. Do you have 15 minutes this week to take a look?

Happy to share my screen.

Thanks,
Alex

Tip

Show you already tried something before asking. Offer a specific time commitment, not an open-ended "can you help me."

Escalating an issue

Example

Hi David,

I wanted to flag that the database migration we planned for Friday is at risk. We are still waiting on approval from the security team, and we have not heard back since Tuesday. Could you help unblock this?

Happy to set up a quick call if that is easier.

Best,
Alex

Tip

Escalate facts, not frustration. Say what is at risk and what you need, not how annoyed you are.

Subject lines: be specific

The subject line determines whether your email gets read today or next week. Vague subjects get deferred. Specific subjects get answers.

Avoid: "Question", "Help needed", "Following up"

Better: "Access request: payments-team AWS group", "Follow-up: API rate limit question from Monday", "Checkout bug affecting payments, fix deploying today"

How to sound professional without sounding cold

English professional email tone sits somewhere between formal and casual. You do not use "Hey" unless you know the person well. You do not use "Dear Mr. Smith" unless you are writing to someone in a formal industry like law or finance.

For most emails inside a tech company, "Hi [Name]," is completely standard and accepted. But if you are writing to someone senior you have never met, or to an external contact at a more formal organization, "Hello [Name]," is a safer choice: it is professional without being stiff.

"Dear [Name]," works for very formal external emails, but it can feel cold in a tech context. When in doubt about the culture: start with "Hello" the first time, and follow the other person's lead in their reply.

For sign-offs, these work in most professional contexts:

Thanks,	Any email where you are asking for something or someone is helping you.
Best,	Neutral, professional. Good for stakeholders and people you do not know well.
Best regards,	Slightly more formal. Good for external contacts or first contact.
Let me know if you have any questions,	Good closing line before your sign-off when you have delivered information.

Polite phrases that do the heavy lifting

Asking for something

"Could you please...?"
"Would it be possible to...?"
"I would appreciate it if you could..."
"When you get a chance, could you...?"

Following up

"Just following up on my previous email."
"I wanted to check in on..."
"Any update on this when you have a moment?"
"No rush, but wanted to make sure this did not get lost."

Delivering bad news or a delay

"I wanted to give you a heads-up that..."
"Unfortunately, we have run into an issue with..."
"I am sorry for the delay on..."
"We are working on this and will update you by [date]."

Ending professionally

"Let me know if you have any questions."
"Happy to jump on a call if that is easier."
"Please do not hesitate to reach out if you need anything else."
"Looking forward to hearing from you."

Things that sound ruder than you think

Avoid

"As per my last email,"

Why: This is passive-aggressive in English. It implies the other person did not read your email and you are annoyed. Use "As I mentioned" or just repeat the information.

Avoid

"Please advise."

Why: This sounds cold and demanding. Replace with a specific question: "Could you let me know how you would like to proceed?"

Avoid

"Obviously," or "Clearly,"

Why: These words make the reader feel like they missed something obvious. Avoid them completely.

Avoid

"I need this by [time]."

Why: Framing your deadline as a demand. Try: "Would it be possible to have this by [time]? I need it for..."

Avoid

"No subject, or subject: "Hi""

Why: It signals that you do not value the other person's time. Always write a descriptive subject.

A real story: a polite reply that still caused problems

Early in my career I worked at a company with a very strict hierarchy. I found out the hard way.

One day, someone sent an email to our team with a question about the product. I knew the answer, so I did what seemed logical: I replied.

I wrote a professional email, in formal English. I answered the question clearly and offered to help if they needed more information.

I thought I had done a good job.

Shortly after, my manager's manager called me into a meeting.

She challenged me for having replied to that email.

I was completely confused.

My reply had been polite. The information was correct. I had responded before the rest of the team. I did not understand what the problem was.

Then she explained it to me.

The person who had sent the email held a much more senior position within the company. And in that organization there was an unwritten rule: someone at my level was not supposed to communicate directly with someone at theirs.

It did not matter that they had written first.

It did not matter that I had the correct answer.

It did not matter that my intention had been to help.

I was expected to escalate the query and let someone more senior handle the communication.

I never agreed with that rule. But I learned something important that day:

Being polite is necessary, but it is not always enough.

In some companies, hierarchy does not only determine who can give you instructions. It also determines who you are allowed to communicate with and who is authorized to represent the team.

So before you reply to an email from someone outside your immediate team, especially if they belong to another organization or hold a more senior position, it is worth asking yourself:

Am I the right person to reply? Should I check with my manager first? Is there an internal protocol for this kind of communication?

A perfectly written reply can cause problems if it is sent by the wrong person in the wrong company.

When in doubt, check before you hit send.

Before you send: a quick checklist

Subject line is specific and descriptive.
You are the right person to send or reply to this email.
You have followed any required process first (ticket, Slack, your manager).
You stated who you are and why you are writing in the first two lines.
You are asking for one thing, not five.
Your tone is direct but not blunt.
You included a clear next step or question.
You signed off professionally.

Keep learning

Ready to practice your English at work?

Lingua-e has interactive exercises built around real developer conversations: standups, code reviews, retrospectives, and more. Practice until it comes naturally.

Try Lingua-e for free

Written by

Roxana Lafuente

Lingua-e's founder

Roxana Lafuente is a software engineer with 8+ years of experience. At the beginning of her career, even though she had already passed the First Certificate in English, she still froze every time she had to speak up in the daily standup. That was a gap nobody was fixing. After 2,000+ standups, she figured out what actually builds fluency: practice that looks like your real work. She built Lingua-e so other developers wouldn't have to take the long road to feel confident working in an international development environment.