How to read a tech job description without wasting your week

The 'requirements' block is typically assembled by merging the current team's skills with the hiring manager's aspirations. Research on hiring behaviour has consistently found that candidates who meet a majority — not all — of listed criteria are routinely interviewed and hired, while candidates who self-reject at a missing bullet never enter the pipeline at all.

The practical rule: separate the list into capabilities that are load-bearing for the day-to-day work and capabilities that are decoration. A backend role listing 'Go, Postgres, Kubernetes, Terraform, gRPC, Kafka, GraphQL, React' is not describing one person's daily work; it is describing the team's stack. Identify the two or three that appear in the responsibilities section as well, and treat only those as real.

Years of experience are the softest requirement of all. They function as a rough proxy for autonomy. If your work demonstrates that you can take an ambiguous problem to a shipped outcome without supervision, the number matters far less than the description implies.

Ignore the title and read the verbs. 'Implement', 'assist', 'contribute to' describe a role where scope is handed to you. 'Own', 'define', 'drive', 'partner with' describe a role where you are expected to generate the scope yourself. A 'Senior Engineer' posting full of implementation verbs is a mid-level role with an inflated title; a 'Software Engineer' posting full of ownership verbs is a senior role that will pay below its actual scope.

This matters for two reasons. It tells you whether the interview will test execution or judgement, and it tells you whether the compensation on offer matches the work being described.

• Implement / assist / support → scope is given to you.
• Own / define / drive / influence → you generate the scope.
• Mentor / set direction / partner cross-functionally → staff-level expectations.

Very few Indian listings state a range, so you are reading proxies. 'Competitive compensation' means the number is below what the market pays for that title, or the employer wants anchoring control. 'ESOPs' quoted as a large headline figure should be read alongside the strike price, vesting schedule and last round valuation — none of which will be in the listing, and all of which you can ask about in the first call.

'CTC' is not salary. Deduct the employer's provident fund contribution, gratuity provisioning, notional insurance value and any variable component that is contingent on company performance to get the number that actually reaches your bank account. A 20 lakh CTC and a 20 lakh cash salary are very different offers.

When a range genuinely is absent, ask for it in the first conversation rather than at the offer stage. It is a normal question, and an employer that refuses to answer it at any point in the process is telling you something useful.

Some patterns are reliably predictive of a bad experience, and they are visible before you apply.

A listing that emphasises 'fast-paced' three times, mentions 'wearing many hats', and describes a role covering frontend, backend, infrastructure and customer support is describing understaffing, not opportunity. A listing that requires a multi-day unpaid take-home before any human conversation is treating candidate time as free. A listing with no company name, no website and a generic mail domain is either an agency fishing for a database or a scam.

The clearest single signal in the Indian market is any request for payment, documents beyond a resume, or original certificates before an offer letter exists. That is not a hiring process.

• No company name or a free-mail contact address.
• Payment, deposit or 'training fee' requested at any stage.
• Multi-day take-home before any human conversation.
• Role scope spanning four functions at a junior title.

Once decoded, the listing writes your application for you. Take the two or three load-bearing capabilities, and reorder your resume so that the projects demonstrating them appear first. Reuse the employer's own vocabulary — if they say 'distributed systems' and you say 'scalable backend', a keyword filter and a hurried reviewer will both miss the match.

Then write down the two questions the description does not answer — usually team size and what the first ninety days look like — and ask them in the screening call. Candidates who ask specific, informed questions are consistently rated higher, and the answers tell you whether to continue.