Most advice about resume templates is really advice about taste, which is why it is so unhelpful. A template is not decoration. It is a set of decisions about what a reader meets first, what they meet second, and how much room each part of your history gets. Choosing one is choosing the order in which your evidence is presented.
What a template actually changes
It changes three things and only three things: the order of sections, the space allocated to each, and the visual weight that tells a skimming reader what to look at. It does not change your content, and it cannot rescue content that is not there.
That is worth stating because the most common mistake is treating template choice as the interesting decision. It is a real decision, but it is a small one next to whether your bullets describe outcomes. A brilliant resume in a plain layout beats an ordinary one in a beautiful layout in every screening process that has ever existed.
The one-sentence version
Pick the layout that puts your strongest evidence where a six-second skim lands. For a graduate that is education and projects. For a senior individual contributor it is skills and systems. For a director it is scope.
One column or two
This is the first real fork. A two-column layout puts contact details, skills and languages in a sidebar and experience in the wider column. The benefit is genuine: a reader checking whether you have used a specific tool finds the answer at eye level, before they have begun reading your history. In engineering, data and design, where tooling is a real filter rather than a formality, that is worth having.
The cost is also genuine, and it is twofold. A sidebar takes roughly a third of the page width, so the experience column has to be disciplined: four bullets a role rather than eight. And a two-column layout is the single most reliable way to break an applicant tracking system, because a parser reading across the full page width interleaves the two columns into alternating fragments.
The resolution is not to pick a side. Keep a two-column version for the human and a single-column version for the upload form. They hold identical content.
Chronological, functional, or hybrid
Reverse chronological lists roles newest first. It is the default nearly everywhere, and it is the default because it answers the question a reader is actually asking: what are you doing now, and how did you get there.
Functional groups achievements by skill and pushes employment history to a bare list at the bottom. It is usually a mistake, and it is worth being blunt about why: recruiters know it is the format people reach for when they are hiding something. Using it announces a gap or a job-hopping pattern more loudly than the gap itself would have. It also removes the reader's ability to tell when you did any of it, which is the first thing they will try to establish.
Hybrid keeps the reverse-chronological history but opens with a short block of the most relevant capabilities. This is the right answer for a career change, and it does the job people reach for functional format to do, without the signal that comes attached. Lead with the translated skills, then let the chronology speak.
Match the layout to your career stage
- Student or first job. Education near the top with coursework named, then projects, then any work. The strongest evidence you have is not employment, and a layout that leads with three months of part-time work buries the degree that is actually doing the work.
- Two to eight years. Experience first, education reduced to a line at the bottom. Skills near the top if your field filters on tools.
- Senior individual contributor. Experience, weighted heavily toward the last two roles. Older roles get a title, a company and a date. A layout with room for a technical skills block earns its space here.
- Manager and above. A summary that states scope, then experience. Team size, budget and remit belong in the first third of the page, because scope is what a reader needs before any individual achievement means anything.
Match the layout to your field
Field convention is a stronger constraint than most people expect, and violating it reads as not knowing the field.
Law, academia, medicine, accounting and most of finance expect a plain serif document with no accent colour. In those fields colour reads as decoration, and decoration reads as someone compensating. Tech, design, marketing and startups are relaxed about a single accent colour and a modern sans-serif, and in design specifically the resume is itself a work sample.
If you genuinely do not know the convention in a field you are entering, choose the plainer option. Being slightly under-designed costs you nothing anywhere. Being over-designed costs you in about half the market.
Colour, type and whitespace
- One accent colour, used for structure. Section headings or a rule. Not four colours, and not a coloured block behind body text, which hurts both readability and printing.
- One typeface, two if you are confident. Anything standard is fine. The reader is not scoring you on the choice, but they will notice a font that is hard to read at eleven points.
- Whitespace is not wasted space. It is what makes a page skimmable. A resume crammed to the margins to fit one page is harder to read than a well-spaced two-page document, and being hard to read is the only formatting sin that reliably costs you.
- No photo, in the US, UK, Canada, Ireland or Australia. It invites a discrimination claim and many employers discard such resumes for that reason alone. In much of continental Europe it is still expected. Check the market you are applying into.
Traps that look like good design
A handful of template features are popular, look professional in a preview, and actively work against you in a screening process. They are worth naming because each one is something a designer put there deliberately.
Skill rating bars. Five dots, four filled. They communicate nothing: nobody knows what four-fifths of Python means, and you have just told a reader you are 80% competent at something rather than describing what you built with it. They also carry no text, so to any parser the skill simply is not there. If you want to convey depth, say "six years" or name the hardest thing you did with it.
Icons instead of labels. An envelope glyph beside an address and a phone glyph beside a number look tidy and reduce to an unlabelled string of characters the moment the file is parsed or read aloud by a screen reader. Icons alongside a text label are fine. Icons replacing one are not.
Headers and footers. Putting your name and contact details in the document's header region is a normal thing to do in a word processor and one of the most reliable ways to become uncontactable, because that region is frequently discarded during extraction. Keep them in the body.
Timelines and infographics. A visual career timeline down the left margin is a two-column layout wearing a costume, with the added problem that the dates are now positional rather than textual. Beautiful in a portfolio. Unreadable to the system that files it.
The template is not the document
One practical habit makes every other decision on this page cheap: keep your content separate from its presentation. Write and maintain the actual substance once, and treat the layout as something you apply to it, not something you write inside.
This matters because you will need more than one version. The plain single-column file for application forms. The designed version for a recruiter who emails you or for the interview panel. Possibly a longer one for a field that expects a CV. If those are three separately maintained documents, they drift, and eventually you send a version with a role missing or a two-year-old job title.
It also means that changing your mind about a template costs nothing. If the layout is a decision applied to the content rather than baked into it, trying the plainer version against a posting is a click rather than an evening.
Deciding in sixty seconds
Ask three questions in order. What is the strongest evidence I have for this specific job? Does my field expect a plain document? Is this going to an upload form or to a person?
The first answers what goes at the top. The second answers how much visual design is safe. The third answers whether you send the designed version or the plain one. Everything else is preference, and preference is not what is being assessed.
See the layouts side by side
Every template rendered with the same content, so the only thing changing is the decision the layout makes. Each one notes who it suits and why.
Browse the templates