What to include (in this order)
- 1
Header
Name, phone, email, city, LinkedIn and GitHub.
- 2
Summary
Years of experience, your focus (backend, frontend, mobile), and the scale you've worked at.
- 3
Experience
Reverse-chronological. Company, role, dates, then 3–5 impact bullets per role.
- 4
Skills
Languages, frameworks, databases, cloud and tools — as plain text so ATS can read them.
- 5
Projects
Side projects or open source, especially if your job work is under NDA.
- 6
Education
Degree, college, year. Move it below experience after 2+ years of work.
Sample bullet points
- Redesigned the order service's caching layer, reducing p95 API latency from 820ms to 310ms.
- Led migration of 40+ cron jobs to a queue-based worker system, eliminating nightly failures.
- Built a React component library adopted by 4 product teams, cutting UI build time for new pages.
- Mentored 3 junior engineers and introduced code-review guidelines that halved rework.
Tips that make a difference
- Write bullets as: action + what you built + measurable result.
- Mention scale: requests per second, users, data size, latency.
- Don't list every library — keep the stack relevant to the role.
- Use a single column and standard headings so ATS parses skills correctly.
- Tailor the top half to each job description.
Skills you can list
SahiResume
Let AI write it. You pick the look.
No login · from ₹10 · real PDF preview before you pay
Build this resumeFrequently asked questions
Should a software engineer resume be one page?+
One page for under ~5 years of experience; two pages is fine for senior engineers if every line earns its place.
Should I include LeetCode or competitive programming ratings?+
Yes if they're strong and you're early in your career. Later, real project impact matters more.
Is a two-column resume bad for tech jobs?+
Not bad for human readers, but a single-column format is safer for applications that go through an ATS.