Business Analyst
crypto:applicationengineeringIC4Professional Services-720
Compensation
Not disclosed
Secure Every Identity, from AI to Human
Identity is the key to unlocking the potential of AI. Okta secures AI by building the trusted, neutral infrastructure that enables organizations to safely embrace this new era. This work requires a relentless drive to solve complex challenges with real-world stakes. We are looking for builders and owners who operate with speed and urgency and execute with excellence.
This is an opportunity to do career-defining work. We're all in on this mission. If you are too, let's talk.
The Customer First Team
We are a team of Identity and Access Management experts. We help customers, businesses, and organisations maximise their Okta IAM platform investment, providing rapid time-to-value in adoption and usage and promoting scalability and agility. Our team sits within the Customer First area - focused on ensuring the long term success of our customers. Join our team! We’re building a world where Identity belongs to you.
Role Summary
The Business Analyst (BA) is a central figure on the Okta Professional Services team. Your mission is to serve as the bridge between customer business objectives and technical implementation, driving high-impact outcomes for Okta Identity and Access Management (IAM) deployments. You will own the requirements lifecycle—from initial discovery and stakeholder alignment to functional design and solution integrity—ensuring that the final delivery is secure, scalable, and aligned with the customer's strategic needs.
Key Responsibilities
Discovery & Requirements Facilitation: Facilitate stakeholder workshops brainstorming sessions to uncover requirements, map current-state IAM processes, and identify dependencies and pain points across IT, security, and product teams.
Documentation & Solution Design: Translate business needs into detailed functional and non-functional requirements. Produce clear business process flows and solution design diagrams to visualize the "how" and "why" behind the technical config