Originally published on the CVFit blog. Also on Medium.
I'm Momin, founder of CVFit in Ottawa. I build a tool that helps people tailor a resume to a specific tech job using only work they have actually done. The summary at the top of a resume causes more confusion than almost any other section, and the answer is less absolute than most advice makes it sound.
Full disclosure: this is my product area, and I have a point of view. The evidence below comes from published studies and surveys, plus conversations with recruiters and hiring managers. Where the research is old or limited, I'll say so.
The first look is very short
The most quoted timing figure still comes from an eye-tracking study by Ladders in 2018, which recorded an average first screen of 7.4 seconds. That work was done in a lab, years ago, so treat it as a rough guide rather than a rule. Newer data points in the same direction: a 2025 survey by Novorésumé of more than 200 HR professionals found 42% spend under 10 seconds on an initial review. Canada's Job Bank, by contrast, gives a more generous estimate of about 30 seconds to skim a resume.
Whatever number you trust, the first pass is brief, and the top third of the page carries a lot of weight.
Recruiter Ron White turns that into a test: set a timer for seven seconds and ask whether a reader can tell what role you want, your strongest measurable result, and your level — without scrolling. A summary is not a personal statement. It is where those three answers can sit together.
Recruiters usually start with experience
The same Novorésumé survey found 79.4% of HR professionals check work experience first, while only about 10% said the summary or objective is where they look first. The Ladders study also found recruiters spent more time on job titles than on any other element. At the same time, that study listed an overview at the top of the first page among the traits shared by the best-performing resumes.
Those findings fit together. Most readers jump to your titles and most recent role, then glance back to check whether the summary matches. Hiring manager Krista Kelly notes that what a reader encounters first carries extra weight and shapes how they read everything after it. So a summary rarely wins an interview on its own — it frames the rest of the page. When it is vague, or claims more than the bullets below can support, it works against you.
What the screening software does with it
Much summary advice is really keyword advice, built on the idea that software rejects your resume before a person sees it. The picture is more mixed.
Harvard Business School's Hidden Workers report found more than 90% of employers surveyed use their systems to initially filter or rank candidates, and 88% agreed that qualified, high-skill candidates get screened out because they do not match the exact criteria in the job description.
On the other hand, when Enhancv interviewed 25 US recruiters in 2025, 92% said their ATS does not auto-reject resumes based on content or design; rejection mostly came from knockout questions such as work authorisation or location. What recruiters clearly do is search: Jobscan's survey of 384 recruiters found 99.7% use filters, and 76.4% filter by skills. So the summary is a reasonable place to use the posting's exact name for a skill you really have — "React" instead of "front-end frameworks." It is a poor place to stuff in skills you cannot point to below. The Ladders study flagged keyword stuffing as a trait of the worst resumes.
Should a new grad use one?
This is where advice splits most. Washington University in St. Louis tells students that most college students can skip a summary, but that a summary is highly recommended for technical and engineering resumes. Virginia Tech says a professional summary is typically recommended for more seasoned candidates, and suggests an objective for students and career changers who do not yet have a strong history in the field. The University of Toronto Mississauga career centre gives the most practical test: use a summary of qualifications when your skills come from a mix of projects and jobs that would take a reader time to piece together, and skip it when the top half of the page already shows you are qualified.
For a new graduate applying to a junior developer or data role, that test usually points toward a short summary. Your strongest evidence is often spread across a capstone, an internship and a side project, and none carries the job title the posting asks for. Two lines that name the target role and connect those pieces save the reader the work. What does not work is a generic line like "Motivated computer science graduate seeking opportunities to grow" — it adds nothing the education section does not already say. Heidi Ram of The Product Recruiter makes the same point: contrast a resume that lists tools and tasks with one that shows use cases, business value and outcomes.
How to write a summary you can stand behind
A useful summary has three parts, each pointing to something lower on the page. First, the role and level you are targeting, in the posting's words — "Junior backend developer" is clearer than "software professional." Second, two or three skills the job asks for that your resume proves. If the posting lists Python, SQL and AWS and your projects use Python and SQL, name those two. Leave AWS out unless it appears in a bullet. Third, one concrete result, even a small one, with a number that is yours and not a template's.
Then rewrite the summary for each kind of role you apply to. It is the cheapest part of your resume to tailor and the part a reader sees first. The rule is that every claim in those lines must be one you could defend in a screening call.
Four questions before you keep it or cut it
- If someone covered everything below your summary, could they name the role you want and your level?
- Does every skill in the summary appear again in a project or experience bullet?
- Is the summary doing something your most recent role doesn't already do on its own?
- Would you change at least one line of it for the next job you apply to?
If you answer no to most of these, the summary is probably costing you space. Cut it, or rewrite it around the one job you are applying to now.
If you want a quick read on whether your resume and summary line up with a specific posting, CVFit's free match checker compares the two, and a first check does not need an account. New accounts get one month of Pro free, with no credit card.
For tech roles, do you read the summary, or go straight to the first bullet of the latest role? If you hire for tech, I'd like to hear how you read it — I'll be in the comments.
Read the original post on CVFit: Does the resume professional summary still matter for tech jobs?
Top comments (0)