How to Write a Resume for Your First Job (No Experience)

You are writing your first resume. You stare at the blank page. The job description wants "3 to 5 years of experience." You have a degree and three college projects.

You feel stuck. You feel like a fraud just listing yourself as a "Software Engineer" or "Marketing Analyst." You wonder if anyone will take your resume seriously.

Good news: people land their first jobs every day with zero traditional experience. The resume is the first hurdle, and there is a specific way to write one that gets callbacks.

Here is the exact format that works for first-time job seekers in the US in 2026.

What Your Resume Is Actually Trying to Do#

Your resume has one job: get you a phone screen. It is not your life story. It is not a comprehensive list of everything you have ever done.

Recruiters spend 6 to 10 seconds on a first pass. Their question: "Does this person seem like they could do this job?"

You need to answer that question fast. Everything on your resume should help answer "yes."

The One-Page Rule#

For your first job, one page. Period. Two-page resumes from someone with no experience signal you do not know how to prioritize.

If you cannot fit everything on one page, cut. The cut version is better than the long version.

The Structure#

In this exact order:

1. Header (name, contact, links)
2. Education
3. Relevant Projects
4. Internships / Work Experience (if any)
5. Skills
6. Awards / Activities (if relevant)

Skip: objective statement, references available upon request, photo, declarations, hobbies (unless directly relevant to the role).

Section 1: Header#

Three lines. Keep it minimal.

Jane Smith
Boston, MA | (617) 555-0123 | [email protected]
linkedin.com/in/janesmith | github.com/janesmith | janesmith.dev

Notes:

• City and state (no full address, no zip code)
• Real phone number with area code
• Professional email ([email protected], not your gamer tag)
• LinkedIn URL (customize it: linkedin.com/in/jane-smith, not the auto-generated string)
• Portfolio or GitHub link (essential for tech roles)
• Skip: photo, marital status, date of birth, nationality (illegal to consider in the US)

Section 2: Education#

For first-time job seekers, education comes second (right after header). Move it lower once you have 2+ years of work experience.

Format:

University of Boston | B.S. Computer Science | May 2026
Boston, MA | GPA: 3.7/4.0 (Major GPA: 3.9)
Relevant Coursework: Data Structures, Algorithms, Operating Systems, Machine Learning
Honors: Dean's List (5 semesters), Phi Beta Kappa

Notes:

• Include GPA if 3.4 or higher (omit if lower)
• Include major GPA if higher than overall
• Relevant coursework: list 4 to 6 courses that match the job
• Honors: include scholarships, dean's list, top awards
• Skip: high school information (always)

For graduate degrees, list both:

MIT | M.S. Computer Science | June 2026
Cambridge, MA | GPA: 3.85/4.0
Thesis: Optimizing distributed training for large language models

University of Michigan | B.S. Computer Engineering | May 2024
Ann Arbor, MI | GPA: 3.6/4.0 | summa cum laude

Section 3: Projects#

For first-time job seekers, this section is critical. Projects prove you can do the work even without traditional experience.

What Makes a Good Project Entry

Each project should have:

• A specific name (not just "Class Project")
• 3 to 4 bullet points showing what you built and why it matters
• The tech stack you used
• A link to live demo or GitHub (if possible)

Format

PriceWatch — Personal Project | github.com/jane/pricewatch
- Built a price-tracking app monitoring 12,000 products across 8 e-commerce sites
- Used Python, FastAPI, PostgreSQL, and Redis to process 200k page loads daily
- Acquired 2,400 daily users in 3 months through organic search and Reddit
- Tech stack: Python, FastAPI, PostgreSQL, Redis, AWS Lambda, Next.js

Notice:

• Specific numbers everywhere (12,000 products, 8 sites, 200k loads, 2,400 users)
• Mix of technical and impact bullets
• Tech stack explicitly listed
• Links to actual work

What If My Projects Are Smaller

That is okay. Even smaller projects can be framed well.

Class Project: Real-time Chat Application | github.com/jane/chatapp
- Built a real-time chat app supporting 50 concurrent users for a class project
- Used WebSockets to deliver messages with under 100ms latency
- Implemented user authentication, message persistence, and emoji reactions
- Tech stack: React, Node.js, Socket.io, MongoDB

Adding measurable details (concurrent users, latency, features) makes a class project sound substantial.

Include 2 to 4 Projects

Pick your best 2 to 4. Resist the urge to list every project you have ever done. Quality over quantity.

Section 4: Internships / Work Experience#

If you have any internships, list them. Even short or part-time experiences count.

Format:

Company Name | Role | Location | Dates
- Bullet 1
- Bullet 2
- Bullet 3

Without Internships

If you have no internships, do not invent fake experience. Instead, include:

• Research assistantships
• Teaching assistant roles
• Significant volunteer work
• Part-time jobs (even non-tech)

Translating Non-Tech Experience

If your only work experience is non-tech (retail, food service, customer service), translate it into business language:

Bad framing:

"Cashier at Target. Took customer orders and handled payments."

Good framing:

"Customer Service Associate, Target | Boston, MA | June 2024 – Present

• Managed 200+ daily customer interactions in a high-volume retail environment
• Resolved escalations and complex transactions, maintaining 98% customer satisfaction
• Trained 3 new associates on register procedures and inventory management"

