Principal Software Engineer

Okta Okta · Enterprise · Bangalore, India · SW Eng - Applications-674

Okta is seeking a Principal Software Engineer with a focus on UI to build and own the long-term technical strategy and architecture for their core UI platform infrastructure. This role involves defining technical vision, resolving complex architectural debt, establishing standards, and leading technical due diligence for strategic decisions, all within a fast-paced agile environment.

What you'd actually do

  1. Define, socialize, and gain organizational consensus for the 3–5 year technical vision and strategic roadmap for Okta’s core UI platform infrastructure.
  2. Proactively identify and drive the resolution of the most systemic technical issues and complex architectural debt across the R&D organization.
  3. Serve as the final authority on critical, cross-team architectural decisions, ensuring long-term scalability, reliability, and security.
  4. Provide deep technical mentorship and sponsorship for key initiatives led by Staff and Senior Staff engineers, multiplying their impact and ensuring alignment with company strategy.
  5. Establish and govern architectural standards and best practices for developer experience, observability, and quality across all frontend feature teams.

Skills

Required

  • 10+ years of software development experience
  • Expertise in software architecture and implementation
  • strong development background in a language like Java, Python, or C++
  • significant experience with frameworks such as Spring, React.js, or Node.js
  • strong grasp of software engineering designs, principles, and practices
  • building scalable and maintainable systems
  • strong communication skills
  • distill complex concepts into simple, easy to understand narratives
  • Experience being part of a platform team treating developers as customers

Nice to have

  • Experience defining and implementing internationalization and localization strategies for large-scale enterprise applications.
  • Familiarity with globalization testing processes

What the JD emphasized

  • complex technical challenges
  • multi-year
  • complex architectural debt
  • critical, cross-team architectural decisions
  • multi-million dollar investments
  • multi-year shifts