AI handles different titles for the same role by semantic mapping: SSE sits near Software Engineer, Associate Consultant near Developer, Module Lead near Senior Engineer when the surrounding skills match. Keyword search drops those people. Mapping is not a job offer. A recruiter still reads whether the person actually wrote code, led a module, or only inherited a grand designation.
Title inflation is not a data-quality bug. It is how Indian IT names jobs. Your screening has to speak both dialects.
Why Indian titles refuse to mean one thing
Product-company JDs say Software Engineer, SDE-2, Senior Backend. Service-firm resumes say Associate Consultant, Consultant, Analyst, SSE, “C2,” Module Lead. The work underneath can be the same Java service. Keyword search on the JD string never sees the consultant. That is not the candidate hiding. That is two naming systems sharing one labour market.
Inflation runs the other way too: Vice President of Engineering at a ten-person shop, “Lead” after eighteen months, “Architect” with no design evidence. If the model worships the title, you will rank theatre. If it only worships the JD string, you will empty the market. Semantic mapping plus must-have skill gates is the middle path. See keyword vs semantic matching and must-have vs good-to-have scoring.
| JD title | Common resume titles | Keyword risk | What mapping should do |
|---|---|---|---|
| Software Engineer | SSE, ASE, Developer, Programmer | Drop SSE / ASE | Same-role neighbourhood if skills align |
| Developer | Associate Consultant, Consultant, Analyst | Drop all three | Map if stack and bullets are development work |
| Senior Engineer | Module Lead, Tech Lead, SSE | Inconsistent hits | Map seniority loosely; verify scope on the call |
| Must-have: Java | Any title above, no Java evidence | May still hit the title | Cap at 55% regardless of designation |
How semantic mapping reads past the designation
The pipeline in how AI resume screening actually works extracts the title as one field, then scores the whole text. Embeddings put “Associate Consultant” near “Developer” when neighbouring tokens are Java, REST, Git, sprints. A Consultant whose bullets are pure PMO should not sit in the same neighbourhood just because the word Consultant appeared on last quarter’s successful hire.
Unless the client made a designation non-negotiable (“only SDE-2+”), title is a retrieval clue. Skills are the gate.
Four years of Spring Boot in project lines outweighs “Senior” in the header. Four years of “coordinated with vendors” does not become engineering because the title says Consultant.
A VP missing the must-have language still sits at a 55% cap. Designation cannot compensate for a missing core skill.
Semantic neighbourhood gets the consultant into the ranked list. It does not prove they can pass the client’s coding round. That is still a recruiter conversation — and why ranking cannot replace the call.
What still needs a human check after the title maps
Ask what they built, what they owned, and what the “lead” meant: people, architecture, or a billing grade. Ask whether the Associate Consultant track was delivery or sales support. Indian recruiters already do this. AI should not pretend it finished that job. It should only stop you from never calling the person because the JD said Developer and Infosys said Consultant.
Collapsed titles (SSE, Consultant, Analyst for the same work): let semantic match retrieve them, then gate on must-have skills. Inflated titles (Lead, Architect, VP without evidence): retrieve if you want, but do not let the header outrank empty bullets or a missing must-have.
Keep the JD and the market in the same language
When you intake a requirement, add the aliases your market actually uses. If the client says Software Engineer, note SSE / Developer / Associate Consultant as search cousins — not as seniority upgrades. That is a five-minute JD hygiene step that makes both Boolean and semantic search less stupid. The model can map. It cannot know that this particular client treats “Consultant” as a dirty word unless you tell it, or unless you override the score when they do.
Different titles for the same role are normal. Treating the title as the role is the mistake. Map for recall. Gate for skills. Call for the work.
Find the consultant who is actually a developer
TeamOB - SafalHires maps Indian title variants semantically, then still gates on must-have skills so a designation cannot hide a missing stack.
Free trial