Marking Lead, Growth

Sumble Inc

13d

About The Position

Sumble is hiring a foundational marketing-team member to own growth across its web app, API, CRM integrations, and MCP server. This senior individual-contributor role has no direct reports and carries ownership of the growth number, with a budget for paid media and tools and authority to change what is not working. The role partners closely with Product, Engineering, Sales, RevOps, and marketing leads. The lead will own automated lifecycle email and growth loops, paid acquisition, marketing GTM systems and attribution, website strategy and conversion, and a weekly experimentation and measurement program. The work is expected to be built as measurable, repeatable systems, with decisions guided by pipeline and other meaningful data. The position is suited to an engineering-minded, highly experimental marketer who can prototype and ship, including front-end and internal GTM tools, while communicating results clearly to founders, Sales, and non-technical teammates. Sumble is a team of over 40 across product, design, engineering, data science, marketing, customer success, and sales. Its working principles include experimenting with AI tools, taking ownership from open-ended problem to shipped outcome, transparency about data, using Sumble internally, and favoring prototypes over decks. The hiring process includes a practical project.

Requirements

At least 5 years of experience in growth marketing, growth engineering, or a technical demand role at a B2B SaaS, data, or developer-tools company; experience with both self-serve and sales-led motions is ideal.
Engineering-fluent and comfortable working with product, engineering, and development teams; a strong record of experimentation.
Practical AI-native experience building with LLMs and agents such as Claude, Cursor, Claude Code, or MCP, with workflows or tools shipped and still in use.
Highly experimental, with the ability to explain tests designed, lessons learned, what was scaled, and what was stopped.
Experience owning paid media budgets and discussing cost per pipeline, not only CPC.
Experience building lifecycle systems or growth loops and strong understanding of CRM data models, routing, and attribution sufficient to fix them.
Ability to make data-informed decisions and explain them clearly to founders, Sales, and non-technical teammates.
A highly autonomous individual-contributor working style, including ruthless prioritization and the ability to work without waiting for permission.

Nice To Haves

Experience selling to technical go-to-market buyers, including RevOps, GTM engineers, Sales Ops, or Marketing Ops.
Hands-on experience with tools such as Clay, as well as product analytics and experimentation platforms.
Experience growing API or usage-based products or developer adoption of a technical product.
Production front-end experience, such as building landing pages, signup flows, or CMS implementations.
A public body of work, such as repositories, posts, or teardowns of experiments.

Responsibilities

Own lifecycle email end to end, including onboarding, activation, product-update, upgrade, and re-engagement flows for self-serve signups, API and MCP users, and event attendees.
Design and ship referral and other compounding growth loops that generate new users and pipeline.
Build automated, signal-triggered growth systems and instrument their value; maintain email deliverability, list quality, and CRM integration.
Own paid acquisition strategy across channels, including targeting, creative testing, budget pacing, and cost per pipeline.
Use Sumble account intelligence to target paid spend and evaluate it using holdouts and pipeline data.
Manage agency and freelance partners and determine which work to outsource, bring in-house, or automate.
Own marketing GTM systems, including lead routing and booking, enrichment, website visitor identification, UTMs, conversion tracking, and dashboard data.
Own attribution from first touch through closed-won and partner with internal operations on Salesforce campaign architecture, lead and contact flow, and funnel definitions.
Prototype internal GTM tools using Sumble data and API, ship useful tools, retire ineffective ones, and document what remains.
Own the website as a growth surface, including information architecture, conversion paths, signup and demo flows, and pricing-page and landing-page experiments.
Run an ongoing conversion-test program, determining what to test, how to measure it, and what to ship in collaboration with Content and Design.
Ship website pages and changes directly without waiting in an engineering queue.
Run weekly experiments across paid, lifecycle, web, and product-adjacent surfaces, each with a hypothesis, metric, sample size, and kill date.
Maintain a shared experiment log and report weekly on the funnel in a way founders and Sales can act on.