Before any round can score you, a person has to put you in the room. For a working engineer with 6 or more years, that means three things done well: a one-page résumé that shows outcomes and scope, a short list of people who can vouch for you, and a way to talk to recruiters without giving away your position. This chapter covers all three, with moves you can adapt. It does not claim any hit rate. The author has no data on how often a referral or a résumé style turns into an interview, and this chapter says so rather than invent a number.
What this chapter does and does not claim
Résumé advice is full of confident claims: "ATS rejects two-column résumés", "referrals are ten times likelier". The author could not confirm any of those from a source worth citing. So the chapter works another way. It gives you things you can check for yourself in a week, such as whether your résumé survives being copied into a plain-text box, and whether a message gets a reply.
A cheap test for any résumé: select all, paste into a plain text editor, and read it. If the order is scrambled, or the dates have drifted from the roles, a parser may do the same. This is a habit, not a claim about any one tool.
Step 1: a target list in three tiers
Do this in week 1 of the calendar. A list stops you applying to whatever turns up. It also lets you take the first screens at companies you care less about, as practice, and keep your best targets for later.
| Tier | What goes in it | How many | When you approach |
|---|---|---|---|
| 3: practice | Companies you would take but not love; fast processes | 10 to 15 | Weeks 2 to 4 |
| 2: want | Good role, good pay, a team you have heard well of | 10 to 15 | Weeks 3 to 6 |
| 1: dream | The few places you would change plans for | 3 to 6 | Weeks 5 to 7, when you have practised |
| Skip | Anywhere whose process you cannot fit around a job (for example, a company that insists on two full days in one week), or where the notice-period rules you saw in your own letter make the joining date impossible | As needed | Re-check if their process changes |
For each name, write one line: the team or product you would aim at, someone you know there (or one step away), and whether the role is in India, remote from India, or relocation. Global roles need a note on whether the employer hires in your country; ask the recruiter in the first call rather than guessing from the job post.
Step 2: a one-page résumé for 6+ years
The mistake at this level is to write the résumé as a list of technologies. A hiring manager reading a 7-year résumé wants to know the scale you worked at, what you owned, and what changed because of you. Stacks come last.
Shape
- Top line. Your title, years of experience, and the domain, in one sentence. Not an "objective".
- Experience. Three to five bullets per recent role, two to three for older ones. Each bullet: an action, a scope, a result. Put the number first where you can.
- Skills. One short line at the bottom. Only what you could be asked about for 30 minutes.
- Education and anything else. Two lines. Add open-source work or talks only if they back up a claim above.
- Length. One page. If a second page would hold real content, it can wait until a recruiter asks.
Before and after
The candidate below is invented. An example, not a real person.
Before
"Worked on the payments backend using Java, Spring, Kafka and MySQL. Responsible for APIs, bug fixes and production support."
After
"Led a team of 4 that moved the refund flow from a nightly batch to event-driven processing; refunds that took a day now take [x] minutes. Owned design, rollout and on-call for [n] downstream consumers."
Bracketed items are for you to fill with your own numbers. If you do not know the figure, give the order of magnitude and be ready to say it is an estimate. Do not round up. A follow-up question will find it.
Try this test on each bullet: "So what? Who benefited, by how much, because of what I did?" If a bullet cannot answer, cut it or rewrite it. Your words and numbers, not a template's.
Do not copy a template wholesale from a paid course or another person's résumé. Use the shape above and make the content yours.