Name the stack in every bullet
"Built REST APIs in Go" beats "worked on APIs". The ATS matches tools, and so do engineering managers.
Engineering job descriptions are full of exact tool names. If your resume says "backend work" and the ad says "Spring Boot microservices", the ATS may not connect them. PopCVs shows you the gap and helps you close it honestly.

List the languages, frameworks and cloud tools you have actually shipped with. Group them by type so a recruiter can scan them in seconds.
Switch between a typical resume and the PopCVs version. Same experience, very different keyword match.
Experience, software engineer (example)
Real experience, but in words the hiring software doesn't look for.
"Built REST APIs in Go" beats "worked on APIs". The ATS matches tools, and so do engineering managers.
Add numbers you can stand behind: requests per second, latency saved, users served, deploys per week.
Add your GitHub, portfolio or a live project. Make sure the repos you link are the ones you're proud of.
Early-career engineers should stay on one page. Senior engineers can use two if every bullet earns its place.
Your Name
Software Engineer · India
Summary
Backend engineer with 4 years building payment systems in Java and Spring Boot. Split a legacy monolith into microservices on AWS and set up CI/CD for a team of 8. Looking for a senior backend role at a product company.
An example to adapt. Write yours from your own experience: PopCVs never adds anything you haven't done.
Contact details with GitHub or portfolio links, a short summary, technical skills grouped by type, work experience with stack-specific bullets, projects and education.
One page for freshers and engineers with under five years of experience. Two pages is fine for senior engineers if every line is relevant to the role.
Yes, at least the summary and skills. Job ads use different names for similar tools, and matching their wording helps both the ATS and the recruiter.