Correction, 17 October 2026. Earlier versions of this article said software roles draw 500 to 2,000+ applicants, that an ATS surfaces only the top 5 to 10% to recruiters, and described how big-tech in-house systems weight keywords and which ATS specific companies use. Those claims had no source, so we have removed them. The structure, keyword and bullet advice below is unchanged.
Software engineering roles at well-known companies draw a large pile of applicants, and recruiters search and filter that pile by language, framework and experience rather than reading every file. The good news for engineers: tech searches are concrete and keyword-based. The bad news: many engineering resumes are formatted in ways that scramble parsing.
The 3 ATS problems common on engineering resumes
1. Multi-column layouts (the biggest tech-resume mistake)
Engineering candidates love clean two-column resume templates, sidebar for skills/contact, main column for experience. Looks beautiful. Risky for ATS parsing. Your "Languages: Python, Go" sidebar can get read as part of your job title or sandwiched between bullets from the wrong role. If you write yours in LaTeX, the same applies to AltaCV and Deedy, and there are two extra traps, ligatures and icon fonts, covered in are LaTeX resumes ATS-friendly.
2. GitHub/portfolio links rendered as image-based icons
Many tech templates show your GitHub/LinkedIn/portfolio URLs as small icons with the URL hidden in a hyperlink. The parser drops the icon (it's an image) and, depending on the template and system, may not keep the hyperlink either. Result: your candidate profile may have no portfolio link, which many tech recruiters want to see.
3. Skills shown as proficiency bars or radial graphs
"Python ████████░░ 80%" looks polished. The parser sees, at best, the word "Python". The bar is a graphic, not text, so the proficiency it shows is lost.
The ATS-friendly tech resume structure
FULL NAME (16-18pt, bold) Senior Software Engineer | Distributed Systems | 8+ Years City, Country • +Phone • email@domain.com linkedin.com/in/handle | github.com/handle | yourdomain.com PROFESSIONAL SUMMARY 2-3 sentences. Years of experience + specialization + one quantified career-defining result. PROFESSIONAL EXPERIENCE Senior Software Engineer, Company Name Remote (San Francisco) | Month Year – Month Year • Bullet: action verb + measurable outcome + tech keyword • Bullet: action verb + measurable outcome + tech keyword • Bullet: action verb + measurable outcome + tech keyword • Bullet: action verb + measurable outcome + tech keyword EDUCATION Bachelor of Science in Computer Science University Name | Year graduated TECHNICAL SKILLS Languages: Python (expert), Go, TypeScript, Rust (intermediate), SQL Frameworks: React, Next.js, Django, FastAPI, Express Cloud: AWS (Lambda, S3, RDS, CloudFront), GCP, Vercel Infrastructure: Docker, Kubernetes, Terraform, GitHub Actions Databases: PostgreSQL, Redis, MongoDB, ClickHouse Specializations: Distributed systems, Real-time data processing, OAuth/SSO CERTIFICATIONS (if relevant) AWS Certified Solutions Architect, Year Certified Kubernetes Administrator (CKA), Year OPEN SOURCE / SIDE PROJECTS (optional but recommended) [Project Name], [GitHub stars / downloads / impact] Brief description.
The contact line, make every link text-extractable
For tech roles, your portfolio links matter as much as your resume content. Format them as plain text that the parser can extract:
Bad (icons + hidden URLs): 🐙 ✉ 🔗 (icons only, no parseable text)
Good (text URLs): email@domain.com | linkedin.com/in/handle | github.com/handle | yourdomain.com
If the role specifically mentions reviewing GitHub portfolios, put the GitHub URL prominently and consider listing 1-2 specific repos with stars/forks counts.
Tech-specific keyword strategy
Languages section, be honest about proficiency
Don't list every language you've ever touched. Tech recruiters check during interviews, and "Python (advanced)" claims that fall apart in a coding interview are death. Use:
- (expert), for languages you can teach others, debug deep issues, write production code in
- No qualifier, for languages you use regularly and could ship features in
- (intermediate), for languages you've shipped projects in but aren't day-to-day
- (familiar), for languages you've explored but wouldn't claim to be productive in
Frameworks & libraries, match the JD
If the JD mentions "Next.js, TypeScript, React Server Components," your resume should mention all three explicitly (not just "React"). Some systems do partial matching, but a recruiter's search is often literal, so exact matches are safer.
Cloud platforms, be specific
"AWS" alone is too generic. List the specific services you've used: "AWS (Lambda, S3, EC2, RDS, CloudFront, IAM)." This signals depth and matches JDs that specifically require those services.
Infrastructure tools, list everything you've shipped with
Docker, Kubernetes, Terraform, Ansible, GitHub Actions, CircleCI, ArgoCD, Helm, these are the keywords recruiters search for in DevOps/SRE/Platform Engineering roles. Even if you're applying to a frontend role, listing relevant infra tools you've worked with shows engineering breadth.
Bullet examples for engineers (XYZ format)
Backend / Distributed Systems:
- "Reduced p99 API latency from 800ms to 120ms by replacing synchronous database calls with async caching layer (Redis + read replicas), serving 50M+ requests/day."
- "Designed and shipped event-driven order processing pipeline using Kafka + AWS Lambda, processing 200K orders/hour with 99.99% reliability."
Frontend:
- "Cut bundle size from 2.4MB to 480KB by migrating to Next.js with code splitting and dynamic imports, improved Lighthouse score from 62 to 96."
- "Built end-to-end checkout flow used by 200K+ monthly customers, achieving 4.1% conversion (vs 2.8% baseline)."
Full-stack:
- "Architected internal admin tool from scratch (Next.js, tRPC, Prisma, PostgreSQL) used by 80+ ops staff to manage $40M+ in monthly transactions."
DevOps / SRE:
- "Eliminated 4 hours/week of manual deploy work by building CI/CD pipeline (GitHub Actions + ArgoCD + Helm), enabling 50+ daily deploys with zero-downtime rollouts."
For FAANG / top-tier applications
Big-tech recruiters and hiring managers screen hard on scale and depth. Optimize for:
- Scale numbers: users served, requests/sec, dollar amounts, team sizes, even rough numbers beat no numbers
- System design keywords: "horizontal scaling," "load balancing," "consensus algorithms," "eventual consistency", these signal senior engineering thinking
- Open-source contributions: link to repos with star counts ≥100 if you have them
- Top-tier prior employers: if you've worked at recognized tech companies, make the names easy to spot
For startup / fast-growing company applications
At smaller companies, recruiters and founders often read applications more directly. Optimize for:
- Generalist signals: "shipped from idea to production," "owned full lifecycle," "wore multiple hats"
- Speed signals: "shipped X in 6 weeks," "0 to 1 product launches"
- Founding/early-employee signals: if applicable, mention founding team or first 10 engineers
One last thing, the GitHub honesty check
If you list GitHub on your resume, your GitHub WILL be checked. Some recruiters look at:
- Activity frequency (do you commit regularly?)
- Code quality on top repos
- Whether claimed contributions match real ones
If your GitHub is empty or 5 years stale, consider not linking to it, or making the few good repos prominent. An empty GitHub linked from a resume is worse than no link.
Test before you apply
Engineering resumes can break parsing in their own ways, especially around stack lists, tool names, and links. Run yours through ATS Verification to confirm:
- Your name extracts correctly
- Your most recent job title and company are detected
- Your years of experience calculates correctly
- Your skills section parses with all technologies
- Your portfolio links (GitHub, LinkedIn, personal site) are extractable
By region: 🇺🇸 US engineering market (Bay Area, NYC, Seattle, Austin) · 🇪🇺 European tech hubs (London, Berlin, Amsterdam, Dublin) · 🇦🇺 Australian tech (Atlassian, Canva) · 🇮🇳 Indian IT services (Bangalore, Hyderabad) · 🇧🇷 Brazilian tech (São Paulo, fintech).
For the canonical software-engineer resume strategy hub, covering staff/principal-level promotion narrative, system-design vocabulary, GitHub linking, how to list a tech stack, and big-tech vs scale-up vs services-firm applications, see our software engineers landing page.
By ATS platform: Workday · Greenhouse · Lever.
→ Free ATS scan for your engineering resume, see exactly what the parser extracts