Skip to content

Resume rules and structure

For interns, new grads, and engineers with 0 to 3 years of experience. You will finish with a one-page base resume, sections in the right order for your track.

How a resume gets read

Stage Who reads it What they check What you control
1. Application form Knockout questions set by the recruiter (Oracle Taleo docs) Work authorization, location, graduation date, degree Truthful answers that match your resume
2. Parser The applicant tracking system (ATS) Name, contact, dates, sections, plain text One column, standard headings, a text PDF
3. Search and ranking Recruiter keyword search (Greenhouse) and AI match grades (Workday HiredScore) The job's basic and preferred qualifications The job's exact terms, backed by real work
4. First human look A recruiter: 5 to 10 seconds on the first pass (Georgia Tech CS Resume Guide), median 31 seconds in a 2024 study (interviewing.io) Company names, school, outcomes in the top third Your strongest evidence placed first
5. Interviews Engineers Every line you wrote Only claims you can defend for 5 minutes

In that study, 76 recruiters judged about 1,000 resumes and picked correctly only 55% of the time. Candidates with FAANG or FAANG-adjacent experience were 35% more likely to be picked. You cannot add a company name you do not have, so put your best evidence in the top third.

Watch out: A resume is necessary, not sufficient. Jugal: "When I was searching for my first US role, I sent around 700 applications and got 3 interviews." He fixed it with people, not a better resume (7 videos on networking your way to offers). Pair this section with referrals.

Ten rules

  1. Keep it to one page. Laszlo Bock, then Google's head of People Operations: "one page per 10 years of work experience" (HC Magazine). Gayle Laakmann McDowell: a second page adds "weaker content to your resume, by definition" (Fortune). Google sets no hard limit but says "Keep it short" (how we hire); UK CVs are the exception (country formats).
  2. Use one column and standard headings. Education, Experience, Projects, Skills. Parsers and recruiters both look for them (how ATS works).
  3. Put your strongest evidence in the top third. Most relevant role first, most relevant bullet first inside each role.
  4. Write every bullet as result, measure, method. Google's wording: "accomplished [X] as measured by [Y], by doing [Z]" (Google: how we hire). Full method: writing bullets.
  5. Tailor. Keep one base resume, one version per role type, and a full pass for your top roles (tailoring).
  6. Write only what you can defend. Jugal: "Do not exaggerate. You'll be asked about everything in the interview" (The New Grad and Internship prep for 2026).
  7. Send a text PDF named after you. Use Firstname_Lastname_Resume.pdf. The Georgia Tech guide asks for your name in the file name.
  8. Ship zero typos. Bock calls typos "deadly" because employers read them as carelessness. In one company's 2012 hiring data, typo count was the strongest signal of who got an offer (interviewing.io); it is one small dataset, and the fix costs 10 minutes.
  9. Make every link clickable and current. Stale GitHub and LinkedIn profiles hurt you (The Tech Resume Inside Out: common mistakes).
  10. Match your LinkedIn. Same titles, companies, and dates (LinkedIn profile guide).

Section order by track

Intern, no internship yet

# Section What goes in Notes
1 Header Name, city and state, phone, email, LinkedIn, GitHub No photo, no date of birth
2 Education School, degree, expected graduation month and year, GPA if 3.5/4.0 or higher, 4 to 6 relevant courses High school only in your first semester or for a national-level award
3 Projects 2 to 4 projects, each linked to GitHub or a demo Your main evidence. Give it the most space
4 Experience TA, grader, research, tutoring, freelance, part-time jobs Non-CS jobs get 1 to 2 bullets
5 Skills Languages, frameworks, tools, databases Only what you can be interviewed on
6 Leadership and awards (optional) Hackathon placements, club roles with numbers, scholarships Show selectivity: "1 of 230 selected"

Georgia Tech's rule: "If your Work Experience is unrelated to CS you should list your Programming Projects then your Work Experience."

Intern with an internship, research, or TA role

# Section What goes in Notes
1 Header As above
2 Education As above Coursework only if there is room
3 Experience Internship, research assistant, TA, co-op 4 to 6 bullets for the most relevant role (Georgia Tech), 3 to 4 if the page is full
4 Projects 2 to 3 projects Pick ones that show skills your experience does not
5 Skills As above
6 Leadership and awards (optional) As above

New grad

# Section What goes in Notes
1 Header As above
2 Education Degree, school, graduation month and year, GPA if strong Drop coursework if the page is full
3 Experience Internships and co-ops first, then research and TA 4 to 6 bullets for the most relevant role, 1 to 2 for others (Georgia Tech)
4 Projects 2 to 3 projects Tech Interview Handbook: "Include at least 2 projects"
5 Skills Grouped lines Order by the job description
6 Awards (optional) Hackathons, scholarships, competitive programming ranks One line each

Experienced, 1 to 3 years full-time

# Section What goes in Notes
1 Header As above
2 Summary (optional) 1 to 2 lines, tailored to the role Skip it if it says nothing a recruiter can check
3 Experience Current role first, 3 to 6 bullets Promotions as separate titles under one company
4 Skills Grouped lines
5 Projects (optional) Only if they show something your job does not
6 Education Degree, school, year Drop GPA and coursework

