How to Write a Resume as a College Student (2026 Guide)

If you are an undergraduate or recent graduate with less than three years of full-time work, your resume is one page. Recruiters at Amazon, Google, Goldman, McKinsey, and almost every Fortune 500 explicitly tell university recruiters to flag two-page student resumes as a maturity red flag.

The constraint is the point. A one-page limit forces you to cut weak bullets, kill the high school soccer captaincy, and lead with the work that signals you can do the job. If your draft is overflowing, fix the formatting first (margins to 0.5in, font to 10.5pt Calibri / Helvetica / Source Sans), then start deleting bullets that do not have a number, a tool, or a result.

Recruiters do not need a graphic. They need: your full name (in the largest font on the page, 18–22pt), a US phone number formatted as (555) 555-1234, a professional email (firstname.lastname@gmail.com is fine — no tigerfan2003@), your LinkedIn URL customized to linkedin.com/in/yourname, your GitHub or portfolio if it is relevant, and city + state. No street address. No date of birth. No photo. No marital status.

If you are an international student and you have a non-Western first name, do not anglicize it on the resume. Use the name you want recruiters to see in interviews. Optionally add a pronunciation in parentheses if you prefer.

For current students and graduates within 12 months of their degree, Education sits directly under the header. Include: school name, location, degree (write it out — "Bachelor of Science in Computer Science", not "B.S. CS"), expected or actual graduation date, GPA only if 3.4 or higher, and a "Relevant Coursework" line for technical roles (Data Structures, Algorithms, Linear Algebra, Operating Systems — 4 to 6 courses, not 12).

Honors, scholarships (Dean's List Spring 2025, full-tuition merit scholarship), and study abroad belong here as bullet points or a single line. Two schools? List the most recent one first; only include the previous school if there is a meaningful credit (e.g., associate degree from a community college before transferring).

The single biggest blocker for college students is the belief that the Experience section requires paid corporate internships. It does not. Any structured activity where you produced output for someone other than yourself counts: teaching assistant roles, undergraduate research, club leadership, hackathons, freelance projects, on-campus jobs, volunteer organizing.

The trick is to frame everything the same way: Action verb + specific work + measurable outcome. Not "Helped run the finance club." Instead: "Led a team of 6 analysts in running 4 mock stock pitches per semester; grew membership from 22 to 71 in two terms by launching a peer-mentorship program."

Here are three real before/after rewrites:

• Before: "Worked at campus dining hall." After: "Supervised 8-person shift handling 600+ meals during peak; redesigned order-flow process and cut average wait time from 9 to 5 minutes."
• Before: "Built a side project in Python." After: "Built a Flask web app that scrapes 5 job boards and emails weekly digests; live with 140+ subscribers and 100% uptime over 6 months."
• Before: "Volunteered with non-profit." After: "Coordinated logistics for 3 fundraising events that raised $14,200; managed 22 volunteers and grew social following from 380 to 1,800."

For technical roles, the Projects section often beats Experience for a sophomore or junior. Each project should be a 3-line block: project name (linked to GitHub or live demo), stack (languages, frameworks, libraries), and 2 bullets describing what you built and the result.

Result-language matters. "Built a stock predictor in Python" is vague. "Trained an XGBoost model on 5 years of S&P 500 data to predict 1-day price movement; achieved 58% directional accuracy on holdout set (vs 50% baseline)" is concrete. Recruiters cannot evaluate your code from a resume, but they can evaluate whether you understand what you built.

If you do not have 2–3 real projects on GitHub, that is your weekend for the next month. A clean project with a written README beats three half-finished tutorials.

Group skills into 3 or 4 categories, not a wall of comma-separated keywords. For a CS student that looks like:

• Languages: Python, Java, TypeScript, SQL, C++
• Frameworks & tools: React, Next.js, FastAPI, PostgreSQL, Docker, AWS (S3, Lambda)
• ML / Data: PyTorch, scikit-learn, pandas, NumPy
• Other: Git, Linux, Jira, Figma

Do not list anything you would not survive a 15-minute interview question on. Recruiters and engineers will probe.

• Objective statements. Replace them with nothing. Your resume is the objective.
• References available on request. Delete. Recruiters know they can ask.
• Buzzword soup. "Hardworking, results-driven, team player." These add zero signal. A bullet about results is the signal.
• Inconsistent date formatting. Pick "May 2025" or "05/2025" and use it everywhere.
• Past tense for current roles. Use present tense for what you are doing now, past tense for everything else.
• Decorative templates. Two-column layouts, photos, icons, color graphics — most are unreadable by ATS parsers. Use a clean single-column template.

Most large employers route resumes through an Applicant Tracking System (Workday, Greenhouse, Lever, iCIMS) before a human reads them. The system parses your PDF into structured fields. A modern ATS handles standard PDFs fine, but it will choke on tables, text boxes, images, headers/footers, and uncommon fonts.

Three rules: (1) Save as PDF, named FirstName_LastName_Resume.pdf. (2) Use standard section headings — Education, Experience, Projects, Skills. (3) Match keywords from the job description naturally. If the JD says "REST APIs", do not write "RESTful endpoints" — write "REST APIs". Do not stuff a keyword bank at the bottom in white text; modern ATS flags it and recruiters reject on sight.

For a deeper system-level walkthrough, see our resume writing service and the college student services page for what a recruiter-ready version looks like.

For a US college student in 2026, this is the canonical order:

1. Header (name, contacts, links)
2. Education (school, degree, GPA if ≥3.4, relevant coursework, honors)
3. Experience (internships, on-campus jobs, research, TA roles)
4. Projects (2–4 strongest)
5. Leadership / Activities (clubs, volunteer roles) — optional if you ran out of space
6. Skills (grouped, honest)

That is the structure. Now go write the bullets that prove you can do the job.