Developer Experience Engineer (DX)
About the role
DX at DogeSMS owns the surface that customer engineers actually touch: API documentation, OpenAPI specs, generated SDKs, code samples, CLI tooling, error message quality, and the Postman / Bruno collections that show up in customer onboarding. This is an engineering role with content production as a first-class output. The forcing function is the customer's time-to-first-OTP after they sign up — if it takes more than 20 minutes, we have work to do.
What you'll do
- Own the API documentation pipeline: OpenAPI spec → generated SDKs (TypeScript / Python / Go / PHP) → published docs site with executable code samples.
- Build and maintain the CLI / Postman / Bruno collections that customer engineers use during integration; benchmark time-to-first-success and drive it down.
- Treat error messages as a product surface — partner with backend engineering to ensure every error code has a clear actionable message + linked doc explaining the recovery path.
What we expect
- 4+ years in DX, developer tooling, or platform engineering at a developer-facing company. Examples of API docs / SDKs / CLI tools you have shipped.
- Strong TypeScript + Python skills minimum; comfort generating code from OpenAPI specs (openapi-typescript-codegen, openapi-generator, or similar tooling).
- Empathy for the developer's first-30-minutes — you have user-tested onboarding flows with real engineers, recorded the sessions, and turned them into roadmap items.
Stack we use
OpenAPI 3.1 spec as source of truth, Mintlify / Docusaurus / Nextra for docs, openapi-typescript / openapi-generator for SDK codegen, Bruno + Postman for shareable API collections, GitHub Actions for docs/SDK auto-publish on spec changes.
Compensation
On the radar. Compensation is calibrated to local cost of living when we open this role — we publish bands when we begin interviewing, not before. USD-denominated regardless of jurisdiction, contractor or employment depending on your legal situation.
Hiring process
- Not actively interviewing right now — this role sits on our 12-month hiring roadmap rather than today's pipeline.
- Submit the talent pool form below; we reach out when we begin interviews, typically 4-8 weeks before a public hire.
- When the role opens, expect a process similar to our current active openings: a short async exercise, 1-2 conversations with the relevant team, and a scoped paid trial project. We do not run leetcode-style screens.
Join the talent pool
Submit the form below to be considered when this role opens. We typically reach out 4-8 weeks before we begin interviews.