Identity and access management hiring across Sydney and Australia, on contract and permanent, from senior engineers through to the principal architects who set the target state.
Identity and access management recruitment.
The demand underneath it has changed shape. Identity used to sit inside security and infrastructure. It’s now the thing standing between an enterprise and every AI initiative it wants to run.
Where the demand is coming from
Most of the briefs we take in this space aren’t “we need more IAM people”. They’re one of these four, and they’re usually urgent.
The AI dependency
Every agent, every integration and every automated workflow needs an identity of its own, with a credential, a scope and an owner. Enterprises are finding that their identity platform was built for humans and is now being asked to carry machine identities in volumes it was never sized for.
The authentication rebuild
A large enterprise that has run on SAML and LDAP federation for a decade now wants token-centric authentication, just-in-time access and a single experience across channels. That’s an architecture programme, not an upgrade, and it needs people who’ve done it rather than people who’ve read about it.
The governance that isn’t landing
An identity governance deployment that has stalled, audit findings that are still open, and a lifecycle process that nobody trusts. This is the unglamorous work that has to be done before anything modern sits on top of it.
The onboarding bottleneck
Every project team rebuilding its own path onto the identity platform, slowly and differently. The fix is usually a central SDK or a reusable pattern that gives every team the same route in, and it needs someone senior enough to design it and win the argument for it.
What we agree before the search goes to market
Identity briefs tend to arrive written around whichever platform the business happens to run, which frames the search around administration rather than architecture. Five things get pinned down before we approach anyone:
- Architecture or operations. Whether the hire owns the target state or runs the platform, because the two markets barely overlap and the title is the same in both briefs.
- The non-human gap. Whether machine and workload identity is in scope, and how bad it currently is, because that single answer changes the profile more than any other.
- The platform reality. What’s deployed rather than what the roadmap says, since a stalled governance deployment is a different problem from a greenfield platform.
- Contract or permanent. Which of the two the work needs, and whether the honest answer is one of each, which it often is on a programme with a deadline.
- Who owns the outcome. The executive the hire answers to, and whether that person can make a decision when the recommendation is unpopular.
We write the brief around the outcome the hire owns and the architecture they have to defend, and treat the platform names as context for the search.
How we assess identity and access management candidates
The scarce thing is evidence that someone turned a modern identity vision into architecture, reusable patterns and something that runs in production. Plenty of strong candidates have administered a platform faithfully for years without ever owning a target state, and length of tenure in identity tells you much less than the question of what they designed and what happened to it.
So we look for the specific calls: the authentication flow they designed and why, the migration they sequenced and what they cut, the moment they told a programme that its approach wouldn’t scale. Product configuration alone isn’t architecture, and we say so rather than letting a title carry a search. Where someone has deep platform depth but no evidence of owning architecture, we flag that honestly instead of hoping the brief absorbs it.
Roles we are working on now
Both live roles this page was written around are on the careers page, and they’re deliberately different shapes.
- A contract Identity Architect, to turn a broad identity mandate into a practical target state and a delivery roadmap
- A permanent Enterprise Architect, to set the shape of enterprise technology outcomes with a commercially grounded architecture view
One is interim architecture with a deadline, the other is a permanent role. Enterprises often need both at the same time, which is why we ask which one the problem is before we go to market.
Frequently asked questions
Do we need an identity architect or an identity engineer?
The architect owns the target state, the patterns and the argument for them. Engineers build and run inside that. Where the business already knows its target state and the constraint is throughput, engineers are the hire. Where the roadmap keeps restarting, the missing piece is usually the architect, and hiring more engineers doesn’t fix it.
Do we need to hire for AI, or is this an identity problem?
Mostly an identity problem. AI at scale depends on machine identities that can be issued, scoped, rotated and revoked without a human in the loop, and on authentication that holds up when the volume isn’t human. Businesses framing this as an AI hiring problem tend to buy AI capability and then discover the constraint was identity all along.
Contract or permanent for identity work?
It depends on whether the work has an end. A platform migration, a tokenisation programme or an audit remediation is a defined piece with a date on it, and contract is usually right. Owning the identity roadmap for the next three years is a permanent role. Programmes frequently need one of each, and we’ll say so.
What's non-human identity, and why does it keep coming up?
It’s every identity that isn’t a person: service accounts, workloads, integrations, certificates, secrets and now AI agents. They’re usually the least governed part of an estate and the fastest growing, because every new system and every new agent adds more. Machine to machine identity is where most of the operational risk now sits.
Why is identity work so hard to hire for in Australia?
The profile sits at an intersection rather than in a discipline: deep identity expertise, cloud-native architecture, token-based authentication design and enough seniority to carry an executive. A great many people are strong in one of those. The intersection is genuinely thin, which is why these searches take longer and why the brief matters more.
Do we need our identity platform replaced?
Usually not, and that’s worth establishing before anyone is hired. Most of the time the platform is capable and the design on top of it is the problem. A replacement is an expensive way to discover that the target state was never agreed.