The Tech Interview Handbook keeps Education above Experience until about 3 years. Decide by signal: if your employer name is stronger than your school, lead with Experience.

Career changer into software

  1. Put Projects right under the header (Georgia Tech rule above).
  2. Keep past jobs, but rewrite bullets toward automation, data, tools you built, and scale you handled.
  3. Put a bootcamp or non-CS degree after Projects.
  4. Use a 1 to 2 line summary that names the target role and the bridge. This is the one case where a summary earns its space.

Quick comparison

Section Intern New grad 1 to 3 years
Education 2nd 2nd Last
Experience 3rd or 4th 3rd 2nd or 3rd
Projects 3rd or 4th 4th Optional
Skills 5th 5th 4th
Summary No No Optional
GPA If 3.5+ If 3.5+ Drop
Coursework Yes, if room Rarely No

The header

[FULL NAME]
[City, ST] | [phone] | [personal.email@domain.com] | linkedin.com/in/[handle] | github.com/[handle]
  1. List four or five contact items. The Tech Resume Inside Out suggests about four: phone, email, LinkedIn, GitHub.
  2. Write city and state only. Tech Interview Handbook: "Just enough for recruiters to determine if you are a local or international candidate."
  3. Use a personal email. Never a work email or work phone (Tech Interview Handbook).
  4. Show readable link text such as linkedin.com/in/handle and make it clickable.
  5. Add a portfolio site only if it shows work that GitHub does not.
  6. Leave out photo, date of birth, age, marital status, nationality, and street address for US and UK roles.
  7. Leave visa status off by default; the application form asks. Exceptions: international students.

Education

Item Include when Write it like
School, degree, major Always B.S. in Computer Science, [University], [City, ST]
Graduation date Always as a student Expected May 2027. NVIDIA and Google EMEA intern postings ask for graduation month and year on the resume
GPA 3.5/4.0 or above (Georgia Tech, Tech Interview Handbook), or above 4.3 on a 5-point scale GPA: 3.72/4.00
GPA on a 10-point scale Only if strong. Show the original scale, do not convert CGPA: 8.7/10
Relevant coursework Room left and few projects or internships. Google says recent grads can include coursework (how we hire) 4 to 6 upper-level courses on one line
High school First semester only, or a national-level result (olympiad medal, top test rank) One line
Exchange or study abroad Optional One line under the main degree

Tip: Google intern postings ask for a transcript too (internships). Keep an English transcript PDF ready next to your resume.

Experience: what counts

Type Counts as Experience? Where it goes
Internship or co-op Yes Experience
Teaching assistant, grader, teaching fellow Yes. Harvard's 2026 CS example lists a Teaching Fellow role under experience (PDF) Experience
Research assistant Yes Experience
Paid freelance or contract work Yes Experience
Open-source programs (Google Summer of Code, MLH Fellowship, LFX Mentorship) Yes Experience
Hackathon Usually a project Projects, placement in Awards
Non-tech part-time job Yes, 1 to 2 bullets Below Projects if your CS work is thin
Club leadership Only with scale (members, events, money) Leadership

Bullet count per role: 4 to 6 for high-relevance positions and 1 to 2 for low-relevance ones (Georgia Tech). On a full student page, 3 to 4 for your best role is a practical floor.

Skills

Languages: [Python, Java, C++, SQL, TypeScript]
Frameworks: [React, Node.js, Spring Boot, FastAPI, PyTorch]
Cloud and tools: [Amazon Web Services (AWS), Docker, Git, GitHub Actions, Linux]
Databases: [PostgreSQL, Redis, MongoDB]
  1. List only what you could answer interview questions about. Jugal: "If the role asks for Kafka and you have never used Kafka, do not add Kafka" (I Asked Claude to Make My Resume Unrejectable).
  2. Leave out soft skills. Georgia Tech: "Do not list soft skills in this section."
  3. Leave out skill bars and ratings. They "can only backfire" (The Tech Resume Inside Out).
  4. Order each line by the job description's priority.
  5. Spell out an acronym once: "Amazon Web Services (AWS)" (Tech Interview Handbook).
  6. Add AI coding tools only if you used them on real work. Amazon's Summer 2027 SDE intern posting lists "Experience using AI-assisted development tools in academic or professional settings" as a basic qualification (posting).

Certifications and courses

Certificates add searchable terms and recognizable provider names at entry level. Jugal's rules from The "Borrowed Logo" Strategy:

  1. Put them in their own section, clearly labelled. Never under Experience.
  2. Pick 3 to 7 that match the job. Do not dump every course.
  3. Use one line each. Add an optional Topics line when the certificate name hides the skills:
CERTIFICATIONS
[Certificate name], [Provider], [Year]
[Certificate name], [Provider], [Year]
Topics: [Python, SQL, APIs, Docker]

Certificates rarely beat projects. Jugal's heading from Top 30 AI Certifications: "Certificates Get the Interview and Projects Get the Offer."

