How to write a cover letter for a remote job (with a template)

People disagree about cover letters. Some say nobody reads them, others say they decide everything. For remote jobs we think they get read more often than not, and that they are worth an hour of your time.

A remote team runs on writing. Decisions live in documents, questions get answered in chat, and work is handed over in notes that someone opens eight hours later. When your application lands, the cover letter is the first thing you have written for them. It works as a small writing sample, and your resume cannot do that job.

Below: what a remote hiring manager is looking for, how to build the letter, a template, three sample middles, a shorter note for application forms, and the mistakes we see most often.

What remote hiring managers look for

Someone opening a cover letter for a remote role has a few questions in mind. You do not have to answer each one out loud, but most of them should be settled by the end of the letter.

Can this person write? Probably the biggest one. Short sentences, the point in the first lines, nothing padded. If the letter is easy to read, the person's Slack messages will likely be easy to read too.

Will they get on with the work without someone checking in? Nobody can lean over your desk. Readers look for signs that you start things, finish them and say what is going on. One story about a project you pushed forward yourself says more than "self-motivated" ever will.

Have they worked async? The word itself is optional. Working with people in other cities, writing something others relied on, or handing off a task so the next person did not need to ask questions all count.

Can we hire them? Location, time zone and work authorization should not be a puzzle. One sentence does it.

Did they read the posting? Generic letters are easy to spot, and remote roles attract a lot of applicants. Mention something real about the company or the work.

The structure, paragraph by paragraph

One screen is plenty. Aim for 200 to 300 words in four short paragraphs. For a senior role, add detail to the proof paragraph instead of adding paragraphs.

Paragraph 1. The role and a specific reason

Name the job and say why this company. Skip "I am writing to apply for", since the subject line already says that. Open with the reason.

A good reason is a product you use, a document the company published, a technical decision you have an opinion on, or a customer group you know well. If you could paste the same sentence into a letter to any other company, pick a different reason.

Paragraph 2. One strong piece of proof

Choose the one experience on your resume that fits the job best and tell it briefly: the situation, what you did, what happened. Put in a number if you have an honest one. If you do not, describe the outcome in plain words.

The reader has your resume open in the next tab, so do not walk through it line by line. Pick the one thing that deserves a paragraph.

If the posting lists a few clear requirements, this is also where you show the match. They want experience with customers in several languages and you have it? Give an example. For the resume side of this, see how to write a resume for remote jobs.

Paragraph 3. How you work remotely

Ordinary cover letters skip this one, and it is the one remote employers care about. In two or three sentences, show how you work when nobody is in the same room. Good material includes:

• A team spread over several time zones, and how you stayed in sync
• A spec, document or handoff note you wrote that other people actually used
• A tool, mentioned in the middle of a story instead of in a list
• What you do when you hit a question and nobody is online

Then the practical part: where you live, your time zone, and how many hours you overlap with the team. If the posting names a region, say you fit it. To see who hires where you live, the remote jobs by region pages are quick to check.

Paragraph 4. A plain close

Say what is attached or linked, and add one line inviting a reply. "I have attached my resume and linked two examples below. Happy to answer questions by email or on a call." Done.

Skip the pleading, the "I would be thrilled" and the long thank-you. A calm ending sounds more sure of itself.

A fill-in template

Copy it, fill every square bracket, then keep editing until it sounds like you. If your finished letter still reads like this template, start that part again.

Subject: [Role title] application, [Your name]

