Solutions Engineer

This is a new role on the Engineering team, created to own the API layer end-to-end.. You'll sit at the intersection of Sales, Implementation, and Support: brought in early on API and web app deals to scope feasibility, owning SOW review for API/web app implementation scope, and serving as the go-to API expert for Support when tickets need deeper technical context. API customers are among our highest-retention, lowest-support-load accounts, and this role exists to protect and grow that.

You're a technical, client-facing professional who's comfortable being the person in the room translating between a customer's integration needs and what our platform can actually do. You don't need to be a deep backend engineer — what matters is that you can read and reason about an API, scope an implementation honestly, and communicate clearly and confidently with clients throughout a sales or implementation cycle. You're a self-starter: this role isn't fully defined yet, and you'll help shape it as you go.

• Get involved early in the sales process on API and web app deals to assess technical fit and scope

• Own SOW review for API and web app implementation scopes

• Support the implementation of API and web app customers

• Serve as the escalation resource for API-related Zendesk tickets, closing the current API knowledge gap in Support

• Act as a resource for upselling and solutioning conversations with existing API customers

• Coordinate across Sales, Implementation, Engineering, and Support to keep API-related commitments visible and on track

• 3+ years in a Solutions Engineer, Sales Engineer, or similar pre-sales role in B2B SaaS

• Working familiarity with APIs and integrations — able to scope integration requirements and speak credibly to technical stakeholders, without needing deep backend engineering depth

• Experience scoping or reviewing statements of work (SOW) with clients

• Strong written and verbal communication skills; comfortable being customer-facing from day one

• Comfortable operating with ambiguity in a role that's still being defined

• Customer-retention minded — sees API customers as a relationship to protect, not just a ticket queue

• Self-starter, able to bring structure to a role without much existing precedent

• Strong cross-functional communicator; equally at ease with clients, sales, and engineers