Software Engineer
Staff Software Engineer, Frontend Location: Austin, TX, United States Category: Consumer Experience & Customer Care Job ID: 3261 Apply Now Description Staff Software Engineer, Frontend — Authentication & Identity At realtor.com®, sign-in
Staff Software Engineer, Frontend
Location: Austin, TX, United States
Category: Consumer Experience & Customer Care
Job ID: 3261
Apply Now
Description
Staff Software Engineer, Frontend — Authentication & Identity
At realtor.com®, sign-in is the front door. Every saved home, every saved search, every personalized recommendation and every lead depends on knowing who the consumer is — across web, mobile web and native, and across every subdomain we operate. We are looking for a Staff Engineer to serve as the technical anchor for the frontend of our Authentication & Identity platform, owning the client-side architecture that millions of authenticated sessions pass through every day.
The Role
As a Staff Engineer, you won't just write code; you will define how authentication is built and consumed across every consumer surface at realtor.com®. Auth is the one system every team depends on and no team wants to own — you will own it, and you will make it something other engineers reach for rather than route around. You will balance hands-on development with high-level system design, ensuring identity is seamless for consumers and boring for the engineers who integrate with it.
Architectural Leadership: Own the end-to-end client architecture of our identity platform — our React/Next.js consumer web surfaces, the shared auth libraries every other team consumes, and their integration with Auth0 and our GraphQL gateway. We are actively consolidating multiple co-existing auth implementations onto one platform; you will lead that convergence and decide what the single path looks like.
Auth at Scale, Without Friction: Drive the client-side work behind new authentication methods — passkeys/WebAuthn, one-time passcodes, social and federated sign-in — and own token lifecycle, session continuity and cross-subdomain identity in the browser. You are responsible for both halves of the tradeoff: reducing forced sign-outs and abandoned registrations while holding the security line on OAuth 2.0/OIDC, PKCE and token handling.
Reliability and Observability: Auth failures are silent, and users don't file tickets — they leave. You will define what "healthy" means for the sign-in path, instrument it, and make regressions visible before they show up in conversion. You will lead frontend resiliency and error-strategy work so that a degraded dependency downgrades the experience instead of ending the session.
AI Strategy & Governance: Lead the integration of AI coding assistants and LLMs into the SDLC. You are responsible for the "human-in-the-loop" verification of AI-generated code regarding security, performance, and long-term maintainability — a bar that is higher, not lower, in code that mints and stores credentials.
Posted September 25, 2026