An illustration showing the recruitment and candidate evaluation process. On the left, a woman uses a magnifying glass to examine candidate profiles. In the center, a highlighted profile card displays a woman's photo with a green checkmark and five gold stars, indicating a top candidate. To the right, two colleagues sit at a desk reviewing candidates on a laptop. Additional candidate profiles are visible in the background. Colorful decorative dots and lines surround the scene, emphasizing the active hiring workflow.

When the Hiring Manager Wants to Change the Level

Recruiter talking points to help hiring managers clarify job level and avoid mid-search hiring changes.

Many hiring searches go sideways because the real business need was never fully clarified upfront.

This guide gives recruiters practical talking points to align with hiring managers on the actual scope, impact, and expectations of the role before launching a search, since mid-process level changes can lead to candidate frustration, longer hiring timelines, and even unnecessary churn.

1) Start with the business need 

Ask:

  • What problem(s) will this role solve?
  • What does success look like in the first 6–12 months?

👉 Goal: Align on outcomes before discussing titles or job level.

2) Use the PSHE framework to clarify scope

A four-step process framework diagram displayed horizontally with colored boxes. From left to right: a blue box labeled "P - Problem," a purple box labeled "S - Solution," a green box labeled "H - How," and a peach box labeled "E - Execute." This visual represents a structured problem-solving methodology moving from identifying the problem through to implementation.

Clarify:

  • Who defines the problem?
  • Who proposes the solution?
  • Who figures out the “how” or approach?
  • Who executes?

👉 Goal: Understand the scope of this role better. Here is more on the PSHE framework and example talking points to use.

3) Pressure test the level

Ask:

  • Impact — Will this role affect the team, department, and/or organization?
  • Responsibility — Are they mainly building something new or improving existing work?
  • Work latitude — What decisions will they make independently? How much guidance do they need? 
  • Knowledge — Is generalized knowledge sufficient, or does the role require deep technical or specialized expertise?
  • Interactions — How much time will they spend interacting with executives, and in what capacity (updating vs. influencing)?

👉 Goal: Turn fuzzy expectations into concrete ones that align with business needs.

4) Clarify tradeoffs & commit before launch

Say: “If we move this role up a level, here’s the impact:”

  • Higher ongoing cost — May limit other hires or department budgets
  • Smaller candidate pool – Likely leads to a longer recruitment process
  • Higher expectations – Candidates will have higher post-hire expectations and require clear communication about scope and growth to avoid misalignment.

Ask the hiring manager to commit to the level before opening the role. Avoid mid-process changes unless truly necessary.

👉 Goal: Speeds up hiring and shows the manager this isn’t a “free” upgrade. 

The goal isn’t to hire the most senior person or highest title possible — it’s to hire the right level for the problems the business needs solved.

Related Insights