First Resume With No Experience: Grad Playbook

11 min read

You're staring at a blank document and the job posting wants three years of experience you don't have. I've screened stacks of new-grad files, and the ones that move aren't empty—they're just selective. Your first resume with no experience still has proof: capstones, campus jobs, clubs, internships, and coursework you haven't translated yet.

This playbook shows you how to inventory that evidence, pick one entry-level target, write bullets a recruiter can follow up on, and format the file so Workday or Greenhouse can read it. Before you spend an hour on margins, check your resume for free once you have a draft—parsing problems kill qualified grads more often than weak GPAs.

You won't need a fake job title or invented metrics. You'll need honest labels, a one-page structure, and language that matches what the posting actually asks for.

What a first resume with no experience actually is

A first resume isn't a biography and it isn't a transcript. It's a one-page argument that you can do entry-level work in a specific lane—operations, marketing, nursing, software, customer support, whatever you're actually targeting.

Evidence beats titles. A dining-hall shift with cash controls and customer complaints handled can outrank a vague "marketing intern" line that says nothing about what you produced.

What it is not: a list of every class you took, a paragraph about being a fast learner, or a design portfolio squeezed into a two-column Canva template. Recruiters give a new grad resume a few seconds on the first pass. They're looking for recognizable headings, a clear target, and at least two examples they could ask about in an interview.

This is not a LinkedIn profile. You don't need a photo, street address, or objective statement that says you want to grow. You need contact info, education, skills you can defend, and two or three proof sections—projects, experience, leadership— ordered by relevance to one role family.

Step-by-step: build your first resume from zero

Step 1: Inventory every piece of evidence

Open a separate document—not the resume yet. List paid jobs, internships, labs, capstones, class teams, clubs, athletics, volunteering, caregiving, freelance tasks, and personal builds. For each one, jot the problem, your actions, tools, team size if relevant, and the final deliverable.

Do this now: set a ten-minute timer and don't filter. A resident assistant role belongs on the list. So does the website you built for a cousin's business. You'll cut later; right now you're proving the page won't stay blank.

Step 2: Pick one entry-level role family

Your first resume shouldn't target "anything." Save three postings for the same role type—say, data analyst, HR coordinator, or clinical research assistant. Highlight recurring hard skills, tools, and deliverables. That list becomes your filter for what earns space on page one.

A lab assistant version and a marketing coordinator version can draw from the same history, but they'll lead with different projects. That's normal. One master inventory, multiple tailored one-pagers.

Step 3: Structure the page so parsers and humans agree

Use contact information, a short summary or headline, education, skills, then projects and experience in whatever order puts your strongest proof higher. Standard labels only: Education, Skills, Projects, Experience, Leadership or Activities.

Contact line: name, city and state, phone, professional email, optional LinkedIn or portfolio. No icons as the only labels. Education: institution, degree, field, graduation month and year. Skills: plain tool names—Excel, Python, Figma—not star ratings.

For ATS extraction details, see the Workday resume format guide and the broader ATS resume guide for students .

Step 4: Turn projects into interview-ready bullets

A project entry needs a name, context label, date, tools, and two or three bullets. Label academic work honestly—"Academic Project" or "Capstone"—not "Consulting Experience."

Composite example — data analyst target:

Before: "Completed a group marketing project."
After: "Interviewed 12 student users, synthesized recurring needs, and co-developed a launch brief with audience segments, channel recommendations, and a presentation to the course panel."

Composite example — software target:

Before: "Used Python in class."
After: "Cleaned and joined three public datasets in Python, documented missing-value decisions, and built a reproducible notebook comparing neighborhood transit access."

Read each bullet aloud. If an interviewer can't ask "what was the dataset?" or "what did you own?" you're not done. More rewrite patterns live in our outcome-based bullet guide .

Step 5: Write a summary that sets direction, not desperation

A summary is optional for some grads, but it helps when your degree alone doesn't explain the target. Keep it to three or four lines. Name the role area, strongest applied evidence, tools, and context.

Don't write "hardworking graduate seeking an opportunity to grow." Don't claim five years of experience by adding up semesters. Describe actual settings: a two-semester lab, a summer internship, weekly front-desk shifts.

If you're applying through a campus career portal, the summary is often the first text a recruiter reads after the degree line. Make it specific enough that they know which pile to put you in.

Step 6: Mine campus jobs for professional behavior

Campus work counts. Employers hire for reliability and customer-facing behavior, not only domain knowledge. A library assistant manages records and patron questions. A tutor diagnoses gaps and adapts explanations. A cashier runs transactions under controls.

Before: "Helped students at the front desk."
After: "Answered student service questions across phone, email, and walk-in channels; routed financial-aid and registration cases to the correct offices; maintained accurate appointment notes."

Use the official title. Don't upgrade "committee member" to "director." Say what you owned inside the role.

Step 7: Add skills as an index, not a wish list

