About the role
Eightfold AI is building the growth engine for a new generation of AI-native products aimed at a fast-growing customer segment. This is a build role: there is no existing playbook, only early market signal. You'll also own scaling our enterprise pipeline motion with rigor, using an internal pipeline quality methodology to ensure volume growth doesn't come at the expense of pipeline health. This is a high-impact leadership role for a growth marketing leader who has built a net-new acquisition motion from scratch before — not just scaled an existing one — and who operates with genuine fluency in AI-native tooling, not just familiarity with it. You'll lead a team spanning campaigns, marketing operations, paid media, and field marketing, and you'll operate inside a marketing organization that is actively transforming into an AI-first function. The ideal candidate is a builder first and an optimizer second: someone comfortable defining structure where none exists, translating thin signal into a repeatable engine, and holding a quality bar even while scaling volume aggressively.
What You'll Do Build a Net-New Growth Engine Build a repeatable customer acquisition engine for an emerging product line and customer segment, starting from early market signal rather than an established playbook Partner closely with a dedicated sales motion to define target accounts, messaging, and go-to-market sequencing for this new engine Treat the first 90 days as diagnostic: assess what's working today, what needs to be built from zero, and where
the team's current tooling and skills fall short Scale Core Pipeline With Discipline Own and scale enterprise pipeline volume significantly while holding or improving pipeline quality against an internal scoring methodology — volume growth that erodes quality is not success Continuously diagnose the funnel using real signal (deal-level intelligence, not just top-line conversion rates) to find where quality gaps actually live Operate as an AI-First Team Bring AI-native, agentic tooling into day-to-day team workflows as the operating standard, not an experiment Have a clear point of view on how agentic tools change team structure, headcount needs, and workflow design — this should come from direct experience, not enthusiasm alone Build a culture where
