How to Write a Resume with No Work Experience

A resume with no work experience faces one specific suspicion from the hiring manager: that the candidate can't yet do the job. The job of the resume is to flip that suspicion fast. The way you do it is by leading with the evidence that does exist (degree, projects, certifications, internships, volunteer work, leadership) and presenting it the way a working professional would (concrete, quantified, specific) rather than the way a student would (vague, comprehensive, padded).

The second move is to acknowledge the gap without apologizing for it. Hiring managers screening entry-level pipelines know they're looking at candidates with limited work history. They are not penalizing you for the gap; they are penalizing you for not handling it well. A resume that opens with "Seeking an entry-level position to apply my skills..." reads as if the writer doesn't know how to start. A resume that opens with a 3-line professional summary naming what you do bring reads as ready.

The third move is to show range without padding. One substantive project, one substantial leadership role, one quantified part-time job, and one relevant certification together prove more than a long list of school memberships and workshops. Pick the strongest 4-6 signals and structure the resume around them.

What doesn't move the screen: comprehensive lists. Every class taken, every workshop attended, every membership held. Hiring managers want the 4-6 strongest signals, not the full record.

Contact + LinkedIn. Name, professional email (not a college nickname), phone, city, LinkedIn. Add a portfolio or GitHub link if you have substantive projects.

Professional Summary (3-4 lines). What you bring, framed in adult professional language. "Recent BS Computer Science graduate; built and shipped a sentiment-analysis pipeline serving 200k tweets through a Flask API on AWS; comfortable in Python, SQL, and modern ML tooling; targeting entry-level data engineering and ML roles" beats every objective statement.

Education. Degree, school, graduation date, GPA if 3.5+, honors, relevant coursework, capstone or thesis topic. The most important section when work history is thin.

Projects (the most important section). Two to four substantive projects. For each: name (linked to demo or repo), one-sentence description, the stack or method, and one quantified outcome or scale signal. One real project beats two vague ones. For non-technical fields: substantive coursework deliverables, freelance or volunteer work, organizing roles in clubs or events.

Experience (any kind). Paid work counts even if not in the field: retail, food service, tutoring, on-campus jobs, summer camps. Lead each role with a quantified bullet that signals reliability and ownership. Volunteer and unpaid work count if substantive.

Leadership / Activities. Substantive roles in clubs, sports, research groups, volunteer organizations. "Treasurer of campus chess club ($14k budget, 180 members)" is signal; "Member" of three clubs is not.

Skills. Group by category. List 4-8 per category. Only what you can defend in an interview.

Certifications. Industry-relevant entry-level certs (Google Data Analytics, AWS Cloud Practitioner, BLS for healthcare, MS Office Specialist).

What to leave off. Photos, irrelevant high school activities (unless freshman/sophomore in college), generic objective statements, every workshop attended, hobbies that aren't a signal.