A support analyst in a mid-sized Ahmedabad company spent her first two years resetting passwords. She was good at it, quick and patient, and slowly she noticed that the same tickets kept returning: a contractor who still had access months after leaving, a service login nobody could explain, an executive locked out while travelling. One afternoon she asked her manager who owned those problems. The answer was a shrug. That shrug became her career. Over the next two years she moved toward what the industry now calls IdentityOps, and the path she took is a useful map for anyone in Gujarat, or anywhere, who wants a skilled and durable role in security-minded IT. I lean on the Ops Atlas for the facts below, since it lays out the discipline and its vocabulary, and I flag where each skill fits.
What the work actually is
The Atlas explains the job as the day-to-day running of the people-and-machine roster: who exists, how each proves it, and how each is removed. The entry admits the label is still settling. A few suppliers keep the scope narrow, meaning upkeep of a live sign-in platform; others describe a blend of access tooling, security work and automation; and in certain firms it is merely a department’s name. The practical lesson for a job-seeker is to read the description carefully, because the same title can mean quite different duties.
A typical week touches four areas: arrivals, role changes and departures driven from the HR system; single sign-on and automatic account provisioning; recovery and second-factor enrolment; and the lifecycle of non-human accounts such as keys and service logins. The Atlas also lists work that sits beside the role but outside it: designing permissions, handling access requests and elevation, running the HR process itself, customer identity and threat detection. Knowing the boundary keeps you from being handed everything.
Skills to build, in a sensible order
1. The directory and the sign-in service. Start by learning how a directory and a cloud identity provider store people and groups. The Atlas cites Entra ID and Okta as typical examples of the cloud sign-in layer, with the company’s HR platform acting as the authority on who actually works there. You do not need to master every product; pick one and learn it deeply enough to explain its joiner and leaver flow.
2. The protocols. Learn the names and rough purposes. SAML 2.0 and OpenID Connect carry sign-in between systems; SCIM 2.0, described in RFC 7643 and RFC 7644, carries account changes. RFC 9700, a security guidance paper, steers developers away from outdated OAuth shortcuts. Reading the actual specifications, even only the introductions, sets you apart from candidates who know only the product screens.
3. Authentication strength. Understand why only FIDO2/WebAuthn and smart cards count as phishing-resistant, why synced passkeys are treated differently at the highest assurance level, and what current US guidance says about long passwords, blocklists and the end of scheduled expiry. This knowledge is useful in interviews because it shows you follow how advice has changed.
4. Recovery and social engineering. Learn how attackers exploit help-desk resets and number swaps, with the Atlas pointing to a well-documented crew that used both. Practise writing a recovery procedure that does not rely on phone call-backs.
5. Machine identities. Learn the lifecycle: inventory, owner, purpose, expiry, short-lived credentials, rotation and disable-wait-delete retirement. The OWASP list of the top ten non-human identity risks from 2025 is a good reading list.
6. Measurement. Practise computing leaver compliance end to end rather than at the central service only. The Atlas’s example turns forty leavers, thirty-six on time and three with lingering app accounts into 90.0 percent at the front door but 82.5 percent overall. Being able to explain that gap in two minutes is worth more than a certificate.
Reading list and frameworks
The Atlas points to several public resources worth bookmarking: the IDPro body of knowledge for professional vocabulary, NIST’s digital identity guidelines, CISA’s zero-trust maturity model along with its one-page note on multi-factor methods that resist phishing, and MITRE ATT&CK techniques such as valid accounts, multi-factor request generation, domain trust modification and modifying authentication processes. You will not memorise all of it. The goal is to know where to look and to recognise the terms when a colleague uses them.
A portfolio you can build at home
Employers value evidence. A few weekend projects, all doable with a free trial tenant or a small lab, make a credible portfolio:
- Write a one-page leaver runbook in the order the Atlas gives: record, disable, revoke sessions, push deactivation to apps, timestamp. Then test it and record the elapsed time.
- Build a register of machine accounts for a fictional small business, with owner, purpose, expiry and review fields.
- Draft a recovery script with three tiers: self-service, manager-assisted and privileged.
- Compute coverage versus usage for a made-up set of sign-in numbers, and explain why the two differ.
- Run a dormant-login sweep on a test directory and document the exceptions you chose.
Turning the stories into interview answers
Interviewers in this field tend to ask scenario questions, so prepare two or three short stories. Describe a departure you traced end to end and what you found in the long tail of tools. Explain how you would respond to a caller demanding an urgent password reset. Say how you would decide whether a machine account is safe to delete, using the disable, wait and delete pattern. Keep each story under two minutes and end with a number: how long it took, how many accounts were affected, what changed afterwards. Numbers signal that you measure outcomes instead of merely performing tasks.
Be honest about gaps as well. The field has no single founding standard and vendors disagree about scope, so a candidate who says “here is what I know, here is where definitions vary” sounds more credible than one who recites a product brochure.
Habits that separate strong candidates
Three habits show up in people who grow quickly here. They write things down, because an identity routine that lives in one head disappears when that head moves on. They test before they trust, running a dummy account through a flow rather than assuming the vendor’s documentation matches reality. And they stay curious about the business side, asking what a manager in sales or finance actually needs on their first day, because good account design starts from real work, not from the tool’s defaults.
Where the career goes
The Atlas offers a five-level maturity ladder for organisations, from ad hoc to continuous, and it is useful for career planning too. At the early levels you are the person who makes the first inventory and the first drill. At the middle levels you automate account creation from the HR record and measure compliance. At the upper levels you work on risk signals between systems and short-lived machine credentials. Each rung has different tasks, so you can see how a role grows. The Atlas also cautions that small organisations may skip a separate practice and that governance products should not be bought before the HR data is clean, a reminder that judgment often matters more than tooling.
The analyst from Ahmedabad followed roughly this order. She started with a leaver runbook for her own team, presented the timing numbers to her manager, and was given the first formal ownership of the process. Within a year she was running quarterly drills. She says the most surprising lesson was that nobody objected once the numbers were on the table.
If you want to check the definitions and see how the Atlas organises the discipline before you commit to a learning plan, the Ops Atlas entry that describes IdentityOps is a good place to read first. For a complementary view on structuring a technology learning journey, this step-by-step overview of building a DevOps career shows how a similar skill ladder works in a neighbouring field.
After the study, a trip
Learning is easier when you take breaks. When you are ready for one, the pointers for sketching a first Gujarat itinerary will help you decide where to start. Come back refreshed and pick one portfolio project to begin.