Founding Growth Lead - Marketing and Developer Growth
Marketing & Communications, Software Engineering, Sales & Business Development
Toronto, ON, Canada · Remote
About Sapien
Sapien is building Proof of Quality (PoQ), a verification layer for AI work. As AI does more of the world's work, the hard question is no longer whether the work got done. It is whether the work is good, and whether anyone can prove it. Most quality claims run on trust. PoQ makes them verifiable: customers author a rubric, expert and agentic reviewers score the output, and consensus produces a Proof Report, a portable record of what was reviewed, how it was judged, and how it scored.
The role
You will be our first dedicated growth hire, and you will own the growth engine end to end: community, developer adoption, content, funnels, campaigns, and the automation that ties them together. This is not a brand marketing role. You think in systems and experiments, ship fast, measure everything, and have the judgment to make all of it feel good.
You should be technical enough to wield AI tools, automation platforms, scraping and enrichment, CRMs, analytics, and landing page builders to build a growth machine that compounds. Roughly: one campaign idea becomes a system that researches, creates, distributes, measures, and improves itself.
The deal is simple: we set the what, you own the how. Each quarter we agree on a small set of growth targets with you. Channels, tactics, tools, and sequencing are entirely yours. You will not be judged on activity, effort, or how impressive the machine looks. You will be judged on whether the numbers moved.
Taste is the bar
We can teach tools. We cannot teach taste. Everything you ship shapes how developers, reviewers, and buyers perceive Proof of Quality, so taste matters as much as any technical skill here. Concretely:
-You know what is good, what is cringe, and what is forgettable before the data comes in.
-Your writing and campaigns feel sharp and credible to technical people, never templated.
-You know when polish matters and when speed matters more, and you are usually right about which is which.
-You kill your own work when it is not landing.
-A growth machine that produces high volume, tasteless output is a liability. We want volume and taste, in that order of difficulty.
Who this is for
We hire for trajectory, not tenure. You do not need ten years of experience or a famous logo on your resume. A hungry early career operator with taste and real output beats a polished marketer who waits for permission, every time. What you do need: technical aptitude, daily fluency with AI tools, a data habit, high agency, and proof you have grown something real.
What you will own
1.) The growth system. Build repeatable, AI powered workflows for research, content, distribution, outbound, and measurement. Automate what should be automated, and know what should not be.
2.) Community. Grow active communities across X, Discord, Telegram, LinkedIn, Reddit, and wherever AI and crypto builders actually live. The goal is active contributors, reviewers, developers, and believers, never vanity followers.
3.) Developer adoption. Make PoQ easy to understand and try: docs campaigns, demos, tutorials, example integrations, GitHub presence, hackathon support.
4.) Funnels and analytics. Own the journey from attention to signup to activation to contribution to referral, and the dashboard that tracks it. Every experiment gets measured.
5.) The content engine. Founder content, technical explainers, threads, newsletters, video, SEO. High output at a consistently high bar, powered by AI and edited by you. Through it, teach the market why AI work needs verification and why quality should be measurable and portable.
6.) Enterprise pipeline. Automated, personalized outbound to AI labs, agent companies, and data teams that need verification: enriched lead lists, landing pages, demos, lead scoring.
As the machine starts working, you will build a small bench of contractors and creators to scale it. The job is building the machine, not just personally completing tasks.
What we look for
-Proof you grew something real: a community, audience, developer ecosystem, funnel, launch, or revenue channel. Numbers over narratives.
-Fluent daily use of Claude, ChatGPT, and the current AI toolchain for real work, not novelty.
-Enough technical depth to build automations, funnels, dashboards, and pipelines yourself. Dangerous with tools like Zapier or n8n, Clay, Webflow or Framer, Mixpanel or -Amplitude, and a modern CRM. Comfortable with APIs and basic scraping.
-Developer empathy. You know developers trust clear docs, working demos, and low friction onboarding, and distrust everything else.
-Crypto fluency is a strong plus. Sapien has a token aligned ecosystem, so experience with communities, incentives, quests, and onchain culture helps.
-Speed. You launch, measure, and iterate weekly. You do not wait for perfect process.
How you will be measured
This role has a scoreboard. The specific targets get set together each quarter, but they will always be output metrics in four categories:
1.) Developer adoption. Developers who integrate and activate, not signups or stars.
Reviewer and contributor growth. Qualified, active reviewers in the network, not registrations.
2.) Enterprise pipeline. Qualified conversations and pipeline created with AI labs, agent companies, and data teams.
3.) Community activation. Members who contribute, refer, or build, not follower counts.
If those numbers move quarter over quarter, you are succeeding. If they do not, no amount of shipped content or elegant automation changes that. If being measured this way excites you rather than scares you, keep reading.
The first 90 days
Day 90 is when the scoreboard goes live. By then you should have a growth dashboard with the core funnels instrumented, AI powered content and outbound workflows running, a weekly experiment cadence shipping, early movement in developer activation and community growth, and a clear read on which channels win. From that baseline we set the first quarterly targets together. The first 30 days are for auditing what exists, sharpening the PoQ narrative for each audience, and shipping the first workflows. After that, everything is scale and iteration.
How to apply
Show us the doing. Send two or three examples of things you actually grew: the starting point, the result, the timeframe, and what you personally owned. Screenshots of dashboards, funnels, and systems beat prose.
Then one more thing, and it matters most. Pick anything Sapien has put into the world, tell us what you would improve, and show us a rough version of the fix. This is the taste test. Lead with the work you are proudest of.