Best Things to Put at the Top of Your Resume
The top two inches of your resume do most of the work. Recruiters scan from the top down, and the first thing they see determines whether they keep reading or move on. Studies on how recruiters actually read resumes confirm this. The initial glance is fast. You get about 6 seconds before they decide if you are worth a closer look.
That means what you put at the very top is not a design choice. It is a strategic one. Here is what works best, ranked by how much it helps during that first scan.
1. Your Name and a Headline
Your name should be the largest text on the page. Not huge, but clearly the first thing the eye lands on. Right below it, add a one-line headline that tells the recruiter exactly who you are and what you do.
A good headline looks like this: "Senior Backend Engineer · Payments · Go/Rust." That is three pieces of info in under ten words: your level, your domain, and your tools. The recruiter now knows if you are in the right ballpark before reading a single bullet point.
A bad headline is your job title alone: "Software Engineer." That tells them nothing they could not guess from the fact that you sent a resume for an engineering role.
Headline formula
[Seniority + Role] · [Domain/Industry] · [Top 2 Technologies]
Examples: "Staff Frontend Engineer · E-commerce · React/TypeScript" or "DevOps Lead · FinTech · AWS/Kubernetes" or "Data Engineer · ML Pipelines · Python/Spark."
2. A URL to Your Full Profile
Put a link to your web profile right below your name and headline. A clean URL like cvin.bio/yourname works well. It is short, easy to remember, and gives the recruiter a way to see your full background in a properly formatted layout.
This matters because your resume is a summary. It cannot hold everything. A profile link lets the recruiter dig deeper on their own terms. It also makes you easy to share. When the recruiter forwards you to the hiring manager, they paste the URL into Slack instead of attaching a file. You can read more about why this works in our guide on putting a URL on your resume.
Best for: anyone in tech. Recruiters expect to see a link to something, whether it is GitHub, a portfolio, or a profile page. Having nothing clickable at the top is a missed opportunity.
3. A Two-Sentence Value Summary
Not an objective statement. Not a paragraph. Two sentences that tell the recruiter what you bring and why it matters. Think of it as your answer to "why should we talk to this person?"
Good example: "Backend engineer with 7 years building payment systems that handle $2B+ in annual transactions. Led the team that cut checkout latency by 40% at a Series C fintech."
Bad example: "Passionate software engineer seeking a challenging role where I can grow my skills and contribute to an exciting team." That second one is an objective statement, and it tells the recruiter nothing useful. It is about what you want, not what you offer.
4. Your Strongest Skills
List four or five of your strongest technical skills right after your summary. Not fifteen. Not twenty. Just the ones that are most relevant to the kinds of roles you are applying for.
This works because it gives the recruiter a quick filter. They scan your skills, see "Go, PostgreSQL, gRPC, AWS, Terraform" and immediately know if your stack matches their team. If you list too many, you dilute the signal. The recruiter does not know if "Docker" means you ran it once in a tutorial or you manage 200 containers in production.
Pick the skills you could talk about for 30 minutes in an interview. Leave everything else for the experience section where you can show how you used it.
What NOT to Put at the Top
Some things waste your most valuable real estate. Here is what to remove or move further down.
Objective statements. "Seeking a role where I can grow" does not help the recruiter decide if you are qualified. Replace it with a value summary that describes what you bring.
Your full home address. City and country are enough if the role is location-sensitive. Nobody needs your street name and zip code at the top of your resume. It is a privacy risk and a waste of space.
A photo. In many countries, including the US, adding a photo can trigger bias concerns. Even where photos are common, they eat up space at the top that your headline and summary need more.
Date of birth. Irrelevant to your qualifications and creates age bias risk. Leave it off entirely.
The test
Cover everything below the top two inches of your resume. Can a recruiter tell from just that visible area what you do, what level you are at, and what makes you worth calling? If not, rearrange until they can.
How Recruiters Actually Read
Eye-tracking studies show that recruiters follow a rough F-pattern. They read the top line fully, scan down the left side, and occasionally dart right when something catches their attention. This means the left side of your top section gets the most eyeball time.
Put your name and headline flush left. Put your URL directly below. Put your summary next. By the time the recruiter has finished their F-pattern scan of your top section, they should know your level, your specialty, your top skills, and where to learn more. That is enough for them to decide you are worth a real read.
If your top section is cluttered with a mailing address, a photo, and an objective about what you hope to learn, the recruiter finishes their F-scan without learning anything useful. You just lost your window.
Putting It Together
Here is what the top of your resume should look like, in order:
- Your name in the largest font on the page
- A one-line headline with your role, domain, and top tools
- Your profile URL and email on the same line
- A two-sentence value summary describing what you bring
- Four or five top skills listed as simple text
That is it. Everything else goes below. Your experience, education, projects, and certifications all get their own sections further down. But the top is reserved for the information that makes you stand out in the first 6 seconds.
Read Next
Turn Your CV into a Website
Drop your CV below or build it from scratch.
Frequently Asked Questions
What should the top of my resume look like?
Your name in a large clear font, a one-line headline with your role and specialty, a link to your full profile, a two-sentence summary of your value, and your four or five strongest technical skills. That is it. Nothing else needs to be above the fold.
Should I put an objective statement on my resume?
No. Objective statements tell the recruiter what you want, not what you offer. A value summary that describes what you bring to the team is far more effective and takes up the same amount of space.
Should I include my full home address on my resume?
No. City and country are enough if location matters for the role. A full street address wastes space at the top of your resume and creates a privacy risk with no upside.
Further Reading
Best Portfolio Platforms for Developers
Seven real options for showing your work online, from free GitHub Pages to a fully custom domain. Here is what each one actually does well.
Best Resume Keywords for Tech Jobs
The right keywords get you past the filter. The wrong ones make you look like you copied a job posting. Here is what actually matters by role in 2026.
Best Ways to Send Your Resume to a Recruiter
You have five options for getting your resume in front of a recruiter, and most people default to the worst one.
Best Resume Mistakes to Fix Before Applying
Ten resume mistakes ranked by how much damage they actually do, starting with the one that gets you rejected in under three seconds.