Genuine requirements versus the wishlist
A posting asking for React, TypeScript, Node, GraphQL, Kubernetes, Kafka and Terraform inside three years of experience is not describing one person. It is a team's skill list, assembled by copying an older posting and adding whatever came up last sprint. Treating all fifteen bullets as equally binding is how strong candidates screen themselves out before anyone reads them.
Frequency weighting sorts that out. A skill named in the title, repeated in the summary and again in two responsibilities is what the role is measured on. A tool mentioned once, near the bottom, under “Good to have”, is padding. If SQL appears five times and Kafka once, missing Kafka costs you almost nothing.
So read the ranked list as a shortlist rather than a checklist. Six matches on the heavily weighted terms beat ten thin matches spread across the whole posting, because the recruiter screening you is scanning for the same handful of words the writer could not stop repeating.
What the wording gives away
Seniority leaks through verbs more reliably than through titles. Indian startups inflate titles freely, and a Lead at two years' experience is common, but a posting that says you will support the roadmap under the guidance of the manager has described a mid-level seat regardless of what the heading claims.
Warning-sign phrases are matched against fixed patterns. “Wear many hats” usually means the scope has not been decided yet. “Fast-paced” often stands in for no process. “Rockstar” or “ninja” signals hiring by instinct rather than a rubric. “Salary as per industry standards” means there is no published band and you will be asked for your number first.
None of these is a reason to skip an application. They are a reason to arrive with questions: what the last person in the seat actually spent their week on, and where you sit in a band advertised as ₹6-15 lakh, which is wide enough to mean the number is set by negotiation rather than by level.
Turning the output into an application
The weighted terms are also the vocabulary your resume should use. Indian hiring runs heavily through applicant tracking systems, and most of them match literal strings. B.Tech and Bachelor of Technology, Power BI and PowerBI, JS and JavaScript are different tokens to a parser that does no stemming and no synonym lookup.
Mirror the posting's exact spelling for anything you genuinely have, and put it in the bullet describing the work rather than in a keyword block at the end. A skills list stuffed with terms that appear nowhere in your experience reads badly to the human who opens the file once the filter has passed it along.
The same ranking is the outline for a cover letter. Three paragraphs, each answering one top-weighted requirement with something you shipped and a number attached to it, beat a page of adjectives, and take about fifteen minutes once you know which three requirements carry the weight.