Sr. Growth Marketing Manager
for each section that has content. Use - for lists. Use
for prose. No job title heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove application instructions. We need to preserve substantive info.
Let's parse the posting.
Sections:
- Role at a glance: includes What, Impact, Team, Where. Could be separate sections? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. Likely we should have sections: About the role (maybe summarizing role at a glance), Responsibilities (What You'll Do), Requirements/Qualifications/Skills (What You'll Bring + Nice to have), Benefits (Compensation & Benefits + We Want You To Feel Taken Care Of...), Pay (Compensation range), Schedule? Not present. Could omit Schedule if not present.
We need to include a section only when posting has real specific content. So we need to decide which sections to include.
Let's extract:
About the role: Could be "Role at a glance" plus "About Rally" and "The opportunity". Might be too much. But we can create an "About the role" section summarizing role description: includes What, Impact, Team, Where, plus maybe description of Rally and opportunity. However we must not invent or summarize away detail; we need to preserve ALL substantive information. So we need to include all details, not just summary. But we can embed details in paragraphs and lists.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove boilerplate: EEO, equal-opportunity, scam-warning, navigation, cookie, legal, application instructions. Also remove "How We Work", "This might not be for you if…", "If you read that and thought…", "Our hiring process", "Rally is an equal opportunity employer", etc. Also remove "Compensation Range: $120K - $140K" duplicate.
We need to keep substantive content: role description, responsibilities, qualifications, benefits, pay.
Let's list substantive blocks:
1. Role at a glance:
- What: As Sr. Growth Marketing Manager, you'll own pipeline coverage and top-of-funnel demand gen end-to-end — deciding how we get there, not just executing a fixed plan.
- Impact: You'll build and run the demand engine that gets Rally and our recently launched Agent and MCP in front of the buyers evaluating an AI-native research stack, directly shaping whether pipeline turns into revenue.
- Team: You'll join our Marketing team and work closely with Sales, the founders, and cross-functional partners across Product and Engineering. At our size, the lines between them ebb and flow, so you'll always be working cross-functionally.
- Where: Remote-first across the US, with hubs in New York and Boston.
2. About Rally (description of company/product). This is substantive.
3. The opportunity (description of why role exists). Substantive.
4. What You'll Do (list of responsibilities):
- Identify and test new channels or tactics to diversify pipeline sources
- Run events, email marketing strategy, and social campaigns
- Partner with sales to align campaigns with pipeline targets and feedback from the field
- Collaborate with product marketing on product-focused campaigns and joint strategy building, ensuring positioning and messaging translate into pipeline-generating activity
- Continuously optimize based on CAC, conversion rates, and pipeline velocity
5. What You'll Bring (requirements):
- 6+ years running demand gen or growth marketing, with a track record of owning a pipeline number and measurable results to show for it
- Built and owned experience across paid, events, and content
- Tech/SaaS background, startup to mid-market, comfortable operating with limited resources and ambiguity
- You'd rather figure out the right approach yourself than wait to be told what to do
6. Nice to have:
- Managing paid campaigns (Google and LinkedIn) and hosted webinars
- Experience in UXR or adjacent research/product tooling
- Startup experience, particularly at Series A/B stage
7. Don’t check every box? Apply anyway. (This is more encouragement; could be considered boilerplate? It's not a requirement; but it's substantive? Might be considered fluff but we can keep as a paragraph under Requirements? Probably okay to keep as a note.)
8. How We Work (description of culture). Might be considered substantive but could be considered boilerplate? It's about remote-first, async, owners, user first, AI-native, etc. This is substantive about company culture. Might keep as a section "Culture" but not in prescribed headings. The instruction only gave examples of headings; we can use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. So we may not include a separate "How We Work" section unless we map it to something like "About the role" or "Benefits"? Probably better to omit as it's not strictly required and could be considered filler? But it's substantive about work style. However the instruction: "Prefer a few substantive sections over many thin ones." Could include as part of "About the role" or "Benefits"? Might be okay to omit.
9. This might not be for you if… (list of disqualifiers). This is also substantive but could be considered a negative list; maybe we can omit as it's not a heading like Responsibilities etc. Could be considered part of "About the role" but it's negative. Might be okay to omit.
10. If you read that and thought… (call to action). Could be omitted as application instruction? It's encouraging to apply; maybe considered application instruction? Might be removed.
11. Compensation & Benefits: includes base salary range, variable compensation equity, benefits list.
12. We Want You To Feel Taken Care Of, So You Can Do Your Best Work. (list of benefits). This is substantive benefits.
13. Benefits may vary based on role, level, and location... (note). Could be included.
14. Our hiring process (steps). This is application instruction; should be removed per instruction: remove application instructions.
15. Rally is an equal opportunity employer... (EEO) remove.
16. This job description is intended... (legal) remove.
17. Compensation Range: $120K - $140K duplicate; remove.
Thus we will produce sections:
- About the role (maybe combine Role at a glance, About Rally, The opportunity). We'll need to preserve all details; we can put them in paragraphs.
- Responsibilities (What You'll Do) as - .
- Requirements (What You'll Bring) as
- .
- Nice to have (maybe under Skills or Qualifications). Could be a separate section "Preferred Qualifications" but not in examples. Could put under Requirements as a separate list with heading "Nice to have" but that is not one of the example headings. Might be better to include under Requirements as a sublist? But we need to preserve content. Could create a section "Preferred Qualifications" using
even if not in examples; but instruction says use for section headings (e.g. ...). It doesn't forbid other headings, but to be safe we could incorporate nice-to-have into Requirements section as a separate with a preceding saying "Nice to have:"? That might be okay.
- Benefits: combine Compensation & Benefits and We Want You To Feel Taken Care Of... into a Benefits section. Use
- for each benefit.
- Pay: separate section for base salary range and variable compensation. Could be under Pay heading.
We must not repeat job title as heading. Already not.
We must not put Job ID/requisition numbers as headings.
Now produce HTML.
Let's craft:
About the role
As Sr. Growth Marketing Manager, you'll own pipeline coverage and top-of-funnel demand gen end-to-end — deciding how we get there, not just executing a fixed plan. You'll build and run the demand engine that gets Rally and our recently launched Agent and MCP in front of the buyers evaluating an AI-native research stack, directly shaping whether pipeline turns into revenue. You'll join our Marketing team and work closely with Sales, the founders, and cross-functional partners across Product and Engineering. At our size, the lines between them ebb and flow, so you'll always be working cross-functionally. The role is remote-first across the US, with hubs in New York and Boston.
About Rally: In a world where anyone can ship anything, the teams building closest to their users win. But talking to users is still way harder than it should be. Pulling lists, chasing consent, juggling calendars, sending incentives: it's why most product teams skip research altogether. We're here to end manual recruitment. Rally is agentic research infrastructure: the system that lets companies talk to their own users safely, at any scale. Tell Rally what you want to learn, and Rally Agent builds the study, finds the right participants, and handles outreach, scheduling, and incentives, all within your company's guardrails. It works from the Rally app, from Slack, or from the AI tools you already use. Agents handle the busywork, so people focus on the human parts: learning from each other. Today, teams at Google, Meta, Figma, Ramp, Perplexity, and MongoDB run their research on Rally. And we're building a company that lasts, investing in the product and the team for the long haul.
The opportunity: We believe teams will always need to talk to their users, however far AI goes, and most companies still don't have a safe way to let team members outside of traditional UX Research do it. We recently launched Rally's Agent and MCP, and we're going after the biggest companies in the world. The product is catching up to the vision, with plenty of exciting challenges still ahead. That's where you come in. You'd join Marketing, a small, high-ownership team that's a little obsessed with our users. We work side by side with the researchers and product builders who use Rally every day, and yes, we use Rally to build Rally. This role exists because demand gen and pipeline need a dedicated owner unafraid to take risks — you'd own it end-to-end, with real latitude to build the approach that works.
Responsibilities
- Identify and test new channels or tactics to diversify pipeline sources
- Run events, email marketing strategy, and social campaigns
- Partner with sales to align campaigns with pipeline targets and feedback from the field
- Collaborate with product marketing on product-focused campaigns and joint strategy building, ensuring positioning and messaging translate into pipeline-generating activity
- Continuously optimize based on CAC, conversion rates, and pipeline velocity
Requirements
- 6+ years running demand gen or growth marketing, with a track record of owning a pipeline number and measurable results to show for it
- Built and owned experience across paid, events, and content
- Tech/SaaS background, startup to mid-market, comfortable operating with limited resources and ambiguity
- You'd rather figure out the right approach yourself than wait to be told what to do
Nice to have:
- Managing paid campaigns (Google and LinkedIn) and hosted webinars
- Experience in UXR or adjacent research/product tooling
- Startup experience, particularly at Series A/B stage
for prose. No job title heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove application instructions. We need to preserve substantive info. Let's parse the posting. Sections: - Role at a glance: includes What, Impact, Team, Where. Could be separate sections? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. Likely we should have sections: About the role (maybe summarizing role at a glance), Responsibilities (What You'll Do), Requirements/Qualifications/Skills (What You'll Bring + Nice to have), Benefits (Compensation & Benefits + We Want You To Feel Taken Care Of...), Pay (Compensation range), Schedule? Not present. Could omit Schedule if not present.
We need to include a section only when posting has real specific content. So we need to decide which sections to include.
Let's extract:
About the role: Could be "Role at a glance" plus "About Rally" and "The opportunity". Might be too much. But we can create an "About the role" section summarizing role description: includes What, Impact, Team, Where, plus maybe description of Rally and opportunity. However we must not invent or summarize away detail; we need to preserve ALL substantive information. So we need to include all details, not just summary. But we can embed details in paragraphs and lists.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove boilerplate: EEO, equal-opportunity, scam-warning, navigation, cookie, legal, application instructions. Also remove "How We Work", "This might not be for you if…", "If you read that and thought…", "Our hiring process", "Rally is an equal opportunity employer", etc. Also remove "Compensation Range: $120K - $140K" duplicate.
We need to keep substantive content: role description, responsibilities, qualifications, benefits, pay.
Let's list substantive blocks:
1. Role at a glance:
- What: As Sr. Growth Marketing Manager, you'll own pipeline coverage and top-of-funnel demand gen end-to-end — deciding how we get there, not just executing a fixed plan.
- Impact: You'll build and run the demand engine that gets Rally and our recently launched Agent and MCP in front of the buyers evaluating an AI-native research stack, directly shaping whether pipeline turns into revenue.
- Team: You'll join our Marketing team and work closely with Sales, the founders, and cross-functional partners across Product and Engineering. At our size, the lines between them ebb and flow, so you'll always be working cross-functionally.
- Where: Remote-first across the US, with hubs in New York and Boston.
2. About Rally (description of company/product). This is substantive.
3. The opportunity (description of why role exists). Substantive.
4. What You'll Do (list of responsibilities):
- Identify and test new channels or tactics to diversify pipeline sources
- Run events, email marketing strategy, and social campaigns
- Partner with sales to align campaigns with pipeline targets and feedback from the field
- Collaborate with product marketing on product-focused campaigns and joint strategy building, ensuring positioning and messaging translate into pipeline-generating activity
- Continuously optimize based on CAC, conversion rates, and pipeline velocity
5. What You'll Bring (requirements):
- 6+ years running demand gen or growth marketing, with a track record of owning a pipeline number and measurable results to show for it
- Built and owned experience across paid, events, and content
- Tech/SaaS background, startup to mid-market, comfortable operating with limited resources and ambiguity
- You'd rather figure out the right approach yourself than wait to be told what to do
6. Nice to have:
- Managing paid campaigns (Google and LinkedIn) and hosted webinars
- Experience in UXR or adjacent research/product tooling
- Startup experience, particularly at Series A/B stage
7. Don’t check every box? Apply anyway. (This is more encouragement; could be considered boilerplate? It's not a requirement; but it's substantive? Might be considered fluff but we can keep as a paragraph under Requirements? Probably okay to keep as a note.)
8. How We Work (description of culture). Might be considered substantive but could be considered boilerplate? It's about remote-first, async, owners, user first, AI-native, etc. This is substantive about company culture. Might keep as a section "Culture" but not in prescribed headings. The instruction only gave examples of headings; we can use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. So we may not include a separate "How We Work" section unless we map it to something like "About the role" or "Benefits"? Probably better to omit as it's not strictly required and could be considered filler? But it's substantive about work style. However the instruction: "Prefer a few substantive sections over many thin ones." Could include as part of "About the role" or "Benefits"? Might be okay to omit.
9. This might not be for you if… (list of disqualifiers). This is also substantive but could be considered a negative list; maybe we can omit as it's not a heading like Responsibilities etc. Could be considered part of "About the role" but it's negative. Might be okay to omit.
10. If you read that and thought… (call to action). Could be omitted as application instruction? It's encouraging to apply; maybe considered application instruction? Might be removed.
11. Compensation & Benefits: includes base salary range, variable compensation equity, benefits list.
12. We Want You To Feel Taken Care Of, So You Can Do Your Best Work. (list of benefits). This is substantive benefits.
13. Benefits may vary based on role, level, and location... (note). Could be included.
14. Our hiring process (steps). This is application instruction; should be removed per instruction: remove application instructions.
15. Rally is an equal opportunity employer... (EEO) remove.
16. This job description is intended... (legal) remove.
17. Compensation Range: $120K - $140K duplicate; remove.
Thus we will produce sections:
- About the role (maybe combine Role at a glance, About Rally, The opportunity). We'll need to preserve all details; we can put them in paragraphs.
- Responsibilities (What You'll Do) as - .
- Requirements (What You'll Bring) as
- .
- Nice to have (maybe under Skills or Qualifications). Could be a separate section "Preferred Qualifications" but not in examples. Could put under Requirements as a separate list with heading "Nice to have" but that is not one of the example headings. Might be better to include under Requirements as a sublist? But we need to preserve content. Could create a section "Preferred Qualifications" using
even if not in examples; but instruction says use for section headings (e.g. ...). It doesn't forbid other headings, but to be safe we could incorporate nice-to-have into Requirements section as a separate with a preceding saying "Nice to have:"? That might be okay.
- Benefits: combine Compensation & Benefits and We Want You To Feel Taken Care Of... into a Benefits section. Use
- for each benefit.
- Pay: separate section for base salary range and variable compensation. Could be under Pay heading.
We must not repeat job title as heading. Already not.
We must not put Job ID/requisition numbers as headings.
Now produce HTML.
Let's craft:
About the role
As Sr. Growth Marketing Manager, you'll own pipeline coverage and top-of-funnel demand gen end-to-end — deciding how we get there, not just executing a fixed plan. You'll build and run the demand engine that gets Rally and our recently launched Agent and MCP in front of the buyers evaluating an AI-native research stack, directly shaping whether pipeline turns into revenue. You'll join our Marketing team and work closely with Sales, the founders, and cross-functional partners across Product and Engineering. At our size, the lines between them ebb and flow, so you'll always be working cross-functionally. The role is remote-first across the US, with hubs in New York and Boston.
About Rally: In a world where anyone can ship anything, the teams building closest to their users win. But talking to users is still way harder than it should be. Pulling lists, chasing consent, juggling calendars, sending incentives: it's why most product teams skip research altogether. We're here to end manual recruitment. Rally is agentic research infrastructure: the system that lets companies talk to their own users safely, at any scale. Tell Rally what you want to learn, and Rally Agent builds the study, finds the right participants, and handles outreach, scheduling, and incentives, all within your company's guardrails. It works from the Rally app, from Slack, or from the AI tools you already use. Agents handle the busywork, so people focus on the human parts: learning from each other. Today, teams at Google, Meta, Figma, Ramp, Perplexity, and MongoDB run their research on Rally. And we're building a company that lasts, investing in the product and the team for the long haul.
The opportunity: We believe teams will always need to talk to their users, however far AI goes, and most companies still don't have a safe way to let team members outside of traditional UX Research do it. We recently launched Rally's Agent and MCP, and we're going after the biggest companies in the world. The product is catching up to the vision, with plenty of exciting challenges still ahead. That's where you come in. You'd join Marketing, a small, high-ownership team that's a little obsessed with our users. We work side by side with the researchers and product builders who use Rally every day, and yes, we use Rally to build Rally. This role exists because demand gen and pipeline need a dedicated owner unafraid to take risks — you'd own it end-to-end, with real latitude to build the approach that works.
Responsibilities
- Identify and test new channels or tactics to diversify pipeline sources
- Run events, email marketing strategy, and social campaigns
- Partner with sales to align campaigns with pipeline targets and feedback from the field
- Collaborate with product marketing on product-focused campaigns and joint strategy building, ensuring positioning and messaging translate into pipeline-generating activity
- Continuously optimize based on CAC, conversion rates, and pipeline velocity
Requirements
- 6+ years running demand gen or growth marketing, with a track record of owning a pipeline number and measurable results to show for it
- Built and owned experience across paid, events, and content
- Tech/SaaS background, startup to mid-market, comfortable operating with limited resources and ambiguity
- You'd rather figure out the right approach yourself than wait to be told what to do
Nice to have:
- Managing paid campaigns (Google and LinkedIn) and hosted webinars
- Experience in UXR or adjacent research/product tooling
- Startup experience, particularly at Series A/B stage
- .
- Requirements (What You'll Bring) as
- .
- Nice to have (maybe under Skills or Qualifications). Could be a separate section "Preferred Qualifications" but not in examples. Could put under Requirements as a separate list with heading "Nice to have" but that is not one of the example headings. Might be better to include under Requirements as a sublist? But we need to preserve content. Could create a section "Preferred Qualifications" using
even if not in examples; but instruction says use
for section headings (e.g. ...). It doesn't forbid other headings, but to be safe we could incorporate nice-to-have into Requirements section as a separate
- with a preceding
- for each benefit.
- Pay: separate section for base salary range and variable compensation. Could be under Pay heading.
We must not repeat job title as heading. Already not.
We must not put Job ID/requisition numbers as headings.
Now produce HTML.
Let's craft:
About the role
As Sr. Growth Marketing Manager, you'll own pipeline coverage and top-of-funnel demand gen end-to-end — deciding how we get there, not just executing a fixed plan. You'll build and run the demand engine that gets Rally and our recently launched Agent and MCP in front of the buyers evaluating an AI-native research stack, directly shaping whether pipeline turns into revenue. You'll join our Marketing team and work closely with Sales, the founders, and cross-functional partners across Product and Engineering. At our size, the lines between them ebb and flow, so you'll always be working cross-functionally. The role is remote-first across the US, with hubs in New York and Boston.
About Rally: In a world where anyone can ship anything, the teams building closest to their users win. But talking to users is still way harder than it should be. Pulling lists, chasing consent, juggling calendars, sending incentives: it's why most product teams skip research altogether. We're here to end manual recruitment. Rally is agentic research infrastructure: the system that lets companies talk to their own users safely, at any scale. Tell Rally what you want to learn, and Rally Agent builds the study, finds the right participants, and handles outreach, scheduling, and incentives, all within your company's guardrails. It works from the Rally app, from Slack, or from the AI tools you already use. Agents handle the busywork, so people focus on the human parts: learning from each other. Today, teams at Google, Meta, Figma, Ramp, Perplexity, and MongoDB run their research on Rally. And we're building a company that lasts, investing in the product and the team for the long haul.
The opportunity: We believe teams will always need to talk to their users, however far AI goes, and most companies still don't have a safe way to let team members outside of traditional UX Research do it. We recently launched Rally's Agent and MCP, and we're going after the biggest companies in the world. The product is catching up to the vision, with plenty of exciting challenges still ahead. That's where you come in. You'd join Marketing, a small, high-ownership team that's a little obsessed with our users. We work side by side with the researchers and product builders who use Rally every day, and yes, we use Rally to build Rally. This role exists because demand gen and pipeline need a dedicated owner unafraid to take risks — you'd own it end-to-end, with real latitude to build the approach that works.
Responsibilities
- Identify and test new channels or tactics to diversify pipeline sources
- Run events, email marketing strategy, and social campaigns
- Partner with sales to align campaigns with pipeline targets and feedback from the field
- Collaborate with product marketing on product-focused campaigns and joint strategy building, ensuring positioning and messaging translate into pipeline-generating activity
- Continuously optimize based on CAC, conversion rates, and pipeline velocity
Requirements
- 6+ years running demand gen or growth marketing, with a track record of owning a pipeline number and measurable results to show for it
- Built and owned experience across paid, events, and content
- Tech/SaaS background, startup to mid-market, comfortable operating with limited resources and ambiguity
- You'd rather figure out the right approach yourself than wait to be told what to do
Nice to have:
- Managing paid campaigns (Google and LinkedIn) and hosted webinars
- Experience in UXR or adjacent research/product tooling
- Startup experience, particularly at Series A/B stage
saying "Nice to have:"? That might be okay. - Benefits: combine Compensation & Benefits and We Want You To Feel Taken Care Of... into a Benefits section. Use
- for each benefit.
- Pay: separate section for base salary range and variable compensation. Could be under Pay heading.
We must not repeat job title as heading. Already not.
We must not put Job ID/requisition numbers as headings.
Now produce HTML.
Let's craft:
- .
- Nice to have (maybe under Skills or Qualifications). Could be a separate section "Preferred Qualifications" but not in examples. Could put under Requirements as a separate list with heading "Nice to have" but that is not one of the example headings. Might be better to include under Requirements as a sublist? But we need to preserve content. Could create a section "Preferred Qualifications" using