Why job titles lie: how to truly assess candidates

Arthur Balabrega avatar
Arthur Balabrega
Cover for Why job titles lie: how to truly assess candidates

Two candidates on your screen. Same job title: “Project Manager”. Same years of experience: 6 years. Same LinkedIn skills: Agile, Scrum, Stakeholder management.

LinkedIn says: identical. Your gut says: check the employers. You google the company names. Five minutes later you know the truth: completely different profiles.

One works at an IT scale-up. The other at a construction company. For your IT vacancy, candidate A is relevant. Candidate B is not.

How often does this happen to you? Every week. Every search. You filter on job title and location, but the real question remains: which employers tell me whether someone actually fits?


Why job titles are misleading

A job title without employer context is meaningless. Consider these examples:

“Project Manager” can mean:

  • IT projects at a SaaS scale-up (agile sprints, EUR 2M budget, multi-stakeholder)
  • Construction projects at a contractor (waterfall methodology, EUR 50M infrastructure)
  • Marketing campaigns at an e-commerce company (2-week sprints, cross-functional)
  • Manufacturing projects (lean, six sigma, supply chain optimization)

“Sales Manager” can mean:

  • New business at a B2B SaaS company (consultative selling, 9-month sales cycle, EUR 200K+ enterprise deals)
  • Retail sales at a consumer electronics chain (transactional, high volume, daily targets)
  • Channel partnerships at a distributor (relationship management, contract negotiations, annual agreements)

“Data Engineer” can mean:

  • Real-time data pipelines at a fintech (Kafka, Spark, millions of transactions per second)
  • BI reporting at an insurance company (SQL, SSIS, monthly batch processes)
  • Machine learning infrastructure at an AI startup (Python, Kubernetes, GPU clusters)

“Product Owner” can mean:

  • Product discovery at a scale-up (user research, prototyping, 0-to-1)
  • Backlog management at a corporate (Jira, stakeholder alignment, incremental improvements)
  • Technical product ownership at a platform company (API design, developer experience)

Same titles. Completely different jobs. Different methodologies, different stakeholders, different complexity, different pace.

The title tells you what someone does. The employer tells you how and in what context.

Without that context, you filter blindly. You add candidate B to your shortlist because the title checks out. Then it turns out in the interview that the experience doesn’t align. You’ve lost an hour. The candidate has lost an hour. The hiring manager asks: why was this candidate presented?


Case study: Project Manager A vs Project Manager B

Suppose you’re looking for an IT Project Manager for a SaaS scale-up. Agile workflow, multi-stakeholder environment, fast decision-making.

You get two candidates:

Candidate A:

  • Role: Project Manager
  • Employer: CloudBase (scale-up, 120 employees)
  • Context: SaaS platform, agile, 2-week sprints, EUR 2M budget, multi-stakeholder (product, engineering, sales), 18-24 month projects

Candidate B:

  • Role: Project Manager
  • Employer: DeltaMech (construction company, 800 employees)
  • Context: infrastructure projects, waterfall methodology, 3-5 year duration, EUR 50M budget, stakeholders (contractors, municipality, regulators)

Same title. Same years of experience. But:

  • Candidate A works in short iterations. Candidate B in long planning phases.
  • Candidate A switches daily between product and sales. Candidate B works with contractors and government bodies.
  • Candidate A works in an organization where decisions are made in a week. At candidate B’s company, approvals take months.

For your IT scale-up vacancy, candidate A is relevant. Candidate B is not. Not because B is a bad Project Manager, but because the context doesn’t match.

This distinction is invisible when you only look at titles. It becomes obvious when you look at employers.


Beyond the title: a framework for context-based screening

If job titles don’t tell you enough, what does? Employer context. Here’s a practical framework you can apply immediately, regardless of which tools you use.

Step 1: Analyze the employer type

For every candidate, look beyond the title to the company behind it. Ask yourself:

  • Sector and industry - What space does the company operate in?
  • Company size and stage - Is it a startup, scale-up, SME, or enterprise?
  • Business model - B2B or B2C? SaaS, services, manufacturing?
  • Geographic scope - Local, national, or international?

You can usually find this basic information on the LinkedIn company page or the “About” section of the company website.

Step 2: Understand the work environment

Two companies in the same industry can operate in completely different ways. Pay attention to:

  • Decision speed - How quickly are decisions made? At a startup, you decide in a standup. At a multinational, you need three layers of approval.
  • Level of autonomy - Does someone have end-to-end ownership or do they execute a subtask within a larger structure?
  • Team structure - Does someone work in a small cross-functional team or in a large specialized department?
  • Methodology - Agile, waterfall, lean? This shapes how someone is used to working and delivering.

Step 3: Evaluate the career path

A single employer doesn’t tell the full story. Look at the pattern across someone’s career:

  • Has this person consistently worked at the same type of company, or have they varied?
  • Are there logical steps in complexity, scale, or responsibility?
  • Which transitions are relevant for your specific vacancy?

