About Avoca

Avoca is transforming how home service companies engage with their customers. Our AI-powered conversational agents handle every high-value inbound call, from booking jobs, qualifying leads, and driving higher revenue, all at a speed and consistency unmatched by human call centers.

We're a Series B startup backed by Kleiner Perkins, Meritech Capital, General Catalyst, and other top-tier investors, with $125M raised and a $1B valuation. We grew 10x in 2025 and have scaled to 170+ employees in under two years across our NYC headquarters and Santa Barbara office.

In a $1T+ market where 85% of missed calls go to competitors, we're building the category-defining platform for AI-driven customer engagement, serving the largest brands in home services. With high-energy, in-office teams in both locations, every hire here has an immediate and visible impact.

About the Role

As a Field Engineer on the Pre-Sales team, you'll be the technical builder behind how we win and enable deals. You'll own two things: the integration work that proves technical feasibility to prospects and partners during the sales cycle, and the demo tooling that lets the entire go-to-market team tell a credible, product-accurate story.

You'll work at the intersection of Sales, Partnerships, Product, Engineering, and AI, partnering with Account Executives and the Partnerships team as their technical counterpart. Unlike our Sales Engineers, who lead the customer-facing technical narrative, this role goes a layer deeper on the build: you're the person who can actually stand up a working integration against an unfamiliar API and turn it into a repeatable demo asset. This is a pre-sales role: you won't carry a closing quota, but your work directly determines whether technical buyers and integration partners trust that Avoca does what we say it does.

What You’ll Do

• Own technical scoping and feasibility for pre-sales opportunities and partner integrations; turning ambiguous requirements from prospects, partners, and AEs into concrete, working implementation plans.

• Build working integrations against third-party APIs, CRMs, field service management (FSM) platforms, telephony systems, and partner ecosystems, writing real code, handling REST APIs, JSON, authentication, and webhooks, and getting a credible proof of concept working quickly.

• Build and maintain the demo and sandbox tooling the GTM org relies on: reusable demo environments, representative fixture data, and internal tools, treating one-off deal builds as reusable assets (integration patterns, reference implementations, scripts) rather than throwaway work.