Somebody on LinkedIn will tell you your resume must fit on one page. That person has never staffed a contract role. Recruiters filling a Senior Data Engineer position at a bank do not want your career story compressed into eleven-point font with half-inch margins. They want to see what you actually did, on which stack, for how long.
If you have 10+ years in the field, a two-page resume is not a red flag. It is the expectation. The debate is over. The real question is not length. It's what earns a spot on that second page and what gets cut without mercy.
This is a decision framework, not a template. Use it to stop agonizing over white space and start making every line justify itself.
Why the one-page rule never applied to you
The one-page myth comes from entry-level and early-career advice. It made sense when you had two internships and a class project. It stops making sense the moment you have five-plus roles, multiple stacks, and measurable outcomes to show.
Compressing 12 years into one page means you're cutting real signal: the migration you led, the outage you prevented, the team you scaled. Recruiters and hiring managers reviewing senior IT and consulting candidates expect two pages. Anything less on a veteran resume reads as either inexperience or a rushed application.
What belongs on page one
Page one is your highlight reel. It has to work in the six to eight seconds a recruiter actually spends on first pass, and it has to survive an ATS keyword scan.
- Summary, 3-4 lines max. Role focus, years of experience, core stack, one standout outcome. No adjectives like 'passionate' or 'dynamic.'
- Core skills block. The technologies, tools, and platforms that match the roles you're targeting. This is for the ATS as much as the human.
- Your two or three most recent roles, in full. Company, title, dates, and 4-6 bullets each focused on scope and outcome, not task lists.
If a recruiter reads only page one and stops, they should already know you're qualified for the role in front of them.
What belongs on page two — and only page two
Page two is where depth lives. It is not a dumping ground for everything that didn't fit above. It has a job: back up page one with detail a technical screener or hiring manager will actually look for.
- Older roles (4+ years back), condensed. Two or three bullets each, not the full six. Show progression, not repetition.
- Certifications and training. PMP, AWS, Azure, Scrum, security clearances if applicable. Group them so a scanner catches them fast.
- Notable projects or contract engagements that show range across industries or platforms, especially if you've worked multiple contracts through a staffing partner.
- Education, unless you're 25 years into your career, in which case a single line is plenty.
- Technical stack detail that didn't fit in the summary — specific versions, tools, methodologies, especially if the role you want is technical and specific keyword matches matter.
Nothing on page two should be information a hiring manager needs to make the first cut. That's page one's job. Page two answers the questions that come up in the second look, right before someone picks up the phone.
What to cut, no matter how proud you are of it
Every consultant has that one line they refuse to delete. Cut it anyway if it doesn't do one of two things: prove capability for the role you want next, or differentiate you from the next candidate in the pipeline.
| Cut it | Keep it |
|---|---|
| Objective statements ('Seeking a challenging role...') | Quantified outcomes ('Reduced deployment time by 40%') |
| Every task from every role since 2005 | Scope and impact from your last 3-4 roles |
| Soft-skill adjectives with no evidence | Specific tools, versions, and methodologies |
| References or 'references available upon request' | Certifications relevant to the target role |
| Roles older than 15 years, in detail | A one-line summary of very early career, if at all |
A quick gut check before you hit send
Print it. Actually print it. Screens lie about length and white space in ways paper doesn't. If page two feels thin, or if it's just page one restated with different verbs, you don't need two pages yet. If page two is full of substance a technical reviewer would care about, you've earned it.
Ask yourself three questions for every bullet on the page:
- Does this tell a recruiter or hiring manager something they need to know to say yes?
- Would a technical screener ask me about this in a phone interview?
- Is this the newest, most relevant version of this skill or achievement I can show?
If the answer is no across the board, cut it. Two pages of substance beats one page of summary or three pages of padding, every time.
If you want a second set of eyes on where your resume earns its second page and where it's just taking up space, the Josh Pros LLC team reviews consultant resumes daily as part of how we match people to contract roles nationwide. Send us a copy at contact@joshpros.com or find us at https://joshpros.com — no pressure, just a straight read.
#TwoPageResume #SeniorITResume #ConsultantResume #ITConsultingCareers #ResumeTips #TechJobSearch #ContractConsulting #ITStaffing #ResumeWriting #CareerAdviceIT #JoshProsLLC #TechRecruiting
Talk to a real recruiter, not a bot.
We'll tell you the rate, the client, and the terms before you interview. And if we're not the right fit, we'll say so.