Web developer resume tips
A web developer resume should name a site a person used and the part you built: pages, a content system, forms, or the publishing path. A grid of frameworks does not say whether you shipped. Reviewers look for the site, the constraint, and the language you wrote.
Cover letter for a web developer
What to put first
Put the kind of site in the first lines: marketing pages, a store, a logged-in product, or a site an editor updates. Then the part you owned and the stack you wrote it in. If a designer or an editor owned a piece, say so.
The page and the person
Name who the site was for and what they could do when you were done. "Built a website" is weaker than the form, the catalog, or the article template you actually finished.
The stack you can defend
List HTML, CSS, and JavaScript, plus a framework or a content system, only where a bullet shows the use. A tutorial you finished and did not ship stays off the skills line.
Text a hiring system can read
Keep the title and the stack in the document body, not only in an image. Dates and employer names belong in text so they are not trapped in a header graphic.
An example line
Adapt this only where it is true for you. It is a shape for a bullet, not a claim that a particular person did this work.
Shipped the article templates for a publisher: editors could place images and calls to action without a developer, and the pages stayed readable on a phone.
What to leave off
Leave off frameworks you would need to relearn from the start, sites you only staged, and performance scores you cannot explain. Leave off a design you did not draw written as if you had.
Questions
- Is a portfolio required?
- A link helps when you are allowed to show the work. The resume should still name the site and your part if nobody clicks.
- What if I used a site builder?
- Say so. Configuring a builder for a real client is different from writing the templates, and both can be honest lines.