Software Engineer

Twilio Twilio · Enterprise · San Francisco, CA · Engineering

Software Engineer role focused on building the onboarding and integration experience for Stytch, a Twilio product, which includes developer-first identity experiences and emerging agentic and non-human identity use cases. The role involves full-stack development, API design, and improving customer integration.

What you'd actually do

  1. Design, build and own the onboarding and integration experience for our customers, including intuitive, reliable SDK APIs that make our product easy to adopt for developers.
  2. Partner closely with Product, Design, and Engineering leadership to shape the team’s roadmap, prioritize high-impact work, and deliver features that unlock customer value quickly.
  3. Build in ambiguity: break down complex authentication and identity problems, make pragmatic tradeoffs, and deliver incremental milestones to production.
  4. Raise the bar for the quality of the products you work on through testing, versioning, documentation, backward compatibility, and smooth migration paths.
  5. Improve performance, reliability, and security of client-side flows, especially those on customers’ critical paths.

Skills

Required

  • 3+ years of experience as a fullstack engineer
  • delivering customer-facing web products in production
  • modern frontend technologies
  • Next.js
  • Experience developing and maintaining complex web applications and/or public-facing web SDKs
  • Experience building developer-first APIs and tools, with a focus on integration experience
  • Proven ability to ship high-quality, reliable software that runs across browsers and environments
  • Excellent written and verbal communication skills
  • comfortable writing design docs and leading technical discussions
  • Bachelor’s degree in Computer Science or equivalent practical experience
  • Schedule: ability to work non-standard, on-call rotation weekend and holiday hours

Nice to have

  • Experience owning or contributing to open-source libraries or SDKs
  • Familiarity with authentication, identity, security, or fraud-adjacent client-side flows
  • Experience supporting public SDKs: release automation, semantic versioning, deprecations, and long-term maintenance
  • Interest in emerging identity patterns, including agentic/non-human identity and new auth workflows

What the JD emphasized

  • Next.js experience is a must
  • developer-first APIs and tools
  • customer-facing web products
  • complex authentication and identity problems
  • emerging identity patterns, including agentic/non-human identity and new auth workflows