The opportunity
As a Staff Software Engineer on the OIN team, you'll be a technical leader for a platform a very large share of Okta's customers depend on every day. You'll independently own complex, ambiguous problems end-to-end — from technical scoping through design, delivery, and production…
What you'll do
Lead discovery and technical scoping for new requirements, turning ambiguous: product asks into a concrete architecture, phased delivery plans, and credible estimates, in close partnership with product, architecture, and design.
Design and evolve the APIs, data models, and security posture that OIN's: integrations depend on, with an eye toward backward compatibility and long-term extensibility.
Drive technical decisions across ambiguous, multi-team dependencies, aligning: stakeholders across engineering, product, and other parts of the business when the "right answer" isn't obvious yet.
Modernize and evolve a large, long-lived production system incrementally: without disrupting the customers and integrations that depend on it every day.
Maintain a high bar for security, testing, and code quality, including: vulnerability remediation and threat-aware design, while keeping a real sense of urgency on customer-impacting work.
Own the production health of the systems you build by writing root-cause: analyses when things break, driving follow-through on the fixes, and building the observability that prevents repeat incidents.
What they're looking for
- Champion AI-native engineering practices by using AI coding assistants and: AI-augmented workflows as a core part of how you design, build, review, and ship software, and helping the team adopt them well.
- Mentor and raise the technical bar for the engineers around you, and: represent the team's technical point of view in cross-functional forums.
- + years of professional software development experience, with a demonstrated: history of technical leadership and mentorship.
- Deep proficiency in Java (our primary backend language) or a comparable: strongly-typed backend language/framework, with the judgment to know when and how to modernize a large, long-lived codebase without disrupting the customers depending on it.