Senior Growth Marketing Manager
Prefect · United States · 1 wk ago
RemoteRemoteMarketing$173k–$222k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- Intro about company (Prefect builds...). Could be "About the role" or maybe "About the company". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" for intro summary.
- Role Summary: description of audience, FastMCP, etc. Could be part of About the role.
- What You'll Do: list of responsibilities. Use - .
- Your Qualifications: list of must-have qualifications. Use
- .
- Nice to have: could be part of Qualifications or separate Skills? Could be "Skills" section.
- Who This Role Is Not For: maybe not needed; could be omitted as not a standard heading? Might be considered part of Qualifications? But it's specific content; we could include as a section "Who This Role Is Not For" but not in the list of allowed headings. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use for section headings (e.g. ...)" implying those are examples; we could still use other headings if needed, but better to stick to those. However "Who This Role Is Not For" could be placed under Qualifications or maybe as a note. But we need to preserve ALL substantive information; we cannot drop it. Could incorporate into Qualifications as a bullet? Might be okay.
- What You'll Get In Return: includes Base Salary Ranges, Perks and Benefits, Belongingness at Prefect, Equal Opportunity at Prefect, Brad note, Compensation Range. We need to include Benefits and Pay sections if posting actually states them. It does state salary ranges and benefits. So we need a Pay section (maybe "Pay") and Benefits section. Also maybe "Schedule"? Not mentioned; remote-first, time zones: Anywhere in continental US. That's schedule info? Could be considered schedule? It mentions time zones and remote-first. Could be a Schedule section. But we should only create Schedule if posting actually states them. It does mention "Time zones: Anywhere in the continental US. We're remote-first." That's schedule/location info. Could be placed under Schedule. However the instruction says prefer a few substantive sections over many thin ones. Might combine location/time zone into About the role or Benefits? But schedule is separate. Might be okay to have Schedule section with that info.
We need to avoid boilerplate: EEO, belongingness, equal opportunity, Brad note, etc. Those are boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove Belongingness at Prefect, Equal Opportunity at Prefect, Brad is a real live person note. Also remove "Compensation Range: $154K - $222K" maybe duplicate of salary ranges? It's duplicate; we can drop.
We need to preserve all substantive information: company vision/mission, remote-first culture, role summary, responsibilities, qualifications, nice-to-have, who this role is not for (maybe keep as note), salary ranges, benefits list.
We need to format as HTML fragment only.
Let's decide sections:
- About the role
: include company intro, vision/mission, remote-first culture, role summary (audience, FastMCP, etc). Could be a few paragraphs.
- Responsibilities
: list of what you'll do (bullet points). Use - .
-
Qualifications
: must-have qualifications bullet list.
- Skills
: nice-to-have bullet list.
- Pay
: salary ranges per location.
- Benefits
: list of perks and benefits.
- Schedule
: time zones/remote-first.
We must avoid filler like "commensurate with experience". Not present.
We must not repeat job title.
We must not include Job ID.
We must not include application instructions.
We must not include EEO etc.
Let's extract substantive content.
Company intro:
"Prefect builds and operates resilient, Pythonic orchestration and MCP platforms -- Prefect OSS, Prefect Cloud, FastMCP OSS, and Horizon -- used for mission-critical workloads. Our Vision: Prefect will define automation for the context era. Our Mission: Curate an intelligent context layer that delivers the right information at the right time. Our remote first company is singularly focused on this vision and mission, and every team member directly contributes to their advancement. We've carefully created a supportive, high-performance culture - the operating system of our company - that empowers our team to do the best work of their careers and achieve their personal and professional aspirations. Our company operates both open-source and commercial offerings, partnering with Fortune 500 companies, data innovators, and fast-growing digitally native startups. We are looking for folks who want to join a remote-first team to continue building an equally amazing company, product, and developer community."
Role Summary:
"We have an audience most companies our size would be thrilled to have. FastMCP is the leading Python framework for building MCP servers, with 27,000+ GitHub stars and a docs site developers read start to finish. PyAI, the practitioner community we founded, went from small meetups to a 600-person conference. Prefect's open-source orchestrator has been trusted by data teams for years. This year we acquired Dagster, which brings a second large open-source community with us. With that opportunity in mind we decided to expand our team by hiring a Sr Growth Marketing Manager. You will own the path from audience to signup to activated user to qualified pipeline, across Prefect, Horizon, and the Dagster funnels. That means attribution, lifecycle and email, paid and organic acquisition, CRO and experimentation. You'll have budget and a number to hit. You'll report to our Chief Growth Officer and work daily with the rest of the Marketing, Sales and Engineering organizations. Time zones: Anywhere in the continental US. We're remote-first. We have a slight preference for candidates near New York, the Bay Area, or Washington D.C., where our spaces and most of our events are, but it isn't a requirement."
What You'll Do (Responsibilities):
"In your first year you will:
- Expand Our Brand Awareness and Pipeline Generation.
- Own paid and organic acquisition end to end: budget, channel mix, landing pages, and CRO.
- Make our funnels scalable and predictable.
- Build funnels/loops and models for our highest-priority motions (FastMCP to Horizon, Horizon self-serve signup to activation, website to inbound, open source to Cloud) with owners, baselines, and conversion targets.
- Own lifecycle. Design and ship the onboarding, activation, and re-engagement sequences that don't exist yet, starting with the thousands of Horizon signups who've never heard from us.
- Measure activation lift, not open rates.
- Experiment fast. Organize campaign taxonomy, UTM discipline, and a clean handoff from HubSpot into Salesforce so we can run multiple experiments to optimize our funnel.
- Report cost per activated user and pipeline per dollar, and kill what doesn't work quickly and out loud.
- Route the audience to the product. Turn FastMCP's developer audience into Horizon accounts through in-product paths, docs placements, end cards, and CTAs. This is the highest-leverage number in the role."
Qualifications (Must have):
"Must have 7+ years in growth or demand generation at B2B SaaS or developer-focused companies, with hands-on ownership throughout.
You've been the person in the tool, not the person briefing someone who's in the tool.
You know how to use channels and campaigns to generate predictable pipeline for sales and self serve signups.
You've owned an acquisition budget and reported honestly on what it returned, including the parts that didn't work.
You've built attribution from close to nothing before: campaign taxonomy, UTM structure, and a funnel model leadership used to make decisions.
HubSpot and Salesforce, or close equivalents.
Lifecycle ownership with measured results.
Onboarding and activation sequences where you can tell us the before-and-after conversion numbers, and what you learned when one of them failed.
Comfort being the only person in your function. You'll pick the sequence, say no to good ideas, and ship without a team behind you."
Nice to have (Skills):
"Background at an open-source or developer-tools company.
You know why a GitHub star isn't a lead, and you've dealt with the particular weirdness of marketing to engineers.
SQL, and comfort living in a BI tool.
Our stack is HubSpot, Salesforce, Amplitude, Common Room, and Omni.
Experience running a product-led self-serve funnel alongside an enterprise sales-led motion without one cannibalizing the other.
You've integrated two marketing stacks after an acquisition and lived to tell about it."
Who This Role Is Not For (maybe keep as a note under Qualifications or separate). Could be a short paragraph.
"We'd rather you rule yourself out now than be unhappy in six months.
You want to manage a team soon. This is an individual contributor role and will stay one for at least a year. If it grows into a team later, good, but don't take this job expecting that.
You need clean data before you'll commit to a number. Some of our plumbing is broken. You'll fix it while also being accountable for outcomes. Those happen at the same time.
You prefer to work through an agency. You can use contractors for execution. The thinking and most of the building will be yours.
You want a stable roadmap. We merged with another company this year, we're validating a new product direction, and priorities move. If that reads as chaos rather than opportunity, this will be a frustrating job."
Pay:
"Base Salary Ranges:
San Francisco Bay Area & NYC Metro: $173,000–$222,000
Washington D.C., Boston, LA Metro, Seattle: $162,000–$201,000
Denver, Chicago, Atlanta, & all other U.S. metros: $154,000–$200,000
Actual base salary within each range depends on the candidate's location, experience, and qualifications.
Please keep in mind that equity and benefits are not included in the range provided above.
Your recruiter can share more about the salary range for your preferred location during the hiring process."
Benefits:
"Perks and Benefits:
Remote-first team with flexible-first culture
Equity Stock Options
401(k) with 5% company match (vests immediately!)
Unlimited PTO
Medical, Dental and Vision insurance
Generous Parental Leave
Life Insurance and Disability benefits
$800/month remote work
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key sections: - Intro about company (Prefect builds...). Could be "About the role" or maybe "About the company". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" for intro summary.
- Role Summary: description of audience, FastMCP, etc. Could be part of About the role.
- What You'll Do: list of responsibilities. Use - .
- Your Qualifications: list of must-have qualifications. Use
- .
- Nice to have: could be part of Qualifications or separate Skills? Could be "Skills" section.
- Who This Role Is Not For: maybe not needed; could be omitted as not a standard heading? Might be considered part of Qualifications? But it's specific content; we could include as a section "Who This Role Is Not For" but not in the list of allowed headings. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use for section headings (e.g. ...)" implying those are examples; we could still use other headings if needed, but better to stick to those. However "Who This Role Is Not For" could be placed under Qualifications or maybe as a note. But we need to preserve ALL substantive information; we cannot drop it. Could incorporate into Qualifications as a bullet? Might be okay.
- What You'll Get In Return: includes Base Salary Ranges, Perks and Benefits, Belongingness at Prefect, Equal Opportunity at Prefect, Brad note, Compensation Range. We need to include Benefits and Pay sections if posting actually states them. It does state salary ranges and benefits. So we need a Pay section (maybe "Pay") and Benefits section. Also maybe "Schedule"? Not mentioned; remote-first, time zones: Anywhere in continental US. That's schedule info? Could be considered schedule? It mentions time zones and remote-first. Could be a Schedule section. But we should only create Schedule if posting actually states them. It does mention "Time zones: Anywhere in the continental US. We're remote-first." That's schedule/location info. Could be placed under Schedule. However the instruction says prefer a few substantive sections over many thin ones. Might combine location/time zone into About the role or Benefits? But schedule is separate. Might be okay to have Schedule section with that info.
We need to avoid boilerplate: EEO, belongingness, equal opportunity, Brad note, etc. Those are boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove Belongingness at Prefect, Equal Opportunity at Prefect, Brad is a real live person note. Also remove "Compensation Range: $154K - $222K" maybe duplicate of salary ranges? It's duplicate; we can drop.
We need to preserve all substantive information: company vision/mission, remote-first culture, role summary, responsibilities, qualifications, nice-to-have, who this role is not for (maybe keep as note), salary ranges, benefits list.
We need to format as HTML fragment only.
Let's decide sections:
- About the role
: include company intro, vision/mission, remote-first culture, role summary (audience, FastMCP, etc). Could be a few paragraphs.
- Responsibilities
: list of what you'll do (bullet points). Use - .
-
Qualifications
: must-have qualifications bullet list.
- Skills
: nice-to-have bullet list.
- Pay
: salary ranges per location.
- Benefits
: list of perks and benefits.
- Schedule
: time zones/remote-first.
We must avoid filler like "commensurate with experience". Not present.
We must not repeat job title.
We must not include Job ID.
We must not include application instructions.
We must not include EEO etc.
Let's extract substantive content.
Company intro:
"Prefect builds and operates resilient, Pythonic orchestration and MCP platforms -- Prefect OSS, Prefect Cloud, FastMCP OSS, and Horizon -- used for mission-critical workloads. Our Vision: Prefect will define automation for the context era. Our Mission: Curate an intelligent context layer that delivers the right information at the right time. Our remote first company is singularly focused on this vision and mission, and every team member directly contributes to their advancement. We've carefully created a supportive, high-performance culture - the operating system of our company - that empowers our team to do the best work of their careers and achieve their personal and professional aspirations. Our company operates both open-source and commercial offerings, partnering with Fortune 500 companies, data innovators, and fast-growing digitally native startups. We are looking for folks who want to join a remote-first team to continue building an equally amazing company, product, and developer community."
Role Summary:
"We have an audience most companies our size would be thrilled to have. FastMCP is the leading Python framework for building MCP servers, with 27,000+ GitHub stars and a docs site developers read start to finish. PyAI, the practitioner community we founded, went from small meetups to a 600-person conference. Prefect's open-source orchestrator has been trusted by data teams for years. This year we acquired Dagster, which brings a second large open-source community with us. With that opportunity in mind we decided to expand our team by hiring a Sr Growth Marketing Manager. You will own the path from audience to signup to activated user to qualified pipeline, across Prefect, Horizon, and the Dagster funnels. That means attribution, lifecycle and email, paid and organic acquisition, CRO and experimentation. You'll have budget and a number to hit. You'll report to our Chief Growth Officer and work daily with the rest of the Marketing, Sales and Engineering organizations. Time zones: Anywhere in the continental US. We're remote-first. We have a slight preference for candidates near New York, the Bay Area, or Washington D.C., where our spaces and most of our events are, but it isn't a requirement."
What You'll Do (Responsibilities):
"In your first year you will:
- Expand Our Brand Awareness and Pipeline Generation.
- Own paid and organic acquisition end to end: budget, channel mix, landing pages, and CRO.
- Make our funnels scalable and predictable.
- Build funnels/loops and models for our highest-priority motions (FastMCP to Horizon, Horizon self-serve signup to activation, website to inbound, open source to Cloud) with owners, baselines, and conversion targets.
- Own lifecycle. Design and ship the onboarding, activation, and re-engagement sequences that don't exist yet, starting with the thousands of Horizon signups who've never heard from us.
- Measure activation lift, not open rates.
- Experiment fast. Organize campaign taxonomy, UTM discipline, and a clean handoff from HubSpot into Salesforce so we can run multiple experiments to optimize our funnel.
- Report cost per activated user and pipeline per dollar, and kill what doesn't work quickly and out loud.
- Route the audience to the product. Turn FastMCP's developer audience into Horizon accounts through in-product paths, docs placements, end cards, and CTAs. This is the highest-leverage number in the role."
Qualifications (Must have):
"Must have 7+ years in growth or demand generation at B2B SaaS or developer-focused companies, with hands-on ownership throughout.
You've been the person in the tool, not the person briefing someone who's in the tool.
You know how to use channels and campaigns to generate predictable pipeline for sales and self serve signups.
You've owned an acquisition budget and reported honestly on what it returned, including the parts that didn't work.
You've built attribution from close to nothing before: campaign taxonomy, UTM structure, and a funnel model leadership used to make decisions.
HubSpot and Salesforce, or close equivalents.
Lifecycle ownership with measured results.
Onboarding and activation sequences where you can tell us the before-and-after conversion numbers, and what you learned when one of them failed.
Comfort being the only person in your function. You'll pick the sequence, say no to good ideas, and ship without a team behind you."
Nice to have (Skills):
"Background at an open-source or developer-tools company.
You know why a GitHub star isn't a lead, and you've dealt with the particular weirdness of marketing to engineers.
SQL, and comfort living in a BI tool.
Our stack is HubSpot, Salesforce, Amplitude, Common Room, and Omni.
Experience running a product-led self-serve funnel alongside an enterprise sales-led motion without one cannibalizing the other.
You've integrated two marketing stacks after an acquisition and lived to tell about it."
Who This Role Is Not For (maybe keep as a note under Qualifications or separate). Could be a short paragraph.
"We'd rather you rule yourself out now than be unhappy in six months.
You want to manage a team soon. This is an individual contributor role and will stay one for at least a year. If it grows into a team later, good, but don't take this job expecting that.
You need clean data before you'll commit to a number. Some of our plumbing is broken. You'll fix it while also being accountable for outcomes. Those happen at the same time.
You prefer to work through an agency. You can use contractors for execution. The thinking and most of the building will be yours.
You want a stable roadmap. We merged with another company this year, we're validating a new product direction, and priorities move. If that reads as chaos rather than opportunity, this will be a frustrating job."
Pay:
"Base Salary Ranges:
San Francisco Bay Area & NYC Metro: $173,000–$222,000
Washington D.C., Boston, LA Metro, Seattle: $162,000–$201,000
Denver, Chicago, Atlanta, & all other U.S. metros: $154,000–$200,000
Actual base salary within each range depends on the candidate's location, experience, and qualifications.
Please keep in mind that equity and benefits are not included in the range provided above.
Your recruiter can share more about the salary range for your preferred location during the hiring process."
Benefits:
"Perks and Benefits:
Remote-first team with flexible-first culture
Equity Stock Options
401(k) with 5% company match (vests immediately!)
Unlimited PTO
Medical, Dental and Vision insurance
Generous Parental Leave
Life Insurance and Disability benefits
$800/month remote work
- .
- Nice to have: could be part of Qualifications or separate Skills? Could be "Skills" section.
- Who This Role Is Not For: maybe not needed; could be omitted as not a standard heading? Might be considered part of Qualifications? But it's specific content; we could include as a section "Who This Role Is Not For" but not in the list of allowed headings. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use
for section headings (e.g. ...)" implying those are examples; we could still use other headings if needed, but better to stick to those. However "Who This Role Is Not For" could be placed under Qualifications or maybe as a note. But we need to preserve ALL substantive information; we cannot drop it. Could incorporate into Qualifications as a bullet? Might be okay. - What You'll Get In Return: includes Base Salary Ranges, Perks and Benefits, Belongingness at Prefect, Equal Opportunity at Prefect, Brad note, Compensation Range. We need to include Benefits and Pay sections if posting actually states them. It does state salary ranges and benefits. So we need a Pay section (maybe "Pay") and Benefits section. Also maybe "Schedule"? Not mentioned; remote-first, time zones: Anywhere in continental US. That's schedule info? Could be considered schedule? It mentions time zones and remote-first. Could be a Schedule section. But we should only create Schedule if posting actually states them. It does mention "Time zones: Anywhere in the continental US. We're remote-first." That's schedule/location info. Could be placed under Schedule. However the instruction says prefer a few substantive sections over many thin ones. Might combine location/time zone into About the role or Benefits? But schedule is separate. Might be okay to have Schedule section with that info. We need to avoid boilerplate: EEO, belongingness, equal opportunity, Brad note, etc. Those are boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove Belongingness at Prefect, Equal Opportunity at Prefect, Brad is a real live person note. Also remove "Compensation Range: $154K - $222K" maybe duplicate of salary ranges? It's duplicate; we can drop. We need to preserve all substantive information: company vision/mission, remote-first culture, role summary, responsibilities, qualifications, nice-to-have, who this role is not for (maybe keep as note), salary ranges, benefits list. We need to format as HTML fragment only. Let's decide sections: -
About the role
: include company intro, vision/mission, remote-first culture, role summary (audience, FastMCP, etc). Could be a few paragraphs. -Responsibilities
: list of what you'll do (bullet points). Use- .
-
Qualifications
: must-have qualifications bullet list. -Skills
: nice-to-have bullet list. -Pay
: salary ranges per location. -Benefits
: list of perks and benefits. -Schedule
: time zones/remote-first. We must avoid filler like "commensurate with experience". Not present. We must not repeat job title. We must not include Job ID. We must not include application instructions. We must not include EEO etc. Let's extract substantive content. Company intro: "Prefect builds and operates resilient, Pythonic orchestration and MCP platforms -- Prefect OSS, Prefect Cloud, FastMCP OSS, and Horizon -- used for mission-critical workloads. Our Vision: Prefect will define automation for the context era. Our Mission: Curate an intelligent context layer that delivers the right information at the right time. Our remote first company is singularly focused on this vision and mission, and every team member directly contributes to their advancement. We've carefully created a supportive, high-performance culture - the operating system of our company - that empowers our team to do the best work of their careers and achieve their personal and professional aspirations. Our company operates both open-source and commercial offerings, partnering with Fortune 500 companies, data innovators, and fast-growing digitally native startups. We are looking for folks who want to join a remote-first team to continue building an equally amazing company, product, and developer community." Role Summary: "We have an audience most companies our size would be thrilled to have. FastMCP is the leading Python framework for building MCP servers, with 27,000+ GitHub stars and a docs site developers read start to finish. PyAI, the practitioner community we founded, went from small meetups to a 600-person conference. Prefect's open-source orchestrator has been trusted by data teams for years. This year we acquired Dagster, which brings a second large open-source community with us. With that opportunity in mind we decided to expand our team by hiring a Sr Growth Marketing Manager. You will own the path from audience to signup to activated user to qualified pipeline, across Prefect, Horizon, and the Dagster funnels. That means attribution, lifecycle and email, paid and organic acquisition, CRO and experimentation. You'll have budget and a number to hit. You'll report to our Chief Growth Officer and work daily with the rest of the Marketing, Sales and Engineering organizations. Time zones: Anywhere in the continental US. We're remote-first. We have a slight preference for candidates near New York, the Bay Area, or Washington D.C., where our spaces and most of our events are, but it isn't a requirement." What You'll Do (Responsibilities): "In your first year you will: - Expand Our Brand Awareness and Pipeline Generation. - Own paid and organic acquisition end to end: budget, channel mix, landing pages, and CRO. - Make our funnels scalable and predictable. - Build funnels/loops and models for our highest-priority motions (FastMCP to Horizon, Horizon self-serve signup to activation, website to inbound, open source to Cloud) with owners, baselines, and conversion targets. - Own lifecycle. Design and ship the onboarding, activation, and re-engagement sequences that don't exist yet, starting with the thousands of Horizon signups who've never heard from us. - Measure activation lift, not open rates. - Experiment fast. Organize campaign taxonomy, UTM discipline, and a clean handoff from HubSpot into Salesforce so we can run multiple experiments to optimize our funnel. - Report cost per activated user and pipeline per dollar, and kill what doesn't work quickly and out loud. - Route the audience to the product. Turn FastMCP's developer audience into Horizon accounts through in-product paths, docs placements, end cards, and CTAs. This is the highest-leverage number in the role." Qualifications (Must have): "Must have 7+ years in growth or demand generation at B2B SaaS or developer-focused companies, with hands-on ownership throughout. You've been the person in the tool, not the person briefing someone who's in the tool. You know how to use channels and campaigns to generate predictable pipeline for sales and self serve signups. You've owned an acquisition budget and reported honestly on what it returned, including the parts that didn't work. You've built attribution from close to nothing before: campaign taxonomy, UTM structure, and a funnel model leadership used to make decisions. HubSpot and Salesforce, or close equivalents. Lifecycle ownership with measured results. Onboarding and activation sequences where you can tell us the before-and-after conversion numbers, and what you learned when one of them failed. Comfort being the only person in your function. You'll pick the sequence, say no to good ideas, and ship without a team behind you." Nice to have (Skills): "Background at an open-source or developer-tools company. You know why a GitHub star isn't a lead, and you've dealt with the particular weirdness of marketing to engineers. SQL, and comfort living in a BI tool. Our stack is HubSpot, Salesforce, Amplitude, Common Room, and Omni. Experience running a product-led self-serve funnel alongside an enterprise sales-led motion without one cannibalizing the other. You've integrated two marketing stacks after an acquisition and lived to tell about it." Who This Role Is Not For (maybe keep as a note under Qualifications or separate). Could be a short paragraph. "We'd rather you rule yourself out now than be unhappy in six months. You want to manage a team soon. This is an individual contributor role and will stay one for at least a year. If it grows into a team later, good, but don't take this job expecting that. You need clean data before you'll commit to a number. Some of our plumbing is broken. You'll fix it while also being accountable for outcomes. Those happen at the same time. You prefer to work through an agency. You can use contractors for execution. The thinking and most of the building will be yours. You want a stable roadmap. We merged with another company this year, we're validating a new product direction, and priorities move. If that reads as chaos rather than opportunity, this will be a frustrating job." Pay: "Base Salary Ranges: San Francisco Bay Area & NYC Metro: $173,000–$222,000 Washington D.C., Boston, LA Metro, Seattle: $162,000–$201,000 Denver, Chicago, Atlanta, & all other U.S. metros: $154,000–$200,000 Actual base salary within each range depends on the candidate's location, experience, and qualifications. Please keep in mind that equity and benefits are not included in the range provided above. Your recruiter can share more about the salary range for your preferred location during the hiring process." Benefits: "Perks and Benefits: Remote-first team with flexible-first culture Equity Stock Options 401(k) with 5% company match (vests immediately!) Unlimited PTO Medical, Dental and Vision insurance Generous Parental Leave Life Insurance and Disability benefits $800/month remote work
- .
-