This year I’ve directly hired for lots of different engineering positions and skillsets: in particular, Ruby on Rails, React, DevOps, and QA. In the process, I’ve read through thousands of resumes. Some patterns and anti-patterns have become clear.

I can’t speak for any other Head of Engineering or recruiter, but here’s a short guide to getting your resume noticed by me. Perhaps these ideas will help you with other people who are hiring, too.

Your resume is a story about you.

I’m a real human being who will read your resume from top to bottom. I’d love to understand a little about you before I dive into your history: in particular, what’s driven you in your career so far, and what you’re looking for from your next position.

It’s best to avoid clichés. “I’m passionate about building high quality software as part of a dynamic team” doesn’t tell me anything at all. On the other hand, “I’m excited about cryptocurrency’s potential to disrupt centralized finance” or “I’m concerned about the widening wealth gap and want to work on projects that help the underserved” both speak volumes. Don’t be afraid to be specific and personal.

I hire for mindset as much as I hire for specific skills, so the more I can learn about you, the better. Are you empathetic, a great communicator, a team player, ego-free, and excited to grow? Those are things I really want to know.

It’s got to be legible.

Any good story needs to be read. That means using clear language with complete sentences, set in a layout that’s easily parsed.

In left-to-right languages, left-aligned text is easier to read. Pay attention to your typeface, line height and headings. You don’t have to be a designer, but keeping your layout consistent, simple and readable demonstrates attention to detail. Similarly, you don’t have to be a great writer, but full sentences and easy-to-follow text demonstrate clear communication.

By the way, I don’t mind how you set your resume up. Most people use a word processor, but I’ve seen plenty of LaTeX typesetting, and I’m always impressed when I see well-written HTML. Whatever works for you is great.

Use as many pages as you need.

Some people ask for a one-page resume. I’d rather you took the time and space you need to represent yourself well. If it’s five pages long, I promise I’ll read all five pages (as long as they’re relevant).

I always follow your links.

Whether you’re using HTML or have sent me a PDF, I’m going to follow any link you give me to demonstrate your work. The more the merrier.

I don’t care where, or if, you went to school.

There are some people who specifically look for a “top 20” school or a prestigious CS course. I’m not one of them.

Particularly in a world where college costs tens of thousands of dollars a year to attend, only some people can take this journey. Even if you have the money or can get a scholarship, you might have had to be a carer for your family. Or you might just have taken a non-standard path through life. Why would I penalize you for that?

I care about what you can do, not whether you’ve conformed to an approved career path.

Don’t worry about “culture fit”.

Culture fit is one of the pervasive, bad ideas in tech hiring. Instead, I like to ask the question: what new perspective will this candidate bring to our team? If you can convey that in your background or work experience, that’s fantastic.

I like context.

A list of skill keywords doesn’t tell me much. Some candidates draw a little progress bar next to each one to show their relative proficiency; that tells me a little more, but it also feels like a character sheet from some technology-themed roleplaying game. It doesn’t let me know how you’ve used those skills.

After your introductory description, the work experience section of your resume is the most most important. I’d love to understand the work you did at each position, and this is an opportunity to discuss the technologies involved. Please do namecheck them here, but do it as part of a description of what that work involved.

I’m not an algorithm, and I’m not keyword searching your resume. I am interested in the technologies you’re proficient in, and how you used them in context. Again: tell me a story.

Finally: skip the photo.

Some people like to include a photo of themselves to give their resume more human character. I appreciate the thought, but please don’t do this.

I don’t want to select candidates based on what they look like, and no employer should. For the same reason, I typically like to conduct interviews over voice, not video (except for pair programming sessions, where some video sharing is necessary).

It’s about how you think and who you are, not how you appear.

*

Looking for an engineering position? ForUsAll is hiring. We’re looking for Ruby on Rails and DevOps engineers, as well as product managers and a host of other roles.