CAREER INSIGHT · READING LISTINGS
Read the Job Description, Not the Title
Why the same words in a title can mean very different work — and how to check before you apply.
A job title is a label a company files a role under. What the person actually does is in the responsibilities section. When the two disagree, the description is the job.
You read the title first. Sometimes it is the only thing you read before you apply or move on. But the title is the weakest part of a job post. It is the label the company files the role under. The work itself sits lower down, in the responsibilities. The two often do not match.
Why titles stop matching the work
It is rarely sloppiness, and almost never a sign of a bad employer. Big companies run grade ladders. Analyst I, II, III. Engineer I. Specialist 2. C09, C10. Every post has to wear one of those tags, whether or not it fits. The recruiting system often makes you pick a title from a fixed menu. Someone copies an old requisition and forgets to change the header. A role keeps a name from a version of itself that no longer exists. And every company names things its own way, so identical work gets a different title depending on who typed it.
Four ways it goes wrong
Composites from real posts. In each one the title says one thing and the responsibilities say another. None of these is rare.
Titled
Physical Design Engineer
Stated experience: 1–2 years of digital design
- RTL design and microarchitecture in Verilog, VHDL or SystemVerilog
- Functional coverage and design verification support
- Working with the physical-design team, not running the physical-design flow
This is an RTL and verification job that talks to the physical-design team. "Physical design" shows up in the title and once in the body. Someone whose skill is place-and-route and timing closure would be doing different work here.
Titled
Software Engineer I
Stated experience: 1 year
- Plan and run functional, integration and system testing
- Automate web and mobile test suites with Selenium, Appium, Cypress or Playwright
- Wire the automated tests into CI/CD pipelines and chase down failures
This is test automation. Verification and validation. It is real software work, but it is not feature development. Walk into a system-design interview for this one and you have prepared for the wrong role.
Titled
Manufacturing Analyst
Stated experience: 0–2 years
- Facility administration and coordination for the engineering and maintenance teams
- Purchasing support and vendor follow-up
- Inventory monitoring on the shop floor
There is barely any analysis here, and the "manufacturing" part is facility admin, not production data. The post says as much in its own words. The title is the department. The responsibilities are the job.
Titled
Associate Systems Engineer
Job family: Digital
- Backend and web application development in C#, .NET and Angular
- Database work and cloud services on AWS
- Customising a product-lifecycle-management platform
Here "systems engineer" means web and cloud development. C#, .NET, Angular. Not avionics, not requirements engineering, not aircraft systems. One version of the post spells that out.
Same story every time. The title is a filing category. A grade, a department, a job family. The responsibilities are the work. When you decide whether to apply, what to prepare, or whether to accept, go by the work.
Grade labels are not seniority
Level labels that turn up in titles
Each one marks an internal band. None of them reliably tells you how senior the role is.
- Analyst I / II / III
- A pay band. "Analyst III" is often an entry role at nought to one year, not a step above "Analyst II". Read the stated experience.
- Engineer I, Associate Engineer
- An entry grade. It does not mean you would be overqualified. The responsibilities and the required years decide that.
- Specialist 2, Associate 2, C09, C10
- Internal job grades, common in banks and big firms. They carry no fixed meaning between companies.
- Manager, Assistant Manager, Lead
- Sometimes a real management job. Often, in consulting and delivery-centre roles, a title sitting on a 0–2 year job with no reports.
A seniority word in the title means nothing until you check the experience and the responsibilities.
Read a post in this order
Body first, title last. That way the label does not decide for you.
- The responsibilities, the "what you will do" section. This is the job.
- The tools and skills. Do they belong to the role the title implies?
- The experience and education. Does the range fit any seniority word in the title?
- The team, function or job-family field. Many posts have one, and it often says more than the title.
- The title, last. Check it against the four things above.
If the first four do not agree with the title, go with the first four.
- 01 Do the responsibilities describe the work the title implies?
- 02 Do the listed tools belong to that kind of role, or a different one?
- 03 Does the experience range fit words like "senior", "lead" or "manager"?
- 04 Is there a function or job-family field, and does it match the title?
- 05 Does the post itself say something like "despite the title..."?
- 06 If the title and the body disagree, which one would you rather do?
Two or more of these raising a flag means the title is not safe to decide from. Read the body.
The same post, judged two ways.
| 👤 Deciding from the title | 🏢 Deciding from the description |
|---|---|
| "Physical Design Engineer" — I do RTL, not layout, so I will skip it | The responsibilities are RTL and verification. Good fit. Apply. |
| "Software Engineer I" — a coding role, I will prep system design | It is test automation. Prep examples of building test frameworks and CI pipelines. |
| "Manager" — I have no reports, I am not qualified | It asks for 0–2 years and lists IC tasks. I am in range. Apply. |
| "Systems Engineer" at an aircraft company — must be avionics | Job family is Digital, the stack is C# and Angular. It is a web software role. |
Before you apply
- You read the responsibilities, not only the title and the one-line summary.
- The tools and skills match the work you are expecting.
- The stated experience is in your range, whatever seniority word is in the title.
- You checked the function or job-family field, if the post has one.
- If the title and body disagree, you are applying for the work, not the label.
Myth: The title tells me what the job is.
Reality: The title tells me what box the company put the role in. The responsibilities tell me the job.
Myth: A title that does not match the description is a mistake to steer clear of.
Reality: It is usually a grade ladder or a copied post. Read the body and judge the work.
Myth: "Engineer I" or "Analyst III" makes the seniority obvious.
Reality: They are level tags. "III" can be entry-level. "I" can expect independence. The years and the tasks tell you.
Stop deciding from: the title in the search results.
Start deciding from: the responsibilities, the tools, and the stated experience. Read the title last, to check it.
A title is how a company sorts its roles. It is not a promise about your day.
Frequently asked questions
Title and description disagree. Which do I trust?
The description. It is written for the real role. The title is often stuck with a grade or a system label. Decide on the work.
Does a title-versus-description mismatch mean I should distrust the company?
No, not on its own. It is common at large, legitimate employers. Judge a suspicious post by other things: vague company details, payment requests, contact that moves off-platform.
What if there is no real description, just a title and a line?
Treat it as thin. Find the same role on the company careers site, which usually carries the full text, before you decide.
Continue your research
Related Career Insights and the sections of HireSetu where this article applies.
Sections on HireSetu
- Companies & hiring insights — See how individual employers name the same kind of work.
- Discover jobs by industry — Apply this article to the live job market by industry.
- Career Insights library — Every article explaining how hiring decisions actually work.