Marking Lead, Growth

About Sumble

Sales teams don't need more contacts, they need more context. Sumble shows go-to-market teams what's happening inside the accounts they sell to: the technologies they use, the teams and people behind them, and the projects they're investing in. We turn public, traceable evidence into account intelligence that helps go-to-market teams size markets, build territories, prioritize accounts, and reach the right people with a useful point of view.

Customers like Snowflake, Figma, Elastic, Wiz and Vercel rely on us, and we've raised $38.5M from Coatue and Canaan. Now, we're building the marketing function to match the product, and you'll be a foundational hire on that team.

Why this role matters now

Sumble reaches customers through the web app, our API, CRM integrations, and an MCP server that lets AI agents work directly with Sumble data. Every one of those paths needs to be measured, tested, and grown. Today that work is split across the team. This seat brings it under one owner.

This is a core seat on the new marketing team. We want an engineer-minded marketer who treats growth as a system: you'll design the experiments, work closely with product and engineering, and decide with data what to scale and what to kill.

It's a senior individual contributor role with no direct reports, and we're hiring it that way on purpose. You'll have full ownership of the growth number, a real budget for paid media and tools, and the authority to change what doesn't work.

Our team

We're a team of over 40 across product, design, engineering, data science, marketing, customer success, and sales, with experience at companies such as Google, Meta, Stack Overflow and Snowflake. You'll work alongside our marketing leads for Campaigns & Experiences, Product Marketing and Content, and closely with Sales, RevOps, Product and Engineering.

What you'll own

Email and growth loops (automated)

Own lifecycle end to end: 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 loops that turn existing users into new users and pipeline.

Build these as systems, not campaigns. They should be triggered by product and account signals, run without you, and be instrumented so you know what each one is worth.

Keep the email stack deliverable, clean, and wired to the CRM.

Paid media (you own it)

Own paid acquisition across channels (LinkedIn, search, retargeting, and whatever earns its budget next): strategy, targeting, creative testing, budget pacing, and cost per pipeline.

Use Sumble's own account intelligence to aim spend at the accounts and people that matter, and prove it with holdouts and pipeline data, not clicks.

Direct agency and freelance partners, and decide what stays outsourced and what you bring in-house or automate.

GTM stack

Own marketing's GTM systems: lead routing and booking, enrichment, website visitor identification, UTMs and conversion tracking, and the data feeding our dashboards.

Own attribution from first touch to closed-won. Partner with internal ops on Salesforce (campaign architecture, lead and contact flow, funnel definitions) so leadership trusts the numbers.

Prototype internal GTM tools on Sumble's own data and API. Ship the ones that earn their keep, retire the ones that don't, and document what stays.

Website strategy and conversion

Own the website as a growth surface: information architecture, conversion paths, signup and demo flows, and pricing-page and landing-page experiments.

Run a standing conversion-test program. Our Content lead owns the words and our designer owns the visual system; you own what we test, how we measure it, and what ships.

Ship pages and changes yourself without waiting in an engineering queue.

Experimentation and measurement

Run a weekly test cadence across paid, lifecycle, web and product-adjacent surfaces. Every test has a hypothesis, a metric, a sample size and a kill date.

Keep a shared experiment log: what we tried, what happened, and what we decided.

Report weekly on the funnel in a form the founders and Sales can act on.

Requirements

• Must-haves
• 5+ years in growth marketing, growth engineering, or a technical demand role at a B2B SaaS, data, or developer-tools company, ideally one with both self-serve and sales-led motions.
• Engineering-fluent. You're comfortable working with product, engineering and development teams, you know how they work, and you've experimented heavily.
• AI-native in practice. You build with LLMs and agents (Claude, Cursor, Claude Code, MCP or similar) and can show us workflows or tools you shipped and still use.
• Highly experimental, with receipts. You can walk us through tests you designed, what you learned, what you scaled, and what you killed.
• You've owned paid media with real budget and can talk about cost per pipeline, not just CPC.
• You've built lifecycle or growth loops as systems, and you understand CRM data models (Salesforce or HubSpot), routing and attribution well enough to fix them.
• You make decisions with data and explain them clearly to founders, Sales and non-technical teammates.
• A Super IC operating style. You prioritize ruthlessly and work without waiting for permission.
• Nice-to-haves
• Experience selling to technical GTM buyers: RevOps, GTM engineers, sales or marketing ops.
• Hands-on with tools like Clay, plus product analytics and experimentation platforms.
• Experience growing API or usage-based products, or developer adoption of a technical product.
• You've shipped production front-end work: landing pages, signup flows, CMS builds.
• A public body of work: repos, posts or teardowns of experiments you've run.
• How we work
• AI is part of how everyone at Sumble works. We expect you to keep experimenting with new tools and share what's working so the whole team gets better.
• Small team, a lot of ownership. You'll take problems from open-ended to shipped and have direct conversations instead of waiting on approval chains.
• No black boxes. We make it clear where our data comes from. Your reporting should be held to the same standard.
• We dogfood. Our own GTM should be the best example of Sumble in production.
• Builders over briefers. We'd rather see the prototype than the deck.
• Our hiring process includes a practical project.