Sales Engineer

Hatch’s engineering culture thrives on speed, ownership, and impact. We’re a small, ambitious team building AI that transforms how service businesses grow, and we move fast. Engineers own problems end-to-end, ship to production early, and work across a modern stack on problems that directly shape the customer experience. At the end of the day, we’re here to build something that matters, grow as engineers, and do it together.

What You’ll Do

• Co-own discovery calls with the Account Executive (AE) to surface integration requirements early, before they become deal risk. Own the discovery motion for integrations, including CRM/system of record, lead source & attribution, scheduling workflows, call center systems, data syncs, webhooks, API access, automation requirements, reporting needs, and edge cases. Lead technically complex demos involving third-party integrations.

• Scope CRM, lead source, API capabilities and constraints, and overall integration complexity for every late-stage deal. Evaluate APIs, review technical documentation, and determine integration feasibility and effort. Deliver a written complexity tier after qualification and produce the Technical Scope document at close, which serves as the blueprint for onboarding. Advise the AE on technical risk, feasibility, and pricing implications before proposals go out.

• Hand off the Technical Scope to onboarding with a live walkthrough—no critical gaps discovered post-handoff. Work with the Forward Deployed Engineer and Account Manager to ensure technically complex accounts are onboarded successfully (4–8 weeks); you’re the primary technical owner through go-live.

• Participate in a post-launch technical health check on every account you led. Work with the post-sales team to maintain a QA checklist covering data sync accuracy, integration error monitoring, and scope drift identification.

• Stay current on product updates, new integrations, and capability changes. No deal should be lost because your knowledge was stale. Build and own the integration discovery question set—keep it current and usable by the broader sales team.

What It Takes to Succeed

• Question assumptions. If something’s been done a certain way because it always has been, test it. Stack-rank your initiatives—weigh upside against effort, share the reasoning.

• Work with Operations to ensure critical metrics (integration error rates, onboarding cycle time, scope accuracy) are monitored. If you can’t measure it, escalate it. Know enough SQL to pull your own data on deal complexity, onboarding performance, and integration health.

• Feed learnings back to Product and Engineering—you’re closer to the customer’s real environment than almost anyone.

• Flag technical risk in deals before the AE asks—don’t wait. When a scoping decision involves a tradeoff between deal velocity and technical risk, surface it explicitly—don’t make that call unilaterally.

• Communicate tradeoffs clearly to all audiences: Sales (deal risk), customers (realistic expectations), Product and Engineering (patterns and constraints). Send status updates at key milestones—thorough on drivers, clear on the key signal, and always include a recommended next step.