A hiring manager may read thousands of applications over the course of a career. A sought-after role at a well-regarded company can draw anywhere from tens to thousands of applicants, and every one of them costs the team time and energy before anyone reaches the interview stage. Writing with that reviewer in mind — and getting the details right — is the surest way to stand out.

Presentation before content

Spelling, grammar and formatting carry real weight. Typos and errors read as red flags: they suggest either inattention to detail or a reluctance to go the extra step. Running spell check and having a second person proof the document is cheap insurance.

  • Separate sections with headings.
  • Summarize highlights as lists so the document can be scanned.
  • Choose a legible font and font size.
  • Use line spacing that lets the content breathe.
  • Apply bold and italic to pertinent information without overusing them.

Skill charts and hobby lists are a matter of taste, but they show up more often on the applications of beginners — including them may unintentionally signal less experience.

Filling gaps with real work

Thin work history is not disqualifying. Open source contributions, side projects or your own site can demonstrate the kind of work you are capable of, and a solid portfolio, GitHub contributions or a few CodePen demos have been enough to earn a chance for candidates with slim-to-no commercial experience. Not everyone has spare time for side projects, so this is not a hard requirement — it is a way to compensate when relevant work experience is otherwise lacking.

Write experience as outcomes

Every entry in your work history should answer one question: what did you accomplish? That framing delivers substance without fluff. Consider this example:

Due to my team's work refactoring the product page, we were able to meet the demands of our customers, which resulted in a 25% growth in sales. We also took the opportunity to upgrade the codebase from React.createClass to React Hooks for all of our components, ensuring a more flexible and maintainable system.

It shows the candidate can deliver goals as part of a team, understands technical debt, and takes initiative on maintenance. Describe outcomes from the perspective of what you provided for the team.

Bootcamp backgrounds

Applicants arrive with widely varying degrees of experience, and it is safe to assume you are not the most experienced person in the pool. If your development experience comes from online or in-person coding bootcamps rather than commercial projects, talk through it: what you learned there, what interested you, what your final project was, and whether there is a link to that work. For candidates early in their career, hiring managers look mostly for curiosity and a willingness to improve.

Length and contact details

Keep the resume as brief as possible — ideally a single page, with two acceptable only if you really need them. The constraint is a challenge to focus on the most important details; having more to say than fits is a good problem. Padding a resume across multiple pages conveys an inability to communicate succinctly at best, and a lack of respect for the hiring manager's time at worst.

Name, email and phone number are hard requirements, yet resumes that are otherwise impressive still omit them. No one wants to hunt for your email while managing a large candidate pool — most likely, they simply will not.

Tailoring the application

Include a cover letter, and use it to show you have done at least a little research on the company, understand what they need in a candidate and can explain how you fit that need. The descriptions in the resume itself — the takeaways and outcomes, not the job titles — can likewise be adjusted so your skills connect directly to the position.

Ordering

Both work and education details belong in reverse-chronological order. Recent work is a better reflection of what you can do today and of how fresh your skills are, and it is what compels a reviewer to keep reading.