Replace the [bracketed] placeholders with your own details - or open it in the editor and do it there. Switch levels to see the letter rewritten for junior and senior applicants.
Dear Hiring Manager,
I am writing to apply for the Web Developer position at [Company Name]. For the past five years I have built and maintained production websites for a living - currently fourteen client sites in Next.js and TypeScript, shipped from a shared component library at a pace of roughly thirty releases a month. The web I like building is the measurable kind: fast, accessible, and judged by what happened after launch.
The project I would show you first is a storefront rebuild for our largest retail client. The site was losing mobile shoppers to slow pages, so I rebuilt it against a performance budget: Largest Contentful Paint fell from 4.2 seconds to 1.6, and checkout conversion rose 9 percent in the quarter that followed. I also led the accessibility pass that brought every site we manage to WCAG 2.1 AA - more than three hundred issues found with axe and a screen reader, fixed, and then locked in with automated checks in CI so the work could not quietly rot.
Day to day I work across the stack: React and Next.js on the front, Node and PostgreSQL behind it, with enough pipeline ownership to have cut our build-and-deploy time from twelve minutes to four. I write semantic HTML first and add JavaScript when the page earns it - an unfashionable order that keeps sites fast.
What draws me to [Company Name] is that this role owns real product surface rather than a queue of tickets. I want to be measured on what the site does for its users, because that is how I already work.
Thank you for your consideration. I would be glad to walk through the storefront rebuild, code and numbers both.
Sincerely,
[Your Name]
Run your finished letter through these checks before you send it.
The opening states the portfolio, not the passion
Fourteen production sites, a shared component library, and thirty releases a month tell a hiring manager the candidate ships constantly and maintains what they ship. That is a stronger opening claim than any sentence about loving the web could be.
The rebuild story pairs a metric with its mechanism
Largest Contentful Paint from 4.2 seconds to 1.6 is a number; the performance budget it was rebuilt against is the method. Together they promise the result can be repeated on the reader's site, which is the only reason to hire for it.
Accessibility is presented as finished work, not a value
Three hundred issues found with axe and a screen reader, fixed, and locked in with automated checks is a completed engineering project. Most letters mention accessibility as a belief; this one shows the audit trail.
The stack paragraph doubles as an opinion
Semantic HTML first, JavaScript when the page earns it - the letter states how the developer decides, not just which tools they hold. Reviewers hire the decision-making, because the tools change every few years.
Swap in your own launch numbers
Load time, conversion, bounce rate, search ranking - use whichever your project actually moved. If nothing was measured, run Lighthouse on a site you built and report the scores honestly; measured late is still better than unmeasured.
Match the framework sentence to the posting
This letter says Next.js because the writer uses it daily. If the posting says Vue or Rails, your equivalent goes in that sentence - and nowhere else, because one stack sentence is the right amount for a letter.
Rewrite the closing paragraph around their site
Spend ten minutes on the company's actual site before writing it. A specific observation - their checkout, their blog templates, their page speed - turns the closing from flattery into the start of a working conversation.
Keep the accessibility claim at your true level
WCAG 2.1 AA is a specific, checkable standard. If your experience is alt text and contrast fixes, say that instead; inflating an accessibility claim to someone who can test it in minutes is a bad first commit.
A letter that is a frameworks inventory
Naming every library you have ever installed reads as padding and tells the reviewer nothing about judgment. One project with a before and after says more than twenty proper nouns in a row.
Showing only greenfield work
Most web jobs are maintaining and improving sites that already exist. A letter with no maintenance, migration, or debugging story reads junior at any experience level, because it hides the half of the craft the job will actually demand.
Linking a portfolio that contradicts the letter
If the letter claims performance and accessibility, the reviewer will run your own site through Lighthouse. Slow, inaccessible portfolio pages sink the application fast - check yours before you send anything.
Claiming full-stack without evidence on either end
If you say full-stack, the letter needs one concrete thing from each side - a frontend outcome, and an API, query, or pipeline you built. Otherwise say which end you are strongest on; honesty scans better than breadth.
Use the ones that are true of you, in the sentences where you describe the work - not as a list bolted to the end. Matching a job description's vocabulary helps a keyword filter find you; it is not what convinces the person who reads the letter afterwards.
Should a web developer cover letter link to a portfolio?
Yes - a portfolio or a live site you built is the strongest evidence a web developer has, and the letter should name it early. Make sure the linked pages load fast and pass basic accessibility checks, because a reviewer who has just read a letter about performance will test the link against it.
Do I need a computer science degree to apply?
Many working web developers do not have one, and most postings that mention a degree accept equivalent experience. What replaces the credential is evidence: production sites, a maintained repository, and a letter that talks in measured results. Address the path you took in one sentence, without apology, and spend the rest on the work.
How technical should the letter get?
Concrete but readable: name the metric, the standard, or the tool, and skip implementation detail. A line that says Largest Contentful Paint fell from 4.2 to 1.6 seconds works for the recruiter who reads speed and the lead who knows the metric. Save the architecture discussion for the interview the letter earns you.
What if my experience is mostly WordPress or site builders?
Own it - a large share of the web runs on WordPress, and maintaining client sites on it is real development work. Frame it in outcomes the way this letter does: launches delivered, load times improved, plugins replaced with faster code. Then note whatever modern-stack work you have alongside, at its honest depth.