Best Resume Format for Tech Jobs in the USA

Your resume has six seconds. That is the average time a tech recruiter at Google, Meta, or any well-funded startup spends on a first pass. In six seconds they decide: pile A (call back) or pile B (forget).

If your resume has the wrong format, you lose before they read a word about your skills.

Here is the format that consistently works for tech roles at US companies in 2026, broken down section by section.

The One-Page Rule (And When to Break It)#

For anyone with less than 10 years of experience, one page. Period. Two pages signal that you do not know how to prioritize, and tech recruiters absolutely judge that.

Exceptions where two pages are acceptable:

• Senior engineer or staff level with extensive open-source contributions
• Principal or distinguished engineer roles
• Roles requiring publications (research scientist, ML researcher)
• Engineering manager with multiple team leadership stints

If you are a new grad, mid-level engineer, or even a senior engineer with under a decade of experience, one page is the standard.

The Universal Tech Resume Structure#

In this exact order:

1. Header (name, contact, links)
2. Summary (optional, 3 lines max)
3. Experience
4. Projects (for new grads or career switchers)
5. Education
6. Skills
7. Certifications (if relevant)

Skip: hobbies, references, photos, objective statements, declarations.

Section 1: The Header#

Jane Smith
San Francisco, CA | (415) 555-0123 | jane.smith@email.com
linkedin.com/in/janesmith | github.com/janesmith | janesmith.dev

Three lines. That is enough. Notes:

• Use your real city and state. Recruiters filter by location.
• Phone number with area code, no country code if you are in the US.
• Email should be professional. Yourname@gmail.com, not coolcoder1995@aol.com.
• LinkedIn, GitHub, and portfolio links should all be one click away.
• For senior or specialized roles, add a Stack Overflow, Kaggle, or Medium link if active.

Skip the photo. US employers cannot legally consider it, and including it raises flags about cultural fit with US hiring norms.

Section 2: The Summary (Optional)#

Skip the summary if you have under 2 years of experience. Your resume is already short enough.

For mid-level and above, use 3 lines maximum. Include:

• Your target role
• Years of relevant experience
• 2 to 3 standout skills or domains
• A measurable highlight

Example for a backend engineer:

"Backend engineer with 6 years building distributed systems in Go and Python. Shipped infrastructure handling 50M+ daily requests at two Series B startups. Looking for senior IC roles working on payments or developer tools."

Avoid generic openings like "passionate engineer looking for challenging opportunities." Every resume says that. None of them get callbacks because of it.

Section 3: Experience (The Core)#

This is where you win or lose. Each role gets:

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

For your most recent role, 4 to 6 bullets. For older roles, 2 to 3. The further back you go, the shorter it gets.

The Bullet Formula

Every bullet should follow this pattern:

[Action verb] [what you did] [using what tool/skill] [resulting in what measurable outcome]

Examples:

"Designed and shipped a real-time notification service in Go and Kafka, reducing alert latency from 8 seconds to 200ms across 2M users."

"Led migration of legacy Python monolith to FastAPI microservices on AWS ECS, cutting deployment time by 75 percent and infrastructure costs by $180k annually."

"Built React dashboard for internal analytics consumed by 40 product managers daily, replacing a deprecated Tableau setup."

Strong Action Verbs for Tech Resumes

Use these instead of weak verbs like "worked on" or "responsible for":

• Built, Designed, Architected, Developed
• Shipped, Launched, Deployed, Released
• Optimized, Reduced, Scaled, Improved
• Led, Drove, Owned, Coordinated
• Migrated, Refactored, Rewrote, Modernized
• Automated, Streamlined, Integrated

Avoid:

• "Helped with" (sounds passive)
• "Worked on" (no ownership)
• "Was responsible for" (boring)
• "Participated in" (you should never lead a bullet with this)

Quantify Everything Possible

Numbers prove impact. Find them everywhere:

• Lines of code (sometimes useful for very large refactors)
• Users impacted (DAU, MAU, customer count)
• Revenue (saved, generated, prevented loss)
• Performance (latency reduced, throughput increased)
• Time (cycle time, lead time, on-call reductions)
• Team size (engineers managed, code review load)
• Scale (requests per second, queries per second, GB processed)

If you cannot remember exact numbers, estimate conservatively and use ranges. "Reduced costs by approximately $50k annually" is fine. "Reduced costs significantly" is not.

