Developer Advocate

About the role

Developers are shipping AI-generated code faster than anyone can review it. Quality is the new bottleneck and AI-generated-code governance is increasingly necessary. Qase is how engineering teams verify the quality of AI-generated code, so their companies can safely adopt AI-accelerated workflows. We're looking for someone with a technical background and love of software quality who wants to contribute to re-imagining how engineering orgs work given the massive implications of heavy adoption of AI-coding platforms and MCP-mediated access to other developer tools.

You might be a fit if you're…

A talented QA / quality engineer or quality-obsessed developer. From there, two paths fit this role:

• A QA practitioner growing into advocacy: Maybe you've dabbled (a talk, a blog, an OSS contribution), maybe you haven't yet, but you genuinely want to do this: get on stage, work a booth, be in the testing/dev communities. We'll build the advocacy with you: mentorship, speaker coaching, and a staged ramp at real events. You're ready to do it full-time, with a product to influence and a company behind you.
• Experienced developer advocate: Speaking at conferences, maintaining or contributing to OSS testing tools, running a newsletter or blog, or the person whose takes on testing and AI-generated code people actually repost, and with the QA credibility to back it. You arrive ready and ramp faster.

You're credible because you've done the work, not because you read about it.

What you'll do

• Be part of the communities we serve: online (the testing/dev Discords, Slacks, subreddits, LinkedIn), at meetups, and on conference stages. Showing up in these communities as a peer who happens to work at Qase and who sincerely wants to help their peers find ways to improve their workflow.
• Take a real point of view on software quality in the age of AI: how teams should test AI-generated code, verify intent, and keep token use under control. Start with thoughtful research, and from there create derivative content and genuinely-useful tools.
• Make the rest of the company credible. Coach sales and marketing on what lands and what gets an eye-roll. e.g. be the person a salesperson can grab before a call to understand the difference between a release manager and an SDET.
• Run the US field motion: practitioner meetups, prospect dinners and outings, conference presence, alongside reps and a supporting event coordinator.
• Close the loop to product. You'll understand what the community wants, and represent their needs to the rest of Qase.

What we're looking for

Required of every candidate:

• QA / software development credibility. A testing or developer audience trusts you.