Fix your résumé, one honest step at a time
Short, practical guides with real before-and-after rewrites, written for job seekers in India.
Writing your résumé
- How to put numbers on your résumé, even when you think you have noneA bullet with a number is read as proof. A bullet without one is read as a claim. Here’s how to find the numbers already in your work and write them in.
- How to write a résumé summary a recruiter actually readsThe top third of your résumé decides whether the rest gets read. A summary is the two or three lines that tell a recruiter who you are, what level you’re at, and what you’re aiming for.
- The ATS-friendly résumé format, without the mythsAn applicant tracking system turns your résumé into text and fields before a recruiter searches it. A format it reads cleanly means you show up in those searches.
- How to tailor your résumé to a job description in 15 minutesSending the same résumé everywhere is the slowest way to get a callback. Tailoring doesn’t mean rewriting: it means putting the evidence that job asks for where a recruiter will see it.
By role
- Software engineer résumé: what gets you shortlisted in IndiaTech recruiters see hundreds of résumés listing the same languages. What separates yours is evidence: what you built, how big it was, and what changed because of it.
- Data analyst résumé: show the decision, not just the dashboardEvery analyst résumé lists SQL, Excel and Power BI. The ones that get calls show what the analysis changed: a decision made, money saved, a process fixed.
- Product manager résumé: outcomes you owned, not features you shippedProduct hiring managers read for judgement and results. Your résumé should show problems you chose, decisions you made, and the metric that moved.
- Digital marketing résumé: lead with the numbers you movedMarketing is measured, so marketing résumés are judged on numbers. Recruiters want to see budgets, channels and results, not a list of platforms.