Choosing the occupational classification
IAM roles are commonly classified as information security analysts, software developers, or computer network architects depending on where the work actually sits. An engineer building custom provisioning connectors and authorisation services is doing software development. An engineer designing federation topology across business units is closer to network or systems architecture. Someone running certification campaigns and audit response sits squarely in security analysis.
The classification should follow the duties as written. A mismatch between the two is the most common cause of a determination that neither side expected.
How the four wage levels work
Level one reflects entry-level work performed under close supervision with limited judgement. Level two indicates moderate experience with routine independent work. Level three covers experienced practitioners who exercise judgement and may direct others. Level four is reserved for those who plan and lead, resolve novel problems and set technical direction.
Levels are assigned by comparing the stated requirements — experience, education, supervision, special skills — against the classification's baseline. Adding requirements raises the level. This is why a petition claiming architecture ownership at level one is internally inconsistent: the duties and the wage tell different stories.
Geography and the source of the number
Determinations are geographic. The same identity architect role can carry substantially different wages in a coastal metropolitan area versus a mid-sized inland market, because the surveys reflect local labour costs. Remote roles are assessed against the place of employment, which for distributed teams means the location where the work is actually performed.
Employers may also rely on a legitimate independent wage survey where one is available and methodologically sound. Either way, the determination sets a floor, not a target — competitive security offers routinely exceed it.
Practical advice for candidates
Ask which occupational classification and wage level a role was filed under. The answer tells you how the employer characterised the seniority of the work, and a level that sits below the responsibilities described in the interview is worth discussing openly.
For scarce specialisations — privileged access at scale, identity governance in regulated environments, machine identity — the market rate usually sits comfortably above the determined floor. Knowing both numbers puts a candidate in a much stronger negotiating position.
Key takeaways
- Classification should follow the actual duties: development, architecture or security analysis.
- Four wage levels map to supervision, judgement and scope — keep them consistent with the role description.
- Determinations are local; remote work is assessed at the place of employment.
- The determination is a floor, and specialised IAM skills usually clear it comfortably.
Hiring or being hired in IAM?
TagWin Recruiting places Okta, Ping, SailPoint and CyberArk specialists with enterprises that cannot afford an identity gap.
Start an intake