Entry-Level Resume
Writing an entry-level resume isn't about hiding limited work history — it's about knowing what to include instead. Every reviewer knows you're entry-level. They're looking for evidence of what you can do, not 10 years of it.
You can't write a strong resume without work experience
Entry-level resume reviewers know you don't have 10 years of work history — they're looking for evidence that you can learn, work with others, and contribute to a team. The evidence can come from internships, academic projects, clubs, freelance work, volunteer roles, part-time jobs (even unrelated ones), or coursework. The question is not whether you have experience — it's whether you're showing what you have effectively.
Every resume section — what to include and what to avoid
Explained specifically for entry-level candidates, with ATS guidance for each section.
Contact Information
Include
Full name, professional email address, city and state (no street address), LinkedIn URL (if your profile is complete), portfolio or GitHub (for technical or creative roles).
Avoid
Photos, date of birth, GPA below 3.0 (if it's relevant to mention GPA at all — some employers expect it, most don't), objective statements ('Seeking a position where I can grow...') — replace with a professional summary.
ATS note: ATS systems parse the contact block for email and phone. Use a simple header layout — tables and text boxes often cause parsing errors.
Professional Summary (2–3 sentences)
Include
Your most relevant skill, what type of role you're targeting, and one specific accomplishment or trait — even from academic or part-time experience. This is your 15-second pitch, not a repetition of your education section.
Avoid
'Hardworking, motivated team player looking for an opportunity to grow.' This tells the reader nothing. Every candidate claims this. Instead: 'Computer Science graduate with experience building full-stack web applications in React and Node.js — most recently a capstone project serving 200+ beta users. Looking for a backend engineering role where I can contribute from day one.'
ATS note: The professional summary is one of the most important places to include job-description keywords. Read the JD and mirror the language used to describe the ideal candidate.
Education
Include
Degree, major, institution, graduation date (or expected graduation date). Relevant coursework (for technical roles or when the course directly matches the job), academic honors, and GPA if 3.5 or above.
Avoid
Listing every course you took. List 4–6 that are directly relevant to the target role, labeled as 'Relevant Coursework' — not all 32 courses from your transcript.
ATS note: Education section placement: for entry-level, put it near the top (after the summary). After 2+ years of work experience, move education below your experience section.
Experience
Include
Internships first, then part-time jobs with transferable skills, then significant campus roles (RA, student org president, teaching assistant). For each: company, title, dates, location, and 2–4 bullet points describing what you did and — when possible — a result.
Avoid
Listing only job duties without any indication of scope, volume, or outcome. 'Helped customers' tells the reader nothing. 'Handled 80+ customer transactions per shift as cashier, maintaining 98% accuracy over 14-month tenure' tells them something.
ATS note: For roles that seem unrelated (retail, food service), identify the transferable skill the JD is asking for — communication, reliability, teamwork, handling volume under pressure — and write the bullet toward that skill.
Projects
Include
Academic capstone projects, personal projects, hackathon work, freelance projects, or open-source contributions — especially for technical, creative, or analytical roles. Include: project name, brief description (1 sentence), technologies/tools used, and a metric or outcome if available.
Avoid
Listing school assignments that weren't substantial. A semester project where you wrote a 10-page paper is not a project to list. A project where you built something, analyzed something, or produced something concrete is.
ATS note: Project titles and technology stacks are keyword-searchable. Name the specific tools used: 'React, Node.js, PostgreSQL' rather than 'full-stack technologies.'
Skills
Include
Technical skills (software, programming languages, tools), certifications, and languages. List skills you would be comfortable being asked about in a technical screen — don't inflate.
Avoid
Soft skills in the skills section ('Communication, Teamwork, Problem-Solving') — these belong in your experience bullets as demonstrated behaviors, not as standalone claims. ATS doesn't typically weight soft skills in this section, and human reviewers find them uninformative.
ATS note: The skills section is directly parsed by ATS for keyword matching. Organize by category: 'Languages: Python, JavaScript | Frameworks: React, Django | Tools: Figma, SQL, Tableau.' Named skills are more ATS-readable than paragraph format.
Before & after: bullet rewrites for entry-level sources
Internships, academic projects, and unrelated part-time jobs all have strong bullets in them — if you know what to draw out.
Source: Internship
Before
“Assisted marketing team with social media content creation”
After
“Wrote and scheduled 45 LinkedIn and Instagram posts over 10-week internship for B2B software company (12,000 followers); posts averaged 3.2% engagement rate vs. 1.8% company baseline — 3 posts exceeded 500 impressions organically”
Key change: Quantity (45 posts), timeline (10 weeks), company context, and a specific performance benchmark replace 'assisted with.'
Source: Academic Project
Before
“Built a web application for my senior capstone project”
After
“Built full-stack inventory management app (React/Node.js/PostgreSQL) for 10-person capstone team — deployed to 200+ beta users across 3 local businesses; reduced manual inventory tracking time by estimated 4 hours/week per business based on user feedback survey”
Key change: Stack named, team size, deployment scale, user count, and a business impact estimate from user feedback replace the vague description.
Source: Part-Time Job (Unrelated Field)
Before
“Worked as a barista at Starbucks during college”
After
“Served 150+ customers daily as barista during peak shifts; trained 3 new team members on POS system and drink preparation within first 4 months; maintained consistently positive customer feedback ratings throughout 18-month tenure”
Key change: Volume (150+ daily), a training/mentoring signal, timeline, and a quality signal replace a job title with no evidence.
Common questions
Should I put my GPA on my resume?
Include it if it's 3.5 or above. For roles in finance, consulting, or law that explicitly require or filter by GPA, include it even if it's 3.3+. Omit it if it's below 3.0 — omission is expected and won't be questioned. If you have a strong major GPA but weaker overall GPA (e.g., major GPA 3.7, cumulative 3.2), you can list 'Major GPA: 3.7' — which is accurate and highlights the relevant performance. After 1–2 years of work experience, GPA becomes less relevant and can be removed regardless of the number.
How long should an entry-level resume be?
One page — in almost all cases. The rule of thumb is one page per decade of relevant experience, and for entry-level candidates, one page is both appropriate and expected. A two-page resume with limited substance reads as someone who doesn't understand what's worth including. The constraint of one page forces useful editing: it pushes you to keep only the most relevant sections and the strongest bullets.
What should I put on a resume when I have absolutely no experience?
Build the sections that don't require work experience: (1) Education with relevant coursework; (2) Projects — even a personal or academic project demonstrates initiative and skills; (3) Extracurricular and campus activities — leadership roles in clubs, student government, or organizations; (4) Volunteer experience; (5) Skills — list tools, software, and languages you've genuinely used. If you have none of these, the best move before applying is to create a portfolio project: build something, analyze something, or contribute to open source. A personal project completed in 2–4 weeks is worth more on an entry-level resume than a blank experience section.
Optimize your entry-level resume for the specific role you're applying to.
Zari analyzes your resume against the job description — identifies which sections need strengthening, rewrites weak bullets, and coaches you through the interview. Start free, no card required.
Try Zari free