How to Write a Resume With No Experience

When a hiring manager scans a resume from a sophomore or junior who has never held an office job, they are not looking for an empty page. They are asking: "What has this person done that proves they can handle work?"

Real evidence comes from many sources. Here is an inventory to work through—check the ones that apply to you:

• Course projects and labs. A semester-long assignment, a capstone, a design project with a final deliverable. The course title, what you built, and what you learned go on your resume exactly as if you had been hired to do it.
• Relevant coursework. In the absence of job history, naming the 4–6 most advanced courses in your major signals that you have the technical foundation for the role. List by course title, not code.
• Student clubs and organizations. Officer roles (treasurer, president, logistics lead) are work. So are founding a club, growing membership, running an event, or building a tool for the group. Quantify if you can: "Organized weekly meetings for 40+ members," "Raised $2,400 for annual trip."
• Volunteering and community service. Tutoring, mentoring, trail maintenance, food-bank shifts, animal shelter work—these are all legitimate experience. The verb and the impact matter: "Tutored 8 struggling students in algebra" beats "Helped with tutoring."
• Sports and recreation leadership. Captain of a team, organizer of a tournament, coach of younger athletes. Team achievements count: "Led defense to 8-game winning streak," "Recruited 30 new members to climbing club."
• Family business or caregiving. If you have worked in a family business—even informally—list it. Same for significant caregiving: babysitting multiple children on a recurring schedule, caring for a relative. Name the task and the scope.
• Freelance or gig work. Freelance writing, graphic design, tutoring for pay, reselling items, social-media management for a small business. These are jobs, even without a W-2.
• Self-taught projects and portfolios. A website you built, an app you released, a photography portfolio, a blog you maintained, open-source contributions. Include a link if it lives online.
• Competitions and hackathons. First-place finishes, selections to competitive programs, hackathon wins, debate tournament awards. Name the competition and your placement or role.
• Teaching and tutoring. Formal tutoring (paid or unpaid), teaching assistant roles, peer mentoring, guest lectures. Especially valuable if you can cite the number of students or the depth of responsibility.
• Campus jobs. Work-study, library circulation desk, dining services, student IT support—these count. They are employment with a pay stub and scheduled hours. Put them on your resume.
• High school leadership (with caveats). Valedictorian, debate captain, founder of a major initiative—but only if you are a first-semester college student. Drop it by sophomore year. The resume is a document of your most recent growth; a high-school award from two years ago takes space.

Pick the six to eight strongest items from this list. Those become the material for your resume.

A one-page resume is the working standard for undergraduates and first-year graduates. Many hiring managers and recruiters expect it. It is not a ceiling on how much you can say; it is a discipline on how efficiently you say it.

Why one page? A recruiter who spends five seconds on a resume is looking for a reason to move you forward or move to the next candidate. A well-organized, dense one-page resume is easier to scan. More importantly, a one-page constraint forces you to name the right things instead of padding with filler.

When you have very little work history, one page is your friend. Many students panic and think: "If I only have two experiences, I need to make them longer to fill the space." This is the wrong instinct. You do not fill a resume with long sentences. You fill it with meaningful work. If you have three solid projects and two club roles, that is a complete one-page resume. Stop.

Format and spacing:

• Margins: 0.5 to 0.75 inches on all sides. Narrower than that and the text looks cramped; wider and you are wasting space.
• Font size: Body text should be between 10 and 11 points. Names and section headers can be 11–12 points. Anything smaller than 10 is hard to read in print.
• Line spacing: 1 to 1.15 is standard. Tighter spacing saves space; looser spacing makes the page feel airier. Consistency matters more than the exact number.
• White space is not wasted space. A margin, a gap between sections, a line of breathing room after a company name—these are not luxuries. They make the resume readable. Respect the white space; do not fill every gap with text.

State only what you can source. If you are writing about a project, you should be able to show the code, the design file, or the end result. If you are claiming you "led" something, you led it—not just participated. Every word on your resume is an implicit claim that you can back it up in an interview.

The order of sections on your resume should signal what is most relevant to the job. When you have very little history, order becomes a storytelling tool.

Case A: You have no jobs at all

1. Name and contact information
2. Education (with relevant coursework, GPA if ≥ 3.5, expected graduation date)
3. Projects (if you have them; especially strong for technical roles)
4. Leadership & Activities (clubs, volunteering, initiatives you led)
5. Skills (languages, tools, certifications)

