← All resourcesWhat recruiters look for first
A software engineer resume gets ranked in seconds. These are the five signals a recruiter (and an LLM-ranked ATS) checks before deciding whether to keep reading.
- Technologies named at the top — primary languages, runtime, key infra
- Most recent role and years of experience visible without scrolling
- Each bullet starts with an action verb, not a noun phrase
- At least one number per role: latency, scale, throughput, users, cost saved
- A short summary line that names your specialty (frontend, distributed, infra, etc.)
Bullet patterns that work
Every strong software engineer bullet follows the same shape: action verb → what you built → who it was for → a number that proves the impact. Use these patterns as a scaffold, not a script.
Pattern
Built [system] that [scale signal], reducing [metric] by [number]Example
Built a Kafka-based ingestion pipeline handling 12k events/sec, reducing end-to-end latency from 4.1s to 380ms
Pattern
Led [scope] migration of [system] from [old] to [new], unblocking [outcome]Example
Led migration of the auth service from monolith to gRPC microservices, unblocking the mobile team's parallel rollout
Pattern
Designed [pattern] that replaced [old approach], cutting [cost or risk]Example
Designed an idempotent retry layer that replaced ad-hoc Sidekiq jobs, cutting duplicate-charge incidents to zero over 6 months
Skills section — what to keep
Recruiters skim skills sections for the keywords the JD mentioned by name. Lead with the hard skills, group your tools, and keep soft skills short.
Hard skills
- System design
- Distributed systems
- API design
- Database modeling
- Performance profiling
- Code review
Tools
- TypeScript
- Go
- Python
- PostgreSQL
- Redis
- Kafka
- Docker
- Kubernetes
- AWS / GCP
- Terraform
Soft skills
- Cross-team collaboration
- Technical mentorship
- Incident response
Pitfalls that get software engineers filtered
- Listing every framework you've ever touched — recruiters parse for depth, not breadth
- Burying impact under tool names ("used React, Redux, TypeScript, Webpack" tells nothing)
- Quantifying with vanity metrics (LOC written) instead of business or system metrics
- Skipping a one-line summary at the top — recruiters skim the first 8 seconds for a label
Frequently asked
How long should a software engineer resume be in 2026?
One page until you have 8+ years of experience or are applying for staff/principal levels. Two pages is fine for senior+ roles, but every line on page 2 needs to earn its space.
Should I include side projects or open source?
Yes if they show a skill your work history doesn't, or if you're early-career. Cut them if you have 5+ years of strong production work — recruiters at that level want production, not weekend code.
Do GitHub and personal site links matter?
Yes for early-career and yes for IC roles. A profile that's empty or has only forks reads worse than no link at all — only include it if it shows something.
Build this resume in HireDrive.
The free resume builder uses these patterns as defaults. The free resume checker tells you which lines a software engineer recruiter would skim past. No account needed for either.