Software Engineer Ii, Backend - Platform

Uber Uber · Consumer · Sao Paulo, Brazil · Engineering

Software Engineer II, Backend - Platform role on the Login Services team within Core Security Engineering at Uber. This role focuses on building and operating Uber's authentication platform for human and non-human identities, ensuring seamless, secure, and resilient login experiences. Key initiatives include developing a security knowledge platform to compute risk levels and evolving next-generation authentication capabilities. The role involves building core auth services, improving SSO/login health, implementing automation for IAM operational toil, and contributing to data/graph/risk-signal features for the security knowledge platform.

What you'd actually do

  1. Own and deliver a well-scoped slice of Uber’s authentication stack (human + non-human identities), improving security and login reliability.
  2. Build/extend core auth services and workflows (APIs, policy checks, token/session flows) under existing architecture guidance.
  3. Improve tier-zero SSO/login health via bug fixes, performance tuning, and availability-focused changes.
  4. Ship production-ready code with strong fundamentals: tests, code quality, safe rollout/rollback, and clear operational docs/runbooks.
  5. Add observability (metrics/logs/traces), dashboards, and alerts; participate in on-call and drive incident follow-ups to completion.

Skills

Required

  • Proficiency in at least one major language (Go/Java/Python/TypeScript)
  • Experience building and operating distributed services: APIs, data stores, async workflows, and service-to-service integrations.
  • Demonstrated operational excellence: monitoring/alerting, debugging, incident participation, and improving SLAs through reliability work.
  • Working knowledge of security fundamentals (auth flows, sessions/tokens, least privilege)
  • Ability to own a component end-to-end for a scoped area: design docs, implementation, rollout/rollback, and long-term maintenance.
  • Strong engineering hygiene: tests, code reviews, documentation/runbooks, and measurable improvements over time.

Nice to have

  • Hands-on experience building or operating authentication/authorization systems (AuthN/AuthZ)
  • improving observability (metrics/logs/traces) in production.
  • Familiarity with identity/security concepts (SSO, MFA, session/token flows, access controls) and common failure modes at scale.
  • Experience contributing to data pipelines or data-backed products (tables/streams/graphs), with an understanding of data quality and reliability.
  • Troubleshooting skills in high-availability services: can debug incidents, find root cause, and drive fixes with good follow-through.

What the JD emphasized

  • agentic workflows
  • non-human identities
  • security knowledge platform
  • risk levels for identities and assets
  • strong authentication
  • minimal operational cost