Case B: You have some unrelated jobs (retail, food service, etc.)

1. Name and contact information
2. Education
3. Relevant Experience (projects, coursework, labs, volunteer roles that align with the job you are applying for)
4. Additional Experience (retail, fast food, campus jobs that do not directly relate)
5. Skills

Why split experience into "Relevant" and "Additional"? This is the single highest-leverage move for a student applying to a role with only retail or food-service work on their resume. You are not hiding your job history. You are being honest about what each role teaches. A cash-register job does not qualify you for a marketing internship, but a semester-long social-media project for a class does. Show the hiring manager that you understand the difference, and you double the weight of your real work.

Do not create these sections if you do not need them. If all your experience is unrelated, keep it simple: one "Experience" section in reverse chronological order (most recent first).

Education is your anchoring section when you have no job titles yet. It tells the truth about where you are, what you are studying, and what you have learned.

Required fields:

• Degree and major. Bachelor of Science in Computer Science, Bachelor of Arts in Chemistry, etc. Write the full title.
• Institution name. The full, official name of your school.
• Expected graduation date. "May 2027" or "Expected May 2027." Do not write "2027" alone—hiring managers need the month.

Optional but recommended:

• Relevant coursework (4–6 courses). Choose your most advanced, most relevant courses to the job you are applying for. List them by title, not code. Instead of "CS 201, CS 251, MATH 110," write "Data Structures, Object-Oriented Design, Linear Algebra." Hiring managers can read it without looking up the catalog.
• Honors and academic achievements. Dean's List, departmental honors, scholarships—but only if you earned them. Do not write "4.0 GPA freshman year" if it is no longer true; it raises the question of why you are not maintaining it.
• GPA (with conditions). Include your GPA if it is 3.5 or higher. Some schools or industries have different thresholds; check if your field has a norm. If your major GPA is higher than your overall GPA, you can list the major GPA alone. Do not include a weak GPA; it is better to leave it off.

What to drop: Your high school, your intended major (if you are still undecided and have not declared), your high school graduation year, or the name of your residence hall. These do not belong on a college resume.

A semester-long class project, a capstone, a group design challenge, or a hackathon build can occupy a full line item on your resume. You are not applying for a job as a student; you are describing work you have completed that required the same skills.

Structure:

• Title: Give the project a real name. Not "Class Project" but "E-Commerce Product Recommender" or "Interactive SVG Data Visualizer" or "Mobile App for Campus Event Booking."
• One-line description: What is it, and why did you build it? "Designed and built a web application to help residents of on-campus housing discover and register for campus events" is concrete. Avoid "Worked on a project to improve user experience."
• 2–3 bullet points: What did you do, how did you do it, and what was the outcome? Did you design the UI, write the backend, lead the team, manage scope? Did you use Python, React, PostgreSQL? Did 200 students use it, or is it a portfolio piece? Details matter.
• Tools and languages: List the technologies: "React, Node.js, PostgreSQL" or "Python, Pandas, Matplotlib." This is where a recruiter looks to see if you have the skills the job requires.
• Link (if applicable): If the project lives on GitHub, is deployed on a website, or has a demo video, include the link. A real, clickable deliverable is far more convincing than a description alone.

Two worked examples:

A bullet point from a class project, a volunteer role, or a club leadership position should follow the same pattern: action verb + what you did + how you did it + result.

This pattern is the foundation of professional writing. For full guidance on this skill, see our Bullet Point Builder.

Eight worked pairs: weak → stronger

What belongs on your Skills section:

• Programming languages: Python, JavaScript, Java, C++, SQL, R, Go, Rust, etc.
• Frameworks and libraries: React, Django, Flask, Vue, TensorFlow, NumPy, etc.
• Tools and software: Git, Docker, Figma, Adobe Creative Suite, AutoCAD, Tableau, Excel (if you use it professionally, not casually), Jira, etc.
• Platforms and services: AWS, Google Cloud, Azure, Firebase, Vercel, etc.
• Certifications and credentials: CompTIA A+, AWS Certified Solutions Architect, Google Analytics Certification, etc. List the full name and year earned.
• Spoken languages: List the language and your proficiency level honestly. "Spanish (Fluent)," "Mandarin (Elementary)," "Italian (Working Proficiency)." Do not overstate.

