Top ATS Keywords

• JavaScript
• TypeScript
• React
• Node.js
• Python
• AWS
• Docker
• Kubernetes
• CI/CD
• Microservices
• REST API
• GraphQL
• PostgreSQL
• Git
• Agile
• System Design
• Code Review
• Unit Testing

What Hiring Managers Look For

Engineering hiring managers scan resumes for three signals in order: scope, scale, and outcome. Scope is the breadth of systems you have shipped — front-end, back-end, infrastructure, data. Scale is the size of users or data your work has touched: ten users, ten thousand, ten million each tells a different story. Outcome is measurable impact: latency cut, revenue moved, cost saved, bugs eliminated. Lead every bullet with a verb-driven outcome and back it with a number. Avoid passive phrasing like "responsible for" — it tells nothing about what you actually shipped. Senior candidates need to surface architecture decisions, mentorship, and trade-offs, not just feature counts. Skip exhaustive "familiar with" lists; ATS systems heavily weight skills you have shipped recent production code with.

Sample Bullet Points by Experience Level

Entry-Level

• Built REST API endpoints in Node.js serving 5,000+ daily requests with sub-200ms p95 latency
• Reduced bundle size by 35% by migrating five legacy components to React Server Components
• Wrote 120+ unit tests, increasing backend coverage from 60% to 85% over a single quarter
• Shipped four customer-facing features during a 12-week internship, including a real-time chat module

Mid-Level

• Architected microservice refactor that cut deploy time from 45 minutes to 8 minutes and eliminated 80% of release-day rollbacks
• Led migration of 2M-row Postgres database to a partitioned schema, reducing query p99 from 4.2s to 380ms
• Mentored three junior engineers through onboarding; all reached full productivity in under 8 weeks
• Designed CI/CD pipeline using GitHub Actions and Vercel, reducing flaky deploys from 12% to under 1%

Senior

• Owned end-to-end design and rollout of authentication platform serving 12M users across four product surfaces
• Reduced infrastructure cost by $480K/year by consolidating three redundant services into a unified data layer
• Mentored team of seven engineers, with four promoted to senior in 18 months
• Drove technical strategy for org-wide TypeScript migration, eliminating ~60% of runtime type bugs

Common Resume Mistakes

Buzzword bingo skill list

Listing 25 technologies you have touched once kills credibility. Limit your skills section to 8-12 items you have shipped production code with in the last two years. ATS parsers do not reward unranked tech walls — they actually penalize them as keyword stuffing.

Vague job descriptions

"Worked on the user dashboard" tells a hiring manager nothing. Was the dashboard new or existing? How many users? What was the performance baseline before you touched it? Specificity is the cheapest signal you can buy.

No metrics anywhere

Engineering is measurable. If your bullets do not have numbers — users served, latency reduced, revenue impact, deploy frequency — they read as opinion, not evidence. At minimum one in three bullets needs a number.

Outdated tech stack

Listing jQuery, Backbone, or AngularJS in 2026 signals you have not kept current. If the tech is older than 8 years and not still actively maintained, drop it from skills (you can keep it in the relevant job bullet).

Walls of text instead of bullets

Hiring managers spend 6-10 seconds on a first pass. Paragraph-style job descriptions die there. Convert to 3-5 sharp bullets per role, most senior-relevant first. ATS parsers also handle bullet structure better than prose.

Career Path & Salary

US 2026 averages. Major tech hubs (SF, NYC, Seattle) skew 20-40% higher; remote-only or smaller markets typically 10-30% lower. Base only — total comp with equity can double these for senior+ at large public-tech employers.

Frequently Asked Questions

How long should a software engineer resume be?

One page if you have under 5 years of experience, two pages for senior or staff level. ATS does not care about length, but humans do — recruiters spend less than a minute on the first pass. Cut the oldest jobs first; if your second-to-last role does not have at least one measurable outcome, drop the bullet, not the role.

Should I include a GitHub or portfolio link?

Yes if it has real activity: at least 10-15 contributions in the past year and at least one project with a README explaining what it does and why it matters. An empty or 5-year-stale GitHub link hurts you more than no link at all.

How many bullet points per job?

3-5 for your current and most recent role, 2-3 for older positions. Lead with the most senior-relevant bullet, not the chronologically first one. ATS parsers and humans both scan top-to-bottom, so strong opening bullets carry the most weight.

Do I need a portfolio site?

Optional but high-leverage if you target product-focused companies. A simple Vercel deploy with 2-3 case studies — each showing problem, your design, and outcome — beats a 50-page Behance for engineers. Skip it if you have strong open-source contributions linked from GitHub.

Should I list every project I worked on?

No. Three projects you can talk about deeply beats ten you cannot. Each project should answer four questions: what problem, what design, what trade-off, what outcome. If you cannot answer all four for a project, leave it off.