Staff Software Engineer, Okta

• Experience: 7+ years building distributed, highly available production backend systems
• Technical Depth: Hands-on experience shipping production services in Java and/or Go
• Domain Expertise: Strong grounding in OAuth 2.0, OIDC, and RFC 8693 token exchange. You should be highly comfortable reading, interpreting, and implementing spec-driven code
• Track Record: Proven success in shipping identity, authorization, or edge-of-network services at scale, including a deep understanding of the operational side (rollouts, feature flags, observability, incident response)
• Agentic Fluency: Working fluency with agentic development tools (e.g., Claude Code, MCP servers, AI-assisted code review). You have concrete opinions on where they accelerate workflows and where they fall short
• Communication: A direct communication style, a talent for writing strong technical design docs, and the ability to operate seamlessly between a data plane service and a large identity control plane

Desirable

• The Agent Gateway team owns the identity-aware infrastructure that connects enterprise AI agents to the tools, data, and services their organizations authorize. Every call from Claude, Agentforce,, Codex, and internal/homegrown agents to a resource flows through us. We enforce authorization, isolate credentials, mint the right token per target, and produce the audit trails that security teams rely on
• Okta is looking for a Staff Software Engineer to serve as a technical anchor for the Agent Gateway team. You will own critical parts of the data and control planes and drive architectural design as the MCP and agent identity specs evolve
• In this role, you will work close to the metal on request routing, token exchange, credential resolution, and policy evaluation
• You will work equally close to the identity control plane on config bundles, tenant fanout, and operational rollouts
• You are expected to make sharp technology choices, prototype with agentic tooling, and turn rough product ideas into production-ready systems
• You will have the opportunity to build and scale services used by agentic traffic, ensuring workflows are reliable and performant at an unprecedented scale. This role sits at the critical intersection of product, security, and infrastructure
• Architect and Lead: Own the end-to-end design and delivery of major gateway capabilities, from virtual MCP server aggregation to Agent-to-Agent brokered delegation, as well as on-premises deployment models
• Design for Security and Runtime: Set the standard for how the gateway handles credentials, tokens, tenant isolation, and audit logging. Every decision carries direct customer trust and compliance weight. The Gateway team sits in the path of agent runtime traffic, which is in the critical path for customers
• Move With the Protocols: Track and shape MCP, OAuth token exchange, and agent identity specifications. Feed lessons learned from production back into the specs and their reference implementations
• Ship With Agentic Tooling: Treat Claude, Claude Code, and MCP-connected agents as first-class parts of your engineering workflow. Set the pattern for how the team uses these tools across design, code generation, code review, and operations—including custom skills, subagents, and MCP servers that accelerate the entire team
• Raise the Bar: Drive code review, testing standards, incident retrospectives, and our design doc culture. Mentor engineers on the team and foster alignment across adjacent groups