Staff Developer Experience Engineer

What you'll do

• Own the direction of developer experience: set the DX roadmap, act as technical lead without direct reports, represent DX in planning with Product, Engineering, and Partnerships.
• Own the SDK code-generation architecture: design and maintain the system that produces multi-language SDKs, making adding new languages low-cost.
• Set standards for developer experience: define quality bar, cross-language parity, versioning, release discipline, and observability for all SDKs.
• Raise the level of engineers touching the SDK surface through code review, patterns, documentation, and pairing.
• Attack friction at the root: identify and fix systemic issues across developer segments structurally.
• Build tooling the team relies on: code-generation pipeline, CI infrastructure, starter repositories, and context for human and AI coding agents (including llms.txt).
• Design for resilience and longevity: create documentation, automation, and architecture that scales beyond any one person.
• Be the technical voice into Product, Engineering, Marketing, and Partnerships for developer-facing decisions.

What we're looking for

• Track record owning developer-facing tooling across multiple languages, from libraries to SDK generators, templates, and release automation that others build against.
• Use AI as real infrastructure in workflow: agentic pipelines, custom tooling, generators authored and relied on daily, with strong verification (discuss most complex AI system built recently).
• Instinct to build reusable systems that outlive you (generators, automation, pipelines, architectures adopted by others).
• First-principles reasoning about systems: view SDKs, code generation, and partner ecosystems as having inputs, outputs, feedback loops, and boundaries.
• Production ownership instincts: treat SDKs as production systems with observability, incident response, backward-compatibility, and bias toward removing toil.
• Range beyond core expertise: go deep on DX and tooling but can handle developer content, demos, or community work.
• Think in developer outcomes: connect SDK and docs work to product activation and retention.

What you'll work with

• Real-time, streaming SDKs wrapping low-latency WebSocket APIs for speech-to-text, text-to-speech, and Voice Agents (streaming, partial results, reconnection, backpressure, concurrency).
• Multiple languages and tech stacks: Python, JavaScript/TypeScript, Go, Rust, .NET, Java (and monitoring emerging ones).
• Open source on GitHub: own repos, engage with external contributors, issues, PRs.
• Spec-driven, generated SDKs from shared API specification (focus on generation pipeline and templates).
• Wider surface: CLI, documentation, reference experience, starter repos, and integrations for partner stacks (Pipecat, LiveKit, AWS, Twilio).

What success looks like

• Set standards for SDKs and developer tooling adopted by the team.
• Clear DX direction followed by the team; engineers improve at DX through your influence.
• Recognized authority on developer experience; work referenced at integration layer.
• More signups reach successful first API call; fewer drop at integration due to effortless SDKs and docs.
• Reduced support load as tooling and documentation preempt questions.
• Hardest, least-defined DX problems named and solved proactively.