The second version focuses on transferable skills (customer service, conflict resolution, mentorship) that any employer values.

Internship Format

If you have done an internship, lead with the strongest one:

Acme Tech | Software Engineering Intern | San Francisco, CA | June 2025 – August 2025
- Built data ingestion pipeline processing 50M records daily, reducing latency by 35%
- Wrote 200+ unit tests increasing code coverage from 65% to 88%
- Designed and shipped admin dashboard used by 12 operations team members
- Tech stack: Python, Apache Airflow, PostgreSQL, React, AWS

Specific numbers and outcomes. Make it sound like real engineering work, because it was.

Section 5: Skills#

For tech roles, group skills logically:

Languages: Python, JavaScript, TypeScript, Java, SQL
Frameworks: React, Next.js, Node.js, Express, FastAPI
Tools: Git, Docker, AWS (EC2, S3, Lambda), PostgreSQL, Redis
Other: REST APIs, GraphQL, CI/CD, Linux

Rules:

• Only list skills you can discuss in an interview
• Match the job description as closely as possible
• Do not list trivial skills (Microsoft Word, Outlook)
• No proficiency bars, stars, or percentages

For non-tech roles, list technical skills relevant to your field:

For marketing:

Skills: Google Analytics, Meta Ads Manager, HubSpot, Mailchimp, SEMrush, Figma, Notion, SQL (basics)

For finance:

Skills: Excel (advanced, including pivot tables and VBA), Python (Pandas, NumPy), SQL, Bloomberg Terminal, Tableau, Power BI

Section 6: Awards and Activities (Optional)#

Include only if relevant and impressive:

• Hackathon wins (specific events and placements)
• Open source contributions (specific projects)
• Leadership roles (clubs, organizations, with measurable impact)
• Publications (academic papers, technical blog posts)
• Significant volunteer leadership
• Scholarships or major academic awards

Example:

- 2nd Place, MIT Hack: Built a real-time crisis response app in 36 hours (2,400 lines of code, 14 collaborators).
- Tech Lead, Coding Club: Grew membership from 30 to 180 students over 2 years.
- Open Source: Active contributor to React documentation (15+ merged PRs).
- Published: "Optimizing PyTorch Models" — Medium article with 50k+ reads.

If you do not have impressive activities, skip this section entirely. Half a page of weak content is worse than zero.

What to Cut#

Open your draft resume and delete:

• "Objective: To obtain a position where I can use my skills..."
• "References available upon request"
• Hobbies (unless directly relevant)
• Photo
• High school information
• Skills you cannot discuss
• Anything generic ("hard worker," "team player," "fast learner")
• Activities that seem like filler

Tailoring for Each Application#

One resume does not fit all. For each application, spend 10 minutes:

1. Read the job description carefully
2. Highlight every skill and technology mentioned
3. Edit your resume to include those exact keywords
4. Reorder projects to put the most relevant one first
5. Adjust the skills section to match

Run your tailored resume through our ATS checker to make sure it scores above 75 for the specific JD.

Common Mistakes#

Mistake 1: Padding With Filler

When desperate, candidates pad their resumes with weak content. This makes the resume worse, not better.

Cut filler. A focused half-page is better than a padded full page.

Mistake 2: Listing Activities Without Outcomes

Bad:

"Member, Coding Club"

Good:

"Organized 6 workshops for Coding Club, attended by 200+ students total"

Every bullet should have a number or specific outcome.

Mistake 3: Inflating Experience

Do not claim "Senior Software Engineer" if you were an intern. Do not claim "led a team" if you were a member of a team.

Recruiters can tell, and inflation often gets discovered in interviews.

Mistake 4: Generic Objectives

Skip objectives entirely for first-time job seekers. They waste space and never help.

Mistake 5: Poor Formatting

Use:

• Calibri, Arial, or Inter at 10 to 11 points
• 0.5 to 0.75 inch margins
• 1.0 to 1.15 line spacing
• Bold section headings
• Consistent formatting throughout

Avoid:

• Tables (ATS parsers struggle)
• Headers and footers (often ignored by parsers)
• Photos
• Colored backgrounds
• Multiple columns (ATS struggles)
• Fancy fonts

Save as PDF (not DOC unless requested), with filename like Jane_Smith_Resume.pdf (not resume_final_v3.pdf).

The First Job Reality#

Your first resume will not be perfect. You will refine it over the years.

But the first resume needs to:

• Get past ATS filters
• Convince a recruiter in 10 seconds
• Land you a phone screen

If you have a strong portfolio, education, and 2 to 3 quantified projects, you have everything you need to land your first job.

What to Do This Week#

If you are writing your first resume:

1. Create a one-page draft using the structure above
2. Quantify every bullet (numbers, percentages, dates, scope)
3. List 2 to 4 strong projects with specific outcomes
4. Translate any non-tech experience into business language
5. Run through our ATS checker
6. Get feedback from 2 to 3 people in your target field
7. Iterate until it tells a clear story

Your first resume is the foundation of your career. Spending 5 to 10 hours getting it right will pay off across hundreds of future applications.

You do not have years of experience yet. But you have specific skills, real projects, and unique potential. Make sure your resume shows it.