Skills should be tools, languages, methods, and technical knowledge you can demonstrate in a bullet below. Separate categories when it helps scanning: Data: Excel, SQL, Tableau; Design: Figma, Adobe Illustrator; Languages: Spanish (professional working proficiency).

No five-star ratings. No skill bars. If a posting asks for Tableau and your capstone used it, Tableau belongs in Skills and in the project bullet. If you only watched a demo, leave it off.

Composite example — nursing or clinical target:

Before: "Clinical rotation experience."
After: "Completed 120-hour med-surg rotation; documented vitals, intake notes, and patient education under RN supervision; maintained HIPAA-compliant handling of patient identifiers in all written work."

Edge case: career change before your first "real" job

Some grads pivot fields before landing. If your degree doesn't match the target, lead with projects and certifications that bridge the gap. A psychology grad targeting UX can lead with a portfolio project and user-research coursework, not unrelated retail unless the retail bullet shows transferable service skills.

Edge case: overlapping dates from school and work

Part-time campus jobs during school often overlap with project dates. That's fine. Use month-year on each entry and don't hide overlap—it's expected. Problems start when dates are missing or when two full-time jobs claim the same months without explanation.

Edge case: NDA or private client work

Internships under NDA still belong on the resume. Use the employer name if allowed; if not, "Confidential technology startup" or "Fortune 500 financial services client via agency" is acceptable when accurate. Describe the function, stack, and outcome without naming unreleased products or private metrics you can't share.

Step 8: Format for Workday and Greenhouse

Single column. Readable type. Ordinary bullets. Month-year dates inline with titles. No text in headers, footers, or text boxes. Export a text-selectable PDF unless the employer asks for DOCX.

Copy-paste test: select all text and paste into Notepad. Your name should appear first, sections in order, dates still attached to job and project names. If the order scrambles, simplify the layout before you apply.

Match posting terms when they describe your real work. If the listing asks for pivot tables and you used them in a finance project, name pivot tables in that bullet. If it asks for Salesforce and you've never touched it, don't stuff it into Skills.

Step 9: Run a final quality check

Proofread names, dates, degree status, links, and tool claims. Ask a classmate which target role your resume seems to seek—if they name three unrelated jobs, your positioning is too broad. Ask which two examples feel strongest; move those higher and cut weaker repetition.

Compare line by line with the posting. Mark each must-have as proven, adjacent, or absent. Proven means a real example on the page. Adjacent means you can explain honestly in an interview. Absent means absent—don't keyword-stuff your way past a gap you can't defend.

Save the exact file name you upload. If you get an interview, you'll need to remember what version they have.

Copy-paste summary line

Recent economics graduate targeting operations analysis roles, with capstone experience cleaning public datasets in Python and campus-office experience resolving service cases across email, phone, and walk-in channels.

Swap in your field, tools, and strongest proof. Three or four lines max. No "hardworking team player seeking opportunity to grow."

Common mistakes on a first resume with no experience

Listing every course. Relevant coursework belongs as one line under Education or as a project entry—not a transcript dump. Introductory classes whose names merely repeat your degree waste space.

Decorating before selecting. Picking a fancy template before you know what evidence you're leading with is how you end up with a pretty file and no interview stories. Content first, margins second.

Invented metrics. "Increased efficiency by 40%" on a class project you can't explain will collapse in the first interview question. A named deliverable beats a fake percentage.

One resume for every industry. Spraying the same PDF to nursing, sales, and software openings reads unfocused. Build one tailored version per role family; it takes twenty minutes once the inventory exists.

Ignoring GPA rules. Include GPA when it helps and the scale is stated. Drop it when it doesn't add value and the application doesn't require it. Never round up or swap in major GPA without labeling it—that's an easy background-check tripwire.

Weak portfolio links. If you list a portfolio, open it in a private browser window before you apply. Broken links, password walls, and class assignments with private student data make you look careless—not junior.

Use HireFlow before you hit submit

Upload your draft to the free ATS resume checker and look at three things: parsing (did your jobs and dates extract?), keyword gaps against a saved posting, and formatting flags like columns or unreadable headers.

Fix parsing before you tweak wording. A qualified grad with scrambled Workday fields looks like a weaker candidate than the same person with a boring single-column file.

Then run the job match score against the posting you saved. You're not chasing 100%—you're checking whether must-have skills show up in real bullets, not only in a Skills list. If a required tool only appears in Skills with no project or job proof, add a bullet or remove the claim entirely.

Your first resume with no experience, tightened

• Inventory first, one-page selection second—your evidence is probably scattered, not absent.
• Label projects and campus jobs honestly; bullets should survive one follow-up question each.
• Single column and clean dates so ATS and recruiters see the same story.

Open your draft, pick the weakest bullet, and rewrite it with an action, a tool, and a deliverable you could explain in thirty seconds. Then check your resume for free . Stop guessing whether the bots can read it.

Read more

• How to build a resume from scratch — step-by-step for any starting point.
• ATS-friendly resume template for 2026 — layout rules that survive parsing.