Developer Success Engineer

Overview

Join Twilio as a Developer Success Engineer for Stytch in a hybrid engineering and customer success role. Work directly with developers to help them understand Stytch, design implementations, resolve questions, and feed customer insights back to Product, Design, and Engineering teams.

What you'll do

• Build new features and fix bugs in Stytch and Twilio products.
• Serve as a technical resource for customers when they have questions about the product.
• Improve documentation and processes for internal and external stakeholders.
• Help developers design implementations and answer questions throughout the implementation process.
• Serve as the voice of the customer within Stytch and close the feedback loop by ensuring customer insights make it back to Product, Design, and Engineering teams.
• Implement improvements yourself as opportunities arise.
• Contribute new features to Stytch and Twilio products through code as the team grows.

What you'll need

• A genuine drive to understand customer needs and concerns.
• Deep curiosity, grit, and tenacity to troubleshoot tough technical issues and track down root causes.
• Hands-on programming experience in a major language, with 2+ years writing code to build, debug, or automate in a support, solutions, or software engineering role.
• Ability to debug others' code, including customer integrations, SDKs, and open-source libraries, and ship small, well-tested fixes in an existing codebase.
• Familiarity with modern web services and APIs.
• Demonstrated ability to communicate credibly and effectively at all levels.

Nice to have

• Experience with authentication protocols, including SAML/OAuth, MFA, and IdP.
• Prior experience in a customer-facing technical role, such as technical support, solutions engineering, or field engineering.
• Direct experience working on a dedicated software development or product team.

Details

• Remote role based in the East Coast time zone only.
• Not eligible to be hired in CT, NJ, or NY at this time.
• May require occasional travel for project or team in-person meetings.
• May require reporting in person on an ad-hoc basis for team gatherings, functional off-sites, or customer meetings.