"No experience" almost never means no material

Students and new graduates tend to open a blank resume and freeze, convinced they have nothing to put on it because the "Work Experience" section stays empty. That's a labeling problem, not a content problem. A resume isn't a record of paid full-time jobs — it's a record of what you've done that's relevant to what you're applying for. Coursework projects, part-time and retail jobs, volunteer work, and student organizations all count, provided you describe them the way you'd describe any other resume item: what you did, at what scope, with what outcome.

The mistake to avoid is the opposite one: padding the resume with vague filler ("hardworking student eager to learn") to disguise a thin work history. That reads as weaker than a short, honest resume built from real material, even if that material didn't come from a full-time job.

What actually belongs on a first resume

Structure it around whichever of these sections you have real content for — you don't need all of them:

  • Education, moved up near the top (this is the one exception to the usual "experience first" rule — with limited work history, your degree, relevant coursework, and GPA if it's strong are doing real work for you).
  • Projects, especially class projects, capstones, or personal projects with a concrete deliverable. Treat each one like a job: what the project was, what you specifically did, what tools or methods you used, and what the result was.
  • Part-time, retail, or service jobs, even if they're unrelated to your target field. A retail job genuinely demonstrates reliability, customer interaction, and handling responsibility under pressure — describe it with the same specificity you'd use for any other role, not a throwaway line.
  • Volunteer work and student organizations, if you held any real responsibility (organizing an event, managing a budget, leading a small team) rather than just attending.
  • Skills, listed honestly at the level you actually have them — a tool you used once in a class project is "familiar with," not "proficient in."

Turn a class project into a resume bullet

Before: "Completed a group project for Database Systems class."

After: "Designed and built a relational database for a 4-person capstone project, modeling a library checkout system with 6 linked tables; presented the final schema and query set to faculty reviewers."

The "after" version names the scope (4-person, 6 tables), your specific role (designed and built), and a concrete outcome (presented to reviewers) — the same formula used for any resume bullet, just applied to a project instead of a job.

Don't fabricate what isn't there

It's tempting to invent a title, inflate a responsibility, or claim proficiency in a tool you've only briefly touched — resist all three. A thin but honest resume survives a follow-up interview question; a padded one doesn't, and the gap between a claimed skill and a demonstrated one shows up fast once someone asks a real question about it. If a section would genuinely be empty, leave it off the resume entirely rather than filling it with something invented.

If you're not sure how to phrase a skill you've only used briefly, browsing Craftume's Skills Library by category can help you find accurate, honest language for something you're still building toward, rather than either overstating it or leaving it out entirely.

FAQ

Should I include a summary at the top if I have no experience to summarize? A short summary can still work if it focuses on your field of study, a relevant project or two, and what you're specifically looking to do next — skip it entirely if it would just restate your degree with no other information.

Is it okay to list high school achievements once I'm in college? Generally no, once you have any college-level coursework or projects to replace it with — the one common exception is a genuinely notable, relevant achievement (a competitive scholarship, a state-level award) that still says something current about you.

How long should a first resume be? One page, almost without exception. A thin one-page resume reads as appropriately early-career; a stretched two-page resume built from limited material reads as padded regardless of formatting.

Should I list every part-time job I've ever had? Only the ones from the last few years that either show relevant skills or fill in a timeline gap — a single unrelated summer job from years ago usually isn't worth the space once you have more current material.

What if my degree is unrelated to the job I'm applying for? Lead with the transferable skills and projects instead of the degree title itself — problem-solving, research methods, and collaborative project work translate across fields even when the specific subject matter doesn't.