Entry-level resume examples that get interviews

What goes in the header, and what gets you screened out?

Your header is a few short lines: name, phone, a professional email, and the links that show your work. That is it. No mailing address, no headshot, no fancy graphics.

Use an email like firstname.lastname@gmail.com. A leftover handle like skaterboi2003@gmail.com reads as careless before a recruiter has seen a single bullet. If your LinkedIn is bare, spend 20 minutes filling it in before you link it, because they will click.

If you have a GitHub, a Behance, or a personal site with real work on it, put the link here. A live link beats any adjective you could write about yourself.

• Name, slightly larger than body text
• Phone number you actually answer
• Clean email: first.last@gmail.com
• LinkedIn URL, customized (linkedin.com/in/yourname)
• Portfolio or GitHub link if the work is real

Here is the whole page we are about to build, section by section. Every line below comes from the examples in this post.

Do you need a summary or objective at the top?

Skip the objective. Lines like "Seeking a challenging role to grow my skills" tell a recruiter nothing and waste your most valuable space.

If you cannot make the summary concrete, leave it out and let your projects and experience carry the page. For most students, more room for real work beats a paragraph about being hardworking.

A short summary can work, but only if it is specific. Here is the difference:

How do you write the education section as a new grad?

As a student or recent grad, education goes near the top, right under your header. This is the section employers expect to anchor your resume early in your career.

List your school, degree and major, graduation month and year, and GPA if it is 3.3 or higher. Add relevant coursework only when it maps to the job, and use the real class topics, not the course codes.

Include honors, scholarships, or a leadership role in a club if you have them. A line like "Treasurer, Finance Club: managed a $4,000 annual budget" is a real accomplishment, so treat it like one.

• B.S. Computer Science, State University, May 2026
• GPA: 3.6 (list it if 3.3+)
• Relevant coursework: Data Structures, Databases, Machine Learning
• Honors: Dean's List, 4 semesters

What if you have no real work experience yet?

You have more than you think. Class projects, hackathons, freelance gigs, volunteer work, and part-time jobs all count. The trick is to write about them the way you would write about a job.

Make a Projects section and treat each project like a role. Name it, say what you built, name the tools, and show the outcome.

Do not throw away the part-time job either. "Trained 5 new baristas and cut average order time by 20 seconds during the morning rush" shows ownership and numbers, which is exactly what a hiring manager is scanning for.

• Class and capstone projects, written like roles
• Hackathon builds and side projects on GitHub
• Volunteer work and student org leadership
• Part-time and campus jobs, framed by impact

What does a bullet that gets a callback look like?

Every bullet starts with a verb, names a tool or method, and ends with a result. Verb plus tool plus number. That pattern is what separates a resume that gets read from one that gets skimmed and dropped.

Most first drafts sound like the before lines below: honest, first person, a little rambly, and quiet about results. Nothing in them is wrong. They just hide the good part. The fix is not fancier words, it is cutting the wind-up and leading with what happened.

If you genuinely cannot find a number, lead with scope or outcome instead: how many people, how often, what changed. A clear result without a number still beats a vague duty with one.

How should you list skills without padding the section?

List tools and technologies, not personality traits. "Communication," "teamwork," and "problem-solving" mean nothing on their own, and recruiters tune them out. Prove those in your bullets instead.

Group your skills so they are easy to scan. For a technical role: Languages: Python, Java, JavaScript. Frameworks: React, Node, Flask. Tools: Git, Docker, PostgreSQL. For a non-technical role, list the real software you know: Excel, Salesforce, Figma, Google Analytics.

Only list a skill you could defend in an interview. If "Java" is on your resume, expect a Java question. Padding the list with tools you touched once is the fastest way to lose trust in the room.