Forward-Deployed Engineer, API

Forward-Deployed Engineer, API — Vector

Location: Boston, MA (Hybrid) ·
Stage: Seed → Series A ·
Reports to: Head of Engineering

Vector is a contact-level advertising platform built for B2B demand generation teams who are tired of paying Linked In to show ads to people who will never buy from them.

We let marketers build ad audiences from real, verified contacts — people actively visiting their site, engaging with their brand, or researching competitors right now. Then we sync those audiences directly to Linked In, Meta, Google, Reddit, and more. The result: less spend on noise, more spend on actual buyers.

We went through Y Combinator, we're backed by serious investors, and we're preparing for a Series A. The core platform has product-market fit. Now we need someone to own what comes next.

Vector's API product exists — and it's working. Customers are integrating with it. Revenue is coming in. But right now it's being supported off the side of three people's desks, none of whom can give it the attention it deserves.

This is the hire that changes that.

You'll be the first person fully dedicated to our API product — owning everything from the technical onboarding experience to the SDK and documentation to scoping new integrations with prospects. You're not joining a team. You're building the foundation for one.

This role sits at the intersection of engineering, product, and go-to-market. Some days you'll be writing code. Other days you'll be on a call walking a customer's engineering team through an integration. Other days you'll be shaping the roadmap based on what you're hearing in the field. If you need a clean swim lane to be productive, this isn't for you.

If you like owning something end-to-end and making it real, keep reading.

API product ownership You'll be the internal owner of the API product — its roadmap, its reliability, and its trajectory. You'll work closely with engineering and leadership to prioritize what gets built, and you'll have the technical chops to build some of it yourself. This isn't a PM role where you write tickets and wait. You ship.

Technical onboarding and integration support When a customer is integrating with our API, you're the person making sure it goes well. You'll guide their engineering teams through implementation, troubleshoot issues, and build the tooling and processes that make onboarding repeatable — not a fire drill every time.

Developer enablement Our docs, SDKs, and developer experience need an owner. You'll build and maintain the resources that let customers self-serve where possible and get unstuck fast when they can't. If you've ever been frustrated by bad API documentation, this is your chance to build what you wished existed.

Pre-sales technical scoping You'll join sales conversations when there's a technical integration to scope — understanding the prospect's stack, defining what the integration looks like, and giving the team an honest read on complexity and feasibility. You're not carrying a quota, but your ability to translate between business value and technical implementation will directly influence revenue.

Feedback loop to product and engineering You'll be closer to API customers than anyone in the company. That means you're the one surfacing patterns — what's breaking, what's missing, what would unlock the next wave of adoption. You'll turn field signal into product direction.

You can code and you can communicate. This role requires both. You're comfortable writing production-quality code, and you're equally comfortable explaining a technical concept to a non-technical stakeholder or hopping on a call with a customer's senior engineer. People who are strong at one but not the other won't thrive here.

You've worked on developer-facing products. You understand what makes a good API, a good SDK, and a good developer experience. You've either built these things or been close enough to have strong opinions about how they should work.

You've operated in ambiguity. This product doesn't have a playbook yet. You're the person who writes it. You've worked at a startup or in an environment where…