Writing a Resume That Survives the First 10 Seconds

Picture a recruiter on a Tuesday afternoon with 200 applications for one role. They're not reading resumes. They're scanning them: name, current role, company, years of experience, a few skills, maybe one or two bullet points. Then a quick decision: maybe, or no.

Before that, many companies run resumes through an applicant tracking system (ATS) that parses the document and filters or ranks it against the job description.

So a resume has two jobs. It has to be readable by software, and it has to make its point to a human in a few seconds. Most resumes fail at one or both. Neither takes design skills to fix.

For most people in India applying to corporate, tech, finance or consulting roles, this order works:

1. Name and contact details
2. Summary (2–3 lines, optional for freshers)
3. Skills
4. Work experience (or Projects first, for freshers)
5. Education
6. Certifications / achievements (only if relevant)

• Freshers and up to ~5 years' experience: one page.
• More experience: two pages at most. Older roles can shrink to one line each.

If it doesn't fit, the answer is usually to cut, not to shrink the font.

This is the part that gets read. Make it count.

Name, phone number, a professional email, city, and your LinkedIn URL. Add GitHub or a portfolio link if you're in tech or design and it has work worth seeing.

That's all. More on what to leave out below.

Skip "Seeking a challenging position in a reputed organisation to utilise my skills." Every recruiter has read it ten thousand times.

Write two or three lines that say who you are, what you're good at, and one proof point:

Backend engineer with 4 years of experience building payment and lending systems in Java and Spring Boot. Led the migration of a loan disbursal service to an event-driven design, cutting failed disbursals by about 40%.

A fresher version:

Final-year B.Tech (CSE) student with internship experience in full-stack development. Built and deployed a college event registration platform used by 1,500+ students.

Group them so they scan quickly:

Languages: Java, Python, SQL Frameworks: Spring Boot, React Tools: AWS (EC2, S3, Lambda), Docker, Git, Jenkins

Only list what you could discuss confidently in an interview. If you list Kubernetes, expect a Kubernetes question.

Most experience sections read like a job description: "Responsible for testing", "Worked on API development", "Involved in client meetings". They describe duties, not results.

A stronger pattern:

Action verb + what you did + the result (with a number if you honestly can)

You often have more than you think. Look for:

• Scale: users, transactions, records, team size, budget
• Time: hours saved, faster releases, reduced turnaround
• Quality: fewer bugs, fewer complaints, better test coverage
• Money: costs reduced, revenue influenced
• Scope: number of teams, regions or products

If you truly can't quantify, be specific instead: "Designed the database schema for the new invoicing module, later adopted by two other teams" is concrete without a number.

And never make numbers up. Interviewers ask "how did you measure that 40%?" more often than people expect.

• Current or most recent role: 4–6
• Previous roles: 2–4
• Roles from 8+ years ago: 1–2, or just the title and dates

Applicant tracking systems vary, but a few habits make your resume readable by almost all of them.

• Use a single-column layout. Two-column designs and text boxes often get scrambled when parsed.
• Use standard headings: "Work Experience", "Education", "Skills". Not "My Journey" or "Where I've Been".
• Avoid putting key information in images, icons, headers or footers. Some systems skip them entirely.
• Skip skill bars and star ratings. "Python ●●●●○" means nothing to software, and very little to humans.
• Submit as PDF unless the application asks for Word. Name the file sensibly: Priya_Sharma_Resume.pdf, not resume_final_v3_NEW.pdf.
• Mirror the job description's language where it's true for you. If the posting says "stakeholder management" and you've done it, use those words.

Those fancy Canva templates look great to you, but often fail the software screen and slow the human down.

Many Indian resume formats still include personal details that cost space, add nothing, and can invite bias.

Remove:

• Photograph (unless specifically requested, as in some customer-facing or international roles)
• Date of birth and age
• Marital status
• Father's or mother's name
• Religion, caste, nationality (unless relevant to work authorisation)
• Full home address (city is enough)
• "Declaration: I hereby declare that the above information is true…" at the bottom
• Hobbies like "listening to music" and "surfing the internet". Keep a hobby only if it's distinctive or relevant.
• 10th and 12th marks, once you have a few years of experience (freshers can keep them if they're strong or employers ask)

Every line you cut gives more room for what matters.

Sending the same resume to 100 jobs feels efficient. Usually it isn't.

For each job you actually want, spend ten minutes on:

1. Read the job description. Underline the three or four things they care about most.
2. Adjust your summary to lead with the experience that matches.
3. Reorder your skills so the ones they mention come first.
4. Move your most relevant bullets to the top of each role.

Twenty tailored applications usually get more interviews than a hundred generic ones.

Without work experience, your projects and internships are your experience. Put them right after the skills section.

For each project, include:

• What it does in one line
• Tech stack
• What you specifically built (especially in group projects)
• Proof: a live link, GitHub repo, number of users, or a result

Campus Marketplace | React, Node.js, MongoDB | [GitHub link]

• Built a buy-and-sell platform for students with listings, chat and search; 600+ registered users in the first semester
• Designed the search feature with filters and pagination, reducing average page load from 4s to under 1s

Two strong projects you can talk about in depth beat eight tutorial clones.

Before you hit submit:

• Fits on one page (or two, if you're experienced)
• Name, phone, email and LinkedIn are correct and clickable
• Current role and key skills are visible in the top third
• Every bullet starts with an action verb
• At least half your bullets show a result or scale
• No photo, DOB, marital status or declaration
• Single column, standard headings, saved as PDF
• Tailored to this job description
• Spell-checked, and read once aloud

A clean, simple template is fine. Pick one that is single-column with clear headings. Avoid heavily designed ones with graphics, columns and icons.

You need a strong base resume and small tailored changes for each role you seriously want: the summary, the order of skills, and which bullets come first.

Generally no. These come up in recruiter conversations and application forms. Some candidates add "Notice period: Immediate" when it's a real advantage, such as when they can join right away.

Briefly and honestly, in one line if needed: "Career break (2024–2025): caregiving / higher studies / health". Recruiters care much less about gaps than candidates fear, especially when you can show recent learning or work.

AI tools help with rewording and catching errors. Don't let them invent achievements or pad your skills. Every line on your resume is something an interviewer can ask you to explain, so make sure it's true and in words you'd actually use.