Hello [Hiring manager's first name, or "Hiring team"],

I am applying for the [Role title] position. I have used [product or thing you actually use] for [period], and [one specific observation about the product, the team's work or a public document they wrote]. I would like to work on that full time.

At [Current or recent company], I [what you did, one sentence]. [What was hard about it, one sentence]. The result: [the outcome, with a number only if you honestly have one]. It is close to what your posting calls [phrase from the posting].

I have worked remotely for [period], with colleagues in [places or time zones]. To keep my work visible I [a specific habit: written weekly updates, documented decisions, recorded demos]. I live in [City, Country] ([time zone]) and can overlap with [region or hours] for [number] hours a day. [Work authorization sentence, if relevant.]

My resume is attached, and [link to portfolio, repository or writing sample] shows the work in more detail. Happy to answer questions by email or on a call.

Best regards, [Your name] [Email] · [Link]

Some notes on using it.

• The subject line. Recruiters search their inboxes. A role title plus your name makes you easy to find a week later.
• If the posting or the company page names the hiring manager, use the name. Otherwise "Hiring team" is fine.
• Delete any slot you cannot fill truthfully. Three true sentences beat six padded ones.

Three short examples

These are middle sections only, not whole letters. The details are made up for illustration, so swap in your own.

Customer support

At [Company name] I answered about [number] tickets a day from customers in several countries, and two of the other agents were in different time zones from me. The same billing question kept coming in every week, so I wrote a help article and a saved reply and posted both in the team channel. Billing tickets slowed down after that, and new hires were sent the article on their first day. I live in Lisbon (UTC+0), so I can cover European mornings and the start of the US East Coast day.

The letter gets a lot in: volume, a team spread across time zones, a fix you started yourself, and something written that outlasted you. If you are looking at support jobs, the customer support remote jobs show what employers ask for.

Software engineer

At [Company name] I took over moving our job queue from a cron script to a worker service. I wrote the design doc, asked three engineers in other time zones to comment on it in writing, and rolled the change out in stages behind a flag. Before, a failed job meant someone noticed days later. After, it showed up on a dashboard within the hour. There is a similar write-up in the repository linked below. I am in Warsaw (UTC+1) and fine with a few hours of overlap with US teams.

An engineer reading this learns how you work as well as what you know: design doc, written review, staged rollout and a link they can open. Compare it with what is being asked for right now in software engineering remote jobs.

Marketing

At [Company name] I ran the content calendar for a small B2B product. There was one other marketer, in a different time zone, so we wrote a brief for every piece and swapped a written update each week in place of a call. Blog sign-ups went from a handful a month to [number] a month over [period], and two of the articles are still among our top landing pages. Three of them are linked below. I am based in Bogota (UTC-5).

If writing is the job, writing samples are the best proof you have, and this gives the reader some to judge.

The short version for application forms

Plenty of forms have a small text box, or an optional "Anything else?" field. A full letter does not belong there. Write a cover note of three to five sentences.

Hello, I am applying for the [Role title] role. I spent [period] as a [your role] at [Company name], where I [one concrete result]. I like [specific thing] about how [Company name] [does something], and I would like to work on [specific area from the posting]. I live in [City, Country] ([time zone]) and work remotely with teams in [regions]. My resume and [link] are attached.

Four rules for the note.

1. Start with the role and the proof. Thanks can wait.
2. Add one fact that only fits this company. Without it, the note could go to anyone.
3. Give your location and time zone even if the form asks for them separately.
4. If there is a character limit, cut the proof sentence last.

When a posting has no field for any of this, you can still put the note in the body of your email or in the message that goes with a referral. For more on where this kind of application matters, see how to find a remote job.

Format and delivery

• Length. 200 to 300 words for a letter, 50 to 100 for a note.
• File. If the form wants a file, send a PDF with your name in the file name. If it wants pasted text, paste plain text and leave the fancy formatting out.
• Tone. Write the way you would write to a colleague you respect: polite, direct, no slang, no stiff phrases.
• The letter and the resume should agree on your last job title, the dates and your location.
• Check the company and role names against the posting before you hit send.

Common mistakes

Repeating the resume. The reader has it. Use the letter for the story behind one line of it.

Opening with "I am a hard-working team player". Everyone does. Start with the role and your reason.

Leaving out location and time zone. For a remote role this is one of the first things checked. A recruiter who cannot tell whether they are allowed to hire you will often just move on.

Writing a letter that fits any company. Swap the company name for another one. If the letter still works, it is too generic.

Claiming remote skills with nothing behind them. "Excellent async communicator" proves nothing. A link to your documentation, or a short story, does.

Going long. A page and a half buries the point. Cut.

Typos and wrong names. A remote team reads your writing as a preview of your work. Read the letter aloud once, and check the company name twice.

Tailoring only the greeting. If you adapt the letter for each posting, adapt the middle too, not just the first line.

Common questions

Do I need a cover letter if the posting says it is optional?

No, but for remote roles a short note usually helps, because it is the first sample of your writing. If you are sending dozens of applications and cannot write a full letter for each, write one good cover note and rework its first sentence every time.

Should I use a template?

To get started, yes. The structure helps, but the content has to be yours. Hiring managers recognize a letter that still has the template's phrasing in it.

Can I use AI to write it?

You can use a tool to draft or tidy, but read what comes back with care. The letter exists to show how you write and think. Generic text, or claims you could not defend in an interview, will hurt you. Keep your own facts, your own examples and your own voice.

What if I have no remote experience?

Use what you have: work with people in other offices, freelance clients, volunteering, open source, anything you published. The third paragraph can describe how you plan to work remotely, backed by one real example of working on your own.

Should the letter be a PDF or text in the email?

Do what the posting says. If it says nothing, put a short version in the email body and attach the full letter as a PDF. For the resume itself, see the next article on how to make an ATS-friendly resume.

Takeaways

• Remote teams read writing closely, and your letter is a small sample of it.
• Four short paragraphs: role and reason, one proof, how you work remotely, a plain close.
• Always give location, time zone and overlap hours.
• Treat the template as scaffolding and delete any slot you cannot fill truthfully.
• For forms, write three to five sentences with one fact specific to the company.

The letter works best next to a resume that software can parse properly. Here is how to make your resume ATS-friendly.