Many tech roles do not require one, but a short, specific note helps when it is asked for, when you are switching careers, or when your resume needs context. Keep it to three short paragraphs: why this company, one piece of proof that matches the role, and a clear close. Generic letters are worse than none.
What people tell me
Some applications ask for a cover letter, some make it optional, and some do not mention it. I usually either skip it or paste the same long letter I found online with the company name changed. I have heard that nobody reads them in tech, but I have also heard they help when your resume is thin. I am a junior developer and I do not know when it is worth writing one or what to put in it.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- Write one when it is requested, when you are changing careers, or when your resume needs context such as a gap or relocation.
- Keep it to about 150 to 250 words. Hiring teams skim.
- Three parts: why this company specifically, one proof that matches their need, and a short close.
- A generic template letter can hurt you. Specific and short beats polished and long.
- The same structure works as a LinkedIn message or an application form's "why us" box.
Do you actually need one?
In software hiring, many recruiters and engineers skim resumes and portfolios first and may never open the cover letter. But "many" is not "all", and there are situations where a short letter clearly helps.
| Situation | Write one? | Why |
|---|---|---|
| The application asks for it | Yes | Skipping it can look careless or fail a required field |
| Optional field, small company or startup | Usually yes | Founders and small teams often read them |
| Large company portal, optional | Optional | A short one does no harm; skip if you are short on time |
| Switching careers | Yes | Your resume alone does not explain the move |
| Relocation, a gap or an unusual path | Yes | Context prevents wrong assumptions |
| You are being referred | Short note | The referral does most of the work |
What a good one looks like
Think of it as a short email to a busy engineer, not a formal letter.
Paragraph 1: why this company
One or two sentences that could not be copied to another company. Mention something real: their product, a feature, an engineering blog post, the problem they solve.
Paragraph 2: proof that matches
Pick the one or two requirements from the job post that matter most and show evidence for each. Numbers and outcomes help.
Paragraph 3: close
One sentence on what you would like to happen next.
Example (junior frontend developer)
Dear hiring team,
I have used your scheduling app for group projects at university, and the way it handles time zones without asking the user is the kind of detail I enjoy building. That is why the Junior Frontend Developer role caught my eye.
Your post mentions React and accessibility. I recently rebuilt a clinic's booking form in React with keyboard navigation and screen reader support, which cut incomplete bookings in half over the first month. I also contributed two accessibility fixes to an open source component library, both merged.
I would welcome the chance to talk about how I could help your team ship accessible features. Thank you for your time.
That is under 150 words, specific, and easy to read on a phone.
Writing yours in six steps
- Read the job post twice and underline the two or three requirements that appear most important.
- Find one real detail about the company. Five minutes on their site, product or blog is enough.
- Match evidence to requirements. One project or experience per requirement.
- Draft without worrying about length, then cut to 150 to 250 words.
- Remove clichés: "I am a passionate and hardworking individual", "I believe I am the perfect fit", "To whom it may concern".
- Read it aloud. If it sounds like a template, rewrite the first paragraph.
Keep a reusable base
You do not need to write every letter from scratch. Keep:
- A base second paragraph for each role type (frontend, backend, full stack)
- A list of your best evidence lines with numbers
- A short closing line
Then write only the first paragraph fresh for each company. That takes about 10 minutes.
Special cases
Career switchers
Use the letter to connect your previous work to the new role. "In three years of operations work I automated our weekly reporting with Python, which is how I discovered I preferred building the tools." If you are switching without a degree, this answer covers the wider picture.
A gap in your resume
One honest line is enough: "After a year caring for a family member, I have spent the last four months rebuilding my skills with two full stack projects." Do not over-explain.
Relocation or remote roles
State your situation clearly: time zone overlap, notice period, and whether you need sponsorship. Hiding it only wastes both sides' time.
A two-week plan to build your kit
| Days | Task | Output |
|---|---|---|
| 1 to 2 | Collect your best 6 to 8 evidence lines with numbers | Evidence bank |
| 3 to 4 | Write base second paragraphs for your role types | 2 to 3 base paragraphs |
| 5 | Write your closing line and signature | Reusable close |
| 6 to 10 | Use the kit on real applications, one fresh first paragraph each | 10 or more tailored letters |
| 11 to 14 | Compare responses, tighten weak lines | Improved kit |
Common mistakes
- Repeating the resume in sentence form. The letter should add context, not duplicate.
- Writing a full page. Nobody in a hiring pipeline wants to read a page from a junior applicant.
- Getting the company name wrong because you reused a letter. This happens more often than you would think and is hard to recover from.
- Using AI output unedited. It is fine to use AI to tighten wording, but generic AI letters read very similarly. Your specific details are what make it work.
- Focusing on what you want. "This role will help me grow" is about you. Show what you would bring.
Where a cover letter fits
A cover letter rarely rescues a weak resume, and a strong resume rarely needs a letter. Get the resume right first: why your resume is not getting shortlisted walks through the common gaps. The Job search cheat sheet summarises the rest of the application kit.
If you are still stuck
How to apply for software engineering jobs covers the full application process. If you want feedback on how your applications read, join Sefism. It is free to learn, you get credits when you join and your first roadmap is free, and as a member you can ask your own question.
Was this answer helpful?
Read next
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open: sign up and your account is active shortly after. Prefer to talk? A free call works too.