Section 4: Projects (When to Include)#

Include a Projects section if:

• You are a new grad with limited internships
• You are switching careers into tech
• You have impressive side projects relevant to the role
• You have open-source contributions worth showing

Each project gets:

Project Name | Tech Stack | GitHub link
- 2 to 3 bullets about what you built and the impact

Example:

PriceWatch | Python, FastAPI, PostgreSQL, AWS | github.com/jane/pricewatch

• Built price-tracking app monitoring 12,000 products across 8 e-commerce sites, used by 2,400 daily users.
• Designed scraper pipeline using Celery and Redis, processing 200k page loads daily with 99.5 percent uptime.

If you have a strong full-time job, skip Projects. If you have 8 years of experience, Projects looks like padding.

Section 5: Education#

Reverse chronological. Format:

University Name | Degree | Graduation Year
Location | GPA (if 3.5+)
Relevant Coursework: (only for new grads)
Honors: (only for top awards)

New grad example:

Stanford University | B.S. Computer Science | June 2024 Stanford, CA | GPA: 3.8/4.0 Relevant Coursework: Distributed Systems, Machine Learning, Operating Systems, Algorithms Honors: Phi Beta Kappa, Dean's List (6 quarters)

Mid-career example:

MIT | M.S. Computer Science | 2021 Carnegie Mellon | B.S. Electrical Engineering | 2019

Skip high school. Always.

Section 6: Skills#

Group by category. Use this order:

Languages: Python, Go, TypeScript, SQL
Frameworks: React, FastAPI, Django, Next.js
Cloud and Infrastructure: AWS (EC2, S3, Lambda, ECS), Terraform, Docker, Kubernetes
Databases: PostgreSQL, Redis, DynamoDB, MongoDB
Tools: Git, Jenkins, Datadog, PagerDuty

Rules:

• List skills you can actually discuss in an interview
• Match the job description as closely as possible
• Avoid soft skills here (teamwork, leadership) — those belong in bullets
• No proficiency bars, star ratings, or percentages
• Do not list HTML or CSS for senior backend roles
• Do not list Microsoft Word ever

Section 7: Certifications (If Relevant)#

Only include certifications recognized in the tech industry:

• AWS Certified Solutions Architect (Associate or Professional)
• Google Cloud Professional Cloud Architect
• Azure Solutions Architect Expert
• Certified Kubernetes Administrator (CKA)
• HashiCorp Terraform Associate
• PMP (for engineering management roles)

Skip Udemy course completions, Coursera certificates that are not full degrees, and one-off bootcamp graduations.

Format and Visual Choices#

• Font: Inter, Helvetica, or Calibri at 10 to 11 points
• Section headings: 12 to 13 points, bold
• Margins: 0.5 to 0.75 inches all around
• Line spacing: 1.0 to 1.15
• Color: pure black text on white, maybe one accent color (dark blue, dark green) for headings only

Save as PDF with your name in the filename: Jane_Smith_Resume.pdf. Not resume.pdf, not resume_final_v3_actually_final.pdf. Recruiters file these by name.

What to Cut Right Now#

Open your current resume and delete:

• The objective statement
• The "References available upon request" line
• Hobbies (unless they show technical depth, like contributing to open source)
• A photo
• High school information
• Skills you cannot discuss
• Bullets without numbers
• Any role longer than 10 years ago described in detail (one line is enough)

Tailoring Per Application#

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

1. Read the job description twice
2. Highlight every skill, tool, and requirement mentioned
3. Match those exact words in your resume
4. Move the most relevant role's bullets to the top
5. Adjust the summary to mirror the job title

A targeted resume converts 5x better than a generic one. The math is simple: 10 minutes per application versus weeks of silence.

Test Before You Send#

Before you hit submit on any application, run your resume through our free ATS checker. It scores your resume against the job description and tells you exactly which keywords you are missing, what formatting issues might trip up parsers, and how strong your bullet impact is.

If you want help rewriting weak bullets, use our cover letter and resume tools to generate tailored versions for each role you apply to.

The Bottom Line#

A well-formatted tech resume in 2026 is short, scannable, and surgical. It has no fluff, every line earns its place, and every claim is backed by a number or a specific tool.

Recruiters at top US companies see hundreds of resumes per role. The ones they call are not always the smartest candidates. They are the candidates who made the recruiter's job easiest.

Make your resume that resume.