Okta5 days ago

Principal Software Engineer – Developer Platform (Auth0)

RUB 15,333–21,083per month · before tax

MARKET

13,750 ₽median for this role

Tech Lead / Team Lead · 146 jobs with disclosed pay

5,250half of the offers: 10,104–18,1691.2 млн

At market · above 60% of offers

Toronto

Responsibilities

01Own the platform architecture: Set the technical direction for the developer platform, and make the cross-cutting decisions that keep it coherent and easy to build on as it grows
02Architect for scale: Design the distributed systems behind the platform for throughput, reliability, and consistency, so the guarantees developers depend on hold up under real load
03Turn ambiguity into direction: Take the hardest, most vaguely specified platform problems and turn them into clear, modular technical designs the team can execute against
04Design for developers and agents: Shape the platform so it holds up whether a person or an agent is calling it, and so both can build and automate their work against Auth0
05Raise the engineering bar: Set the standard for how the team designs, builds, and operates the platform, and lead deep, constructive reviews that grow the engineers around you
06Partner across teams: Operate peer-to-peer with tech leads in adjacent groups to review major architectural decisions and keep the wider platform aligned

0110+ years of software engineering experience, with a proven track record as a Principal or Staff level individual contributor
02Distributed architecture depth: Extensive experience designing and operating high-scale, reliable backend and event-driven systems, with a strong grasp of the tradeoffs in throughput, consistency, and failure handling
03Platform thinking: A track record of designing and shipping platforms or developer-facing systems at scale, with an instinct for the interfaces and abstractions that keep them coherent as they grow
04IAM platform thinking: Deep understanding of identity and access management, with a sense for the platform capabilities and abstractions that make identity easier for developers to build on
05Ownership in ambiguity: You can own vaguely specified problems and drive them to a clear technical direction without heavy top-down scoping
06Strong engineering fundamentals: Strong Node.js fundamentals; Go a plus
07Agent-aware design: Hands-on familiarity with agentic tooling, MCP, or LLM-facing design, and a sense for how agents consume a platform
08Cross-functional collaboration: Experience working across engineering, product, and architecture in a fast-moving environment, and a habit of raising the bar for the people around you