Most Indian job seekers either apply to everything regardless of fit, or eliminate themselves from perfectly good roles because they feel they do not meet 100% of the requirements. Both strategies cost you good opportunities. This guide teaches you how to read a job description critically: separating real requirements from aspirational padding: so you can apply strategically and tailor effectively.
Most JDs at Indian companies follow a predictable structure:
- Job title and team: Often vague ('Software Engineer II') or overly specific ('Senior Full Stack Engineer - Payments Infra'). The actual role may be different from what the title implies: always read the responsibilities.
- About the company: Marketing paragraph. Read quickly for culture signals, not facts.
- Responsibilities: What you will actually do. This is the most important section. Read carefully. If more than 70% of the responsibilities describe what you already do or have done, you are a strong fit.
- Requirements (Must-have): Experience years, specific skills, education. Treat 'X years of experience' as a signal, not a hard cutoff: see below.
- Requirements (Nice-to-have / Preferred): Skills they want but will not eliminate you for lacking. These are your growth opportunities if you get the role.
- About the team / culture: Often the most honest section because it is usually written by an engineer, not HR. Look for clues about pace, cross-functional work, autonomy.
The most misunderstood element of Indian JDs is the years-of-experience requirement.
The ruleApply if you meet at least 70% of the stated requirements and are within 1–2 years of the experience requirement in either direction.
Why the cutoff is often aspirational: JDs are frequently written by recruiters with guidance from hiring managers who want the best possible candidate. '4–6 years required' often means '3+ years preferred' in practice. Hiring decisions are made by humans who can see potential and trajectory, not algorithms that reject below a strict threshold.
Exceptions where the cutoff is real: • Specific certifications or licences (CPA, bar exam, specific government clearances) • Band-level budget constraints at large companies (if the approved headcount is for a 'Band 6' role, a Band 4 candidate may not proceed regardless of skill) • Technical skills that cannot be demonstrated without a minimum time (enterprise software implementations that take years to learn)
Rule of thumbIf a fresh graduate sees a '3–5 years required' role and has exceptional projects and internship experience, they should apply. If a 10-year engineer sees a '5–8 years required' role, they should apply. The experience range is a signal about seniority, not a legal requirement.
These signals in JDs warrant extra scrutiny:
'Rockstar/Ninja/Guru Developer': Buzzwords that often signal a culture of overwork and ego-driven hiring rather than collaborative engineering. Rare exceptions: some Indian startup founders use these terms without the negative connotations: investigate the specific company.
'Unlimited PTO': Almost always means 'we have no PTO culture and people do not take leave.' Ask in the interview: 'What is the average time off people actually take per year?' Concrete answer = real policy. Vague answer = red flag.
Very long requirements lists (20+ bullet points): Often signals a role that has been open a long time or that has unclear requirements from the hiring manager. Proceed with caution: you may be walking into a role without clear success criteria.
'Startup culture, move fast': This means something specific to the team. Ask in the interview: 'What does moving fast actually look like for this team?' If the answer involves weekends and no planning processes, calibrate accordingly.
Vague compensationIn India, more JDs are now including compensation ranges due to candidate demand for transparency. If a JD says 'competitive compensation' without a range, ask the recruiter directly in the first call: 'Can you share the compensation range for this role?' This is now a normal and accepted question.
Tailoring does not mean rewriting your resume from scratch. It means:
Step 1: Identify the top 5 requirements in the JD. These are usually the first 3–5 bullets in the 'Requirements' section and the first 3–5 bullets in the 'Responsibilities' section.
Step 2: Verify your resume addresses each of these top 5. If any are missing, add them: using the same language the JD uses where your experience genuinely matches. This helps your resume pass ATS (Applicant Tracking System) screening.
Step 3: Move your most relevant experience to the top. If the JD emphasises payments infrastructure and you have done that in one of three jobs, lead with that job's description: even if it was not your most recent.
Step 4: Write a targeted cover letter (or LinkedIn InMail) only if you have a specific reason this role matches you that is not obvious from the resume alone. For most Indian applications, a well-tailored resume is sufficient.