- 📊 You’ve built demo environments, demo data, or sandbox/trial environments at a SaaS company before.
- 🧰 You’ve written automation scripts or tooling to generate data or configure environments at scale.
- 🎬 You’ve built and maintained a library of reusable, templated environments or assets that others relied on.
- 🤝 You have experience with HR tech, ATS workflows, or recruiting operations.
Examples of things you’ll work on
- 🧱 Own the scaled demo system — customize and extend the demo environment infrastructure to support the GTM team.
- 🗂 Generate realistic demo data — standardize and automate how demo environments are populated to eliminate manual setup.
- 🎯 Build vertical- and market-specific demos — create tailored content for target verticals and additional languages as we move upmarket and expand internationally.
- 🚦 Own demo readiness for new releases — make sure every feature is correctly configured and demoable in demo environments before it ships to GA.
- 🧪 Stand up trial and sandbox environments — create templated environments prospects can use to test Ashby during the sales cycle.
- 📚 Document how it all works — maintain clear documentation so the GTM team knows when and how to use each demo environment.
WHY BECOME A DEMO ENGINEER AT ASHBY?
You’ll define a role that doesn’t exist yet. This is a net-new role designed around a real business need. You won’t inherit a mature playbook — you’ll build the infrastructure that lets the whole GTM team demo at a higher level.
Your work will compound. A great live demo helps one deal. A reliable, current, well-documented demo system improves every demo the entire go-to-market team runs. If you like creating leverage, this role has a lot of it.
The product gives you something real to work with. Ashby has strong product-market fit, and that matters here. You’re not manufacturing excitement around a weak product — you’re making it effortless to show something that already resonates when it’s shown well.
You’ll sit at the intersection of Engineering and GTM. This is a rare blend of technical building and understanding what the field actually needs. You’ll help translate our product releases into live deals — and connect the two.
The surface area keeps growing. As we ship new features and expand into new product areas, new verticals, and new geographies, demo needs compound with each release. There is a lot to build, and it only gets more interesting.
Reasons you shouldn’t apply
- If you want to be customer-facing or closing deals, this isn’t the right role — the impact here happens behind the scenes.
- If you’re not genuinely hands-on technical — comfortable in JSON, APIs, and data — the core of this job will be frustrating.
- If you need a fully built environment and a finished playbook, the ambiguity of a 0→1 role with infrastructure still being built will feel uncomfortable.
- If continuously maintaining and updating environments as the product changes sounds tedious rather than satisfying, this won’t be a fit.
- If you’d rather build production product features than internal tooling and demo systems, you’ll likely want a different engineering role.