Before asking for a raise, compare your work with responsibilities other suitable employers expect someone to own.
Use the comparison to identify valuable work and evidence—not to threaten your manager with the highest salary screenshot you can find. Your current employer may or may not have room for the same responsibilities.
A more useful compensation conversation connects your development with a concrete proposal. First understand the work, then ask whether an internal path exists and what evidence would support a change in role or pay.
Compare roles that match your actual constraints
Select several openings that fit your location, experience, and work preferences. Read the responsibilities before treating the pay as comparable.
Check:
- Scope: Is the role asking for SSO troubleshooting, lifecycle automation, access reviews, or ownership of a directory service?
- Seniority: Does it require leadership or expertise you haven't demonstrated?
- Conditions: Are travel, schedule, and location expectations compatible with your needs?
- Evidence: What examples would show you could handle the central work?
A high-paying role with extensive travel or substantially different responsibility isn't a clean comparison with your current position.
The exercise can still reveal useful development targets when salary information is incomplete. Focus on the recurring problems you could become capable of owning rather than assuming a posted range is an entitlement attached to a tool name.
Match those responsibilities to your evidence
For each repeated requirement, identify something you've actually done.
Maybe you've handled approved group changes, helped investigate authentication failures, or documented an onboarding process. Separate independent ownership from work you supported under someone else's direction.
Then identify the gaps. You might have strong troubleshooting experience but no example of building an application integration from the beginning.
This is a more productive finding than deciding that you need a random certification because another candidate has one.
Ask whether the current employer has room for that work
A manager may value your development but have no relevant responsibility to assign. Another team may own the identity systems, or the organization may outsource the work entirely.
Ask about the actual opportunity: a project, a service responsibility, a recurring problem, or an approved partnership with the identity team.
Don't assume that studying a skill automatically creates an internal promotion path. You need a role the organization needs, authority to do the work, and a way to evaluate the contribution.
If those conditions aren't available, external applications may deserve a larger part of your plan.
Bring a proposal rather than a vague ambition
A useful conversation could sound like this: “I'd like to develop responsibility for application-access troubleshooting. These are the tasks I already handle, and this is the gap I want to close. Is there an approved project where I could build that capability?”
Keep the proposal small enough to evaluate. Name the expected result, the support you'll need, and when you would review progress.
Discuss compensation and title expectations directly, but don't assume an informal development opportunity is a guaranteed raise. Ask what process governs those decisions.
Keep market evidence and loyalty separate
Researching other roles does not require treating your current employer as an enemy.
You can appreciate the job and still evaluate whether it supports your next move. You can also decide that its flexibility or working conditions outweigh a larger number elsewhere.
Use the difference between internal value and market value to avoid confusing being indispensable in one environment with having portable evidence of capability.
The goal is an informed decision, not winning an argument about what you're worth.
Leave with a concrete next step
At the end of the discussion, you should know whether to pursue an internal project, develop a missing skill independently, apply elsewhere, or reconsider the target.
Write down the decision and the next review point. Otherwise, a positive conversation can become months of waiting with no change in responsibility.
The Six-Figure IAM Career Playbook helps organize the role-selection, gap-mapping, lab, and application work behind that decision. The $9 guide is a plan for becoming a stronger candidate, not a guarantee of a raise.
Start with the work employers need. Then decide where you can build and demonstrate your ability to do it.