A candidate who moved from a corporate to a scale-up has demonstrated adaptability. A candidate who has spent 15 years at similar companies brings deep domain expertise. Neither is better or worse. It depends on what your vacancy requires.

Step 4: Validate during the intake conversation

Ask your client or hiring manager: “Name three companies that you know operate similarly to yours.” Those companies become your reference frame. Candidates who have worked there bring relevant context. This makes your search more targeted than any Boolean string.

This single question often reveals more about what the hiring manager actually needs than a 30-minute intake about hard skills and years of experience.

Step 5: Use tools for rapid analysis

Manually checking every employer takes time. In a search of 200 profiles, you easily have 150+ unique employers. If you google each one for 5 minutes, you’re spending hours before you’ve even started screening.

AI tools like SourceLens can automate employer analysis: sector, size, business model, way of working. In seconds rather than minutes per employer. This makes context-based screening feasible even for larger searches. Curious about what that costs? Check the pricing.


What factors make employer context valuable?

When analyzing employer context, several categories together paint a complete picture:

About the company itself:

  • Sector and industry
  • Company size (startup, SME, corporate)
  • Revenue and growth stage
  • Geographic focus (local, EU, global)

About the market the company operates in:

  • B2B or B2C
  • Customer segment (enterprise, mid-market, SMB)
  • Product or service type (SaaS, on-premise, physical product, services)

About the way of working:

  • Decision speed and hierarchy
  • Level of ownership and autonomy
  • Culture and work style

For commercial roles specifically:

  • Sales model (inside sales, field sales, consultative, channel)
  • Deal size (transactional vs. enterprise)
  • Sales cycle length (weeks vs. months)

When you include these factors in your assessment, you stop looking only at what someone did and start understanding the environment in which they did it. That environment determines whether experience is transferable.


The traditional search workflow:

  1. Boolean search on LinkedIn for job title + location
  2. Get 800 profiles back
  3. Open profile, check title, add to shortlist
  4. 3-4 hours later: 80 candidates on your shortlist
  5. After calls and interviews: 40% turn out not to be relevant

The context-based workflow:

  1. Boolean search on LinkedIn for job title + location
  2. For each candidate, review employer context (manually or with tooling)
  3. Assess whether the employer type matches the vacancy
  4. Shortlist is smaller but more relevant
  5. After calls and interviews: significantly higher hit rate

The difference isn’t better candidates. It’s better selection. You’re no longer filtering on titles — you’re filtering on context.

The candidate with the perfect title at the wrong type of company doesn’t fit. The candidate with a slightly different title at the right type of company often does.


Why this matters for every type of recruiter

As a corporate recruiter, you can’t know the market for every role you fill. Employer context helps you quickly understand which companies produce comparable profiles, without needing years of sector-specific knowledge.

As an agency recruiter, you build that knowledge over years. But when a new client comes in from an unfamiliar industry, employer context gives you an immediate reference frame. It compresses months of market learning into minutes.

As a solo recruiter, you regularly step into sectors where you have no network yet. Context-based screening helps you quickly understand which employers are relevant, without weeks of market research. It’s the difference between confidently presenting candidates in week one versus spending the first month learning the landscape.


The hidden cost of ignoring context

When you screen on titles alone, the cost is hidden but real:

  • Wasted interviews - 40% of your shortlist turns out to be irrelevant after the first conversation
  • Damaged credibility - Hiring managers lose trust when you present candidates whose experience doesn’t translate
  • Missed candidates - The best match for your role might have a different title but the perfect employer background
  • Longer time-to-fill - You cycle through more candidates before finding the right one

Context-based screening doesn’t just save time. It fundamentally changes the quality of your output. Your shortlists become more defensible. Your hit rate goes up. Your conversations with hiring managers become more substantive.


How to start screening on context today

You don’t need to overhaul your entire process. Start small:

  1. Next search: Before shortlisting, check the top 3 employers on each candidate’s profile. Does the company type match what your client needs?
  2. Next intake: Ask the hiring manager to name comparable companies. Use those as your benchmark.
  3. Next shortlist review: For each candidate, write one sentence about their employer context. Present that alongside the CV. Watch how the conversation changes.
  4. Scale up: Once you see the value, look into tools that automate employer analysis, whether that’s a dedicated solution or your own research workflow. Read more about effective LinkedIn sourcing strategies to combine with this approach.

The shift from title-based to context-based screening is not a technology change. It’s a mindset change. The tools make it faster, but the insight that where someone worked matters as much as what they did is something you can apply right now.


Conclusion: look beyond the title

Job titles are labels. They categorize. But they don’t tell the story.

The employer tells the story. The sector, the organization type, the way of working, the complexity. That’s what determines whether someone’s experience aligns with your vacancy.

The next time you run a LinkedIn search and get 800 “Project Managers” back, ask yourself: at what type of company did these people work? That answer tells you more than the title ever can.

Want the full research? Download our free whitepaper on why job titles mislead and what works better.

Context determines relevance. Not the title.

Share this article

Source smarter with SourceLens

AI analyses employers behind every LinkedIn profile. Go from 500 results to 50 real matches.

14 days free, no credit card required