Summary and contact
The summary is three or four lines aimed at one role family — for example backend engineer in Bengaluru, not “seeking challenging opportunities.” Name the stack, years, and the kind of problem you like to own.
Contact should be boring and complete: a phone that you answer, an email you check, and the city you can work from. If the role is hybrid, say so in one clause. Do not hide location in a footer.
Experience and projects
Lead each role with a title, employer, city, and dates. Bullets should start with a verb and end with a result: users, latency, revenue, quality, or time saved. “Worked on APIs” is weaker than “Cut checkout API p95 from 800ms to 220ms.”
Projects belong here when they prove the same skills as the job. Campus or side work is fine if you can talk through architecture and trade-offs. Drop projects that only repeat a course title.
Skills, education, and extras
Group skills so a parser and a human both see them: languages, frameworks, cloud, and domain. List only what you can use in a screen. Inflated skill clouds are easy to test in the first round.
Education needs degree, institute, and year. Certifications help when they map to the JD. Interests and soft-skill adjectives rarely change a shortlist — save space for one more outcome instead.
After you write: JobBucket apps
When the draft is honest and parse-safe, upload it in the free JobBucket Android or iOS apps. Parsing turns the file into a profile you reuse; the AI resume score highlights gaps before you apply to company jobs on the portal.
You do not need a second designed file for the ATS. The same PDF is what employers parse when you apply — they start free and run paid plans from ₹1,499/mo.