GTM Engineer

At Maple, we’re building AI agents that work for restaurants. These agents answer calls, take orders, book appointments, and handle real customer interactions over natural voice.

But our bigger mission goes deeper: we’re building automated ontologies that model how businesses actually operate — their services, workflows, constraints, and language — so our agents can adapt to them instantly. We meet businesses where they are, not where software wants them to be.

We have many customers, strong revenue growth, years of runway, and backing from world-class investors. I’ll share more once we meet.

You will own the revenue-generating systems at Maple end-to-end. That means the pipes that feed leads in, the tools reps use to close them, the experiments we run to figure out what works, and the plumbing that tells us whether any of it is actually moving the business. Some of this is plumbing. Some of it is experimentation. Some of it is product-adjacent rep-facing tooling. All of it is high-leverage, and all of it is measurable.

• →

  Build and automate pipelines that close loops from the top of the funnel for any channel to closed-won revenue.

• →

  A rep tooling layer that makes a Maple AE genuinely faster than an AE at any other company.

• →

  Work with sales, marketing, and ops to solve bottlenecks and unlock growth

• →

  Keep our data clean and systems running smoothly

• →

  Prototype, test, and roll out new tools and automations

• →

  Whatever other system needs to exist six months from now that neither of us has thought of yet. You'll find them. That's half the job.

• 1–3 years in a technical, ops, or growth role

• Gets excited by the business problem underneath the engineering problem.

• Has a reasonable amount of context on, or genuine curiosity about, how modern GTM actually works. You've at least heard of cold outbound, attribution, PLG, partner channels, SDR motions.

• Operates with zero hand-holding. You don't ask "what should I build next", you show up with three options and an opinion on which is right.

• Writes code that ships, not code that architects. When you see a problem, your instinct is to build the scrappy 40% solution, measure it, and iterate and not to design the perfect system first.

• Uses modern tools (Claude, Cursor, Linear, whatever) fluently and without shame.

• If you're not sure whether you're qualified, apply anyway — we hire on trajectory and wiring, not pedigree.

• We optimize for leverage. That means great internal tooling, fast CI/CD, and code that scales across many customer types

• We believe in deep ownership. Engineers here talk to users, design features, and ship fast

• We value clarity over process. You’ll spend most of your day building, not waiting on decisions

• We move in person. We’re a tight-knit team that moves fast and solves problems together