New Grad Resume With No Experience: What to Put Instead

For a new grad resume with no professional experience, start with education, relevant projects, skills, and any volunteer, campus, or part-time work you can describe honestly. Use clear sections and specific contributions, usually on one page. Do not create an empty work-history section or present coursework as employment.

Academic and Personal Projects That Show Relevant Work

A project can be a research report, a communication campaign, a design prototype, a financial model, or software. Choose work that helps a reader understand a capability the role needs. It does not have to be a commercial product.

Name the context, your contribution, the methods or tools used, and what you produced. If it was a group assignment, explain your part. Share a sample only when you have permission and it contains no private data.

Illustrative rewrite: "Completed a group marketing assignment" becomes "Reviewed student survey responses and drafted audience recommendations for a class campaign proposal." The second version describes work without claiming a real campaign launch or business result.

See how to write resume bullets that show impact for the underlying writing method.

For technical roles specifically, see the entry-level software engineer resume guide for what makes a strong projects section in a technical context.

Internships and Part-Time Work

Brief or part-time experience can belong even if it is not in your target field. Describe what you actually contributed. Observing a process is not the same as building it; do not turn "shadowed colleagues" into an invented project.

For part-time or non-technical work, include it briefly. It demonstrates professional reliability and real work experience, even if the role itself is not related to your career direction.

Coursework: Use Selectively

Listing every course you took is not useful. Selected coursework can be worth including when it is directly relevant to a role requirement that your projects and experience do not already cover. If the work is already demonstrated by your projects, the course entry adds nothing.

Label coursework as coursework. A relevant assessed assignment can demonstrate a skill, but a course title alone does not prove professional experience or a separate certification.

Other Material Worth Including

Research. If you conducted research as an undergraduate or graduate student, include it. Research demonstrates analytical thinking, independent work, and often domain-specific knowledge.

Leadership roles in organizations. President, team lead, event organizer — roles that involved real ownership and decision-making are worth including briefly. Specific and credible beats generic.

Freelance or contract work. Any paid professional work done independently belongs on the resume. Be accurate about the context.

Relevant skills. Include methods, tools, and language skills you can demonstrate, whether that is editing, spreadsheet analysis, research, or software development. See what skills to put on your resume for examples across roles.

A New Graduate Resume Example Outside Software Engineering

This fictional outline is for a communications graduate seeking coordinator work. It illustrates section order and level of detail; replace every claim with your own facts.

For a research role, move the research evidence higher. For an administrative role, emphasize scheduling, records, and coordination you have actually done. The transferable-skills guide helps connect those contributions without inventing a new job title.

Build a First Draft From What You Already Have

1. Choose one type of entry-level role and identify the work it asks for.
2. List relevant assignments, projects, responsibilities, and work, including unpaid contributions.
3. Select the strongest examples and state what you personally did.
4. Use clear labels such as Education, Projects, Volunteer Experience, and Skills.
5. Draft in the free EndLuck resume builder and check the exported page length and readability.

If there is genuinely little relevant material, a small completed project can add evidence. Describe it only after doing the work. You do not need a fabricated internship, a long hobbies list, or an apology for being early in your career.

What Not to Do

• Do not inflate academic projects. "Developed a production-grade system" when describing a class project is inaccurate. "Built a full-stack application as part of a capstone project" is accurate and still compelling.
• Do not list every class. Selective and relevant, not a transcript.
• Do not claim skills you cannot demonstrate. The interview will expose any skill that is paper-only.
• Do not apologize for limited experience. Present what you have with confidence. Hiring managers reviewing new grad applications expect and understand the context.