Source Cost How to use it
CS50x Free Finish the problem sets and final project, then list the certificate if you have no CS degree
AWS Skill Builder Free courses; paid subscription and exams Do the free cloud fundamentals path before applying to cloud-heavy roles
Microsoft Learn credentials Free learning, paid exams Fundamentals exams (for example AZ-900) are a cheap first credential
Google Skills Freemium (some free monthly lab credits, paid subscriptions) Earn a cloud or AI skill badge for cloud or AI roles
freeCodeCamp Free Project-based certifications for web roles
HackerRank skills certification Free Timed tests in problem solving, Python, SQL. Doubles as online assessment practice

Summary or objective

Situation Summary? Source
US student or new grad No Gayle: "No summaries." Georgia Tech: "When in doubt, leave it out"
1 to 3 years Optional, 1 to 2 lines, tailored Tech Interview Handbook allows a short summary for experienced candidates
Career changer Yes, 1 to 2 lines Explains the jump
UK CV Yes, a short profile Prospects
Weak:   Motivated computer science student seeking challenging opportunities to grow.
Strong: Backend engineer, 2 years on payments APIs in Java and AWS; cut p99 latency [60%] on a [5k] requests/sec service.

What to cut

Cut Why Source
Photo, date of birth, age, marital status, father's name, "Declaration" Not expected in US or UK; invites bias The Tech Resume Inside Out, Prospects, Jugal
Street address City and state are enough Tech Interview Handbook
"References available on request" Wasted line The Tech Resume Inside Out
Objective line Says nothing checkable Gayle, Georgia Tech
Soft skills in Skills Unverifiable Georgia Tech
Skill bars and ratings "Can only backfire" The Tech Resume Inside Out
"Responsible for..." Duties, not results Amazon recruiters, Jugal
Internal project code names The reader cannot decode them The Tech Resume Inside Out
High school after your first semester Weaker than college content Georgia Tech
Every tool you touched once You will be asked about it Jugal
Hidden white text or AI prompts Detected and penalized Built In
Columns, icons, images, tables Break parsing Workday docs, OpenResume

Build your base resume this weekend

  1. Watch Jugal's walkthrough of the resume he used for Amazon: This Resume Got Me Into Amazon (about 10 minutes).
  2. Dump everything into a plain doc: every project, internship, TA role, hackathon, club role, award, and pull request. Jugal: "Write down every single thing you've ever done professionally. Everything. We'll cut it down later" (Amazon is still hiring after the biggest layoffs).
  3. Open a template. Default: Jake's Resume on Overleaf. Other options and setup steps: templates.
  4. Fill the header with the rules above.
  5. Pick your section order from the track tables above.
  6. Write each bullet with the X, Y, Z method (writing bullets).
  7. Choose 2 to 4 projects (how to choose projects).
  8. Write three to four Skills lines.
  9. Cut to one page. Remove the weakest bullet first, not the font size.
  10. Export a PDF, name it Firstname_Lastname_Resume.pdf, and run the 10-minute parse test.
  11. Run the final checklist.
  12. Get two human reviews (free review sources).
  13. Save this as your base. Make role-type copies next (tailoring).

Tip: Keep a running "wins" doc. Every time you ship something, write one line with the number. Your next resume update then takes 20 minutes instead of a weekend.

What the companies say

Company What they say Link
Google Build a resume for each job, show you meet the minimum qualifications, use the X, Y, Z formula, no length requirement but keep it short. Cover letters are not required. You can apply to up to three jobs every 30 days How we hire, recruiter video (2019), Google page
Amazon Keep it "text-forward, black and white, and simple". Focus on actions and results. Align with the posting's Basic and Preferred Qualifications Amazon recruiters' tips, recruiter video Q&A, Amazon page
NVIDIA The 2027 software engineering intern posting says your anticipated graduation month and year "must be clearly indicated on a resume or CV to be considered". It also states that NVIDIA uses AI tools in recruiting (as of Oct 2026) 2027 SWE intern posting, NVIDIA page
Anthropic Write the first draft yourself, then you may use Claude to refine it Candidate AI guidance, Anthropic page
Meta, Microsoft No public resume-writing guide found (as of Oct 2026). The general rules on this page apply Meta page, Microsoft page

Free reading, in order

  1. Tech Interview Handbook: Resume: free SWE resume guide by Yangshun Tay, updated Aug 2026. How to use it: read the ATS and keyword sections, then run its plain-text test on your PDF.
  2. Georgia Tech CS Resume Guide (2026 PDF): a university CS guide with section rules and a CS verb list. How to use it: copy its bullet-count rule and verb list.
  3. Harvard College CS Resume Example (2026 PDF): an annotated student CS resume. How to use it: compare your section order and how it lists a TA role.
  4. The Tech Resume Inside Out: free sample chapters by Gergely Orosz. How to use it: run your resume against each mistake. The full book is paid; developers without a job can request a free copy.
  5. Gayle Laakmann McDowell on Fortune (2014): short rules from the author of Cracking the Coding Interview. How to use it: apply the bullet-length and quantify rules. Skip the dated language advice.
  6. interviewing.io: Are recruiters better than a coin flip?: the 2024 study above. How to use it: read it once to see why the top third matters.

Jugal's resume posts

All posts by section: Substack index.

Next: Write bullets that show impact