Developer Success Engineer
This isn’t one of those situations where we tack “engineer” onto the back of every role at LiveKit. No. We’re actually looking for an engineer*. A rare type of engineer that cares about talking to and advocating for customers, helping unblock them by fixing bugs or writing up sample code, and providing customers with guidance, pointers and support. We say rare because in our experience, most engineers aspire to architect large-scale systems or tackle deeply technical problems. Said differently, most engineers want to have influence over the technology they work on or with. There’s nothing wrong with that, we love hardcore engineers. There are many at LiveKit — we’re not complaining. But, this time, we’re looking for a new teammate that wants to have influence over our product and business. If you’d be energized by seeing a developer or team flip a LiveKit integration from staging to production—secretly satisfied in knowing you helped make it possible—you are perfect for this.
*For clarity, this role is compensated like any other engineering role.
What You'll Do
Support and work directly with developers, teams, and companies building with LiveKit, both commercially and in the community.
Triage, file, and fix bugs, respond to support tickets, write sample and production-quality code, update documentation and author technical guides in service of customers.
Regularly meet or follow-up with LiveKit customers to ensure their continued success on the platform.
Collaborate closely with Sales, BD, and Partnerships teams on strategy and support them in customer conversations.
Who you are
You are an engineer.
You don’t mind reading more code than you write.
You’re a natural teacher.
You find joy in helping others learn and succeed.
You can break down complex concepts in a way that’s easily understood by others.
You have excellent spoken and written English.
You enjoy learning new programming languages (quickly) and prototyping.
Bonus Points
You’ve literally done this before.
You have experience working with a community of developers.
You have contributions to OSS.
You’ve built something with LiveKit.
In those school group projects, you did most of the work (:sigh:).
You’re multilingual — LiveKit has users around the world.