Proficiency-wording ladder (in order of depth): Elementary · Conversational · Working Proficiency · Professional Proficiency · Fluent · Native

What does NOT belong:

• "Microsoft Word," "Email," "Internet." These are baseline; every professional is assumed to have them. Listing them makes you look inexperienced.
• "Hard-working," "Team player," "Organized," "Communication skills." These are not skills; they are adjectives. Show these traits through your bullet points, not by claiming them.
• "Proficient in Microsoft Office." If you use Excel for data analysis or PowerPoint for presentations at a professional level, you might list "Excel" or "Advanced Excel." Otherwise, drop it.
• High school certifications (CPR, lifeguard training) if you no longer hold them. If you still hold the cert, you can include it.
• Unrelated hobbies. "Photography," "cooking," "video games" do not belong in the Skills section. If a hobby is relevant—you are a graphic designer and you do photography—it belongs in a portfolio link, not here.

How to format the Skills section: A simple, scannable list, often grouped by category.

Every line on your resume competes for space. Here is what to cut:

• Photo: Unless the industry standard calls for it (modeling, acting, professional headshot industries), do not include a photo. A resume is not a social-media profile. Hiring managers care about your skills.
• Full home address: Include your city and state, or your state alone. "Boston, MA" or "MA" is enough. Do not write your street address; it is a privacy risk and takes up space.
• High school after sophomore year of college: Your high school credentials become irrelevant once you have completed two years of university work. If you graduated high school at 16 (an unusual achievement worth explaining), mention it in your cover letter, not your resume.
• Objective statement: "Seeking a summer internship in software engineering to develop my skills and contribute to a team environment." This tells the hiring manager nothing they cannot infer from the fact that you applied. Delete it. Your resume is your objective.
• "References available upon request": Everyone knows you have references. Do not waste a line on this. If the employer wants references, they will ask. You provide them at that time.
• Unrelated hobbies with no narrative: "Reading," "hiking," "movies"—these belong in your personal life, not on a resume. If a hobby demonstrates a skill or an achievement—"Founded university running club," "Won 3 regional debate championships"—then it is experience and belongs on your resume.
• Birthdate, marital status, or age: Never include these. They are not relevant to your ability to work, and including them can expose you to bias.
• Reasons you left a job or personal life context: Your resume is not a biography. Save explanations—why you left a part-time job, why you took time off, family circumstances—for the cover letter or the interview. The resume is facts and dates only.

Use this checklist to write your first draft right now. You do not need perfect wording; you need to get the structure and facts down. Editing comes after.

1. Open a blank document. Set margins to 0.5–0.75 inches, font to 10–11 pt, line spacing to 1.0–1.15.
2. At the top, write: Your Full Name (slightly larger or bold). Below it, one line: City/State, phone, email address (no "Email:" label).
3. Create a section labeled "EDUCATION." Write your degree, institution, expected graduation month/year. Add 4–6 relevant course titles (separated by commas or bullet points). If GPA ≥ 3.5, add it. If you have honors or scholarships, add one line for each.
4. List every substantial project, class work, volunteer role, club position, campus job, internship, or paid job you have done. For each, write: (a) a title, (b) one sentence describing what it is, (c) 2–3 bullet points listing what you did.
5. Go through each bullet point. Rewrite it in the form: [Action Verb] [Object] [How/Method] [Result]. Example: "Designed and deployed a web app using React and Firebase that helped 200+ students track group expenses."
6. Group your items into sections. Most common: EDUCATION → PROJECTS (if applicable) → EXPERIENCE or RELEVANT EXPERIENCE / ADDITIONAL EXPERIENCE → SKILLS.
7. Trim down to one page. Cut anything that does not add value. If you have 20 bullet points, cut the weakest 5. Fewer, stronger bullets beat a dense wall of text.
8. Read aloud. If a sentence feels vague or too wordy, rewrite it tighter.
9. Check for parallelism: all your bullet points should start with a strong verb. "Designed," "Managed," "Led," "Tutored." Not "Was responsible for" or "Helped with."
10. Print it out. Look at it. Does it look like a resume, or like a diary? If it has too much text, it is a diary. Reduce.
11. Set it aside. Do not look at it for an hour. Then read it with fresh eyes. Would you interview this person based on this resume? If yes, you are done.

Below is a complete, realistic resume for a second-year college student with no traditional job experience. Each section is annotated to explain what it is doing and why.

Related Tools