Staff Product Manager, Growth (Acquisition)
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can choose headings that match content. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings where appropriate. But we need to map content to these headings. Probably:
- About the role: description of role (The Role ...)
- Responsibilities: What You Will Own (list)
- Requirements: What We Are Looking For (list)
- Qualifications: maybe not separate; could combine with Requirements? But we can include Qualifications if we have content. The posting includes experience etc. Could treat as Qualifications.
- Skills: maybe not separate; but we could include Skills from How You Work? Might be better to have Skills section summarizing abilities.
- Benefits: from How We’ll Help You Thrive (benefits list)
- Pay: from compensation paragraph
- Schedule: maybe from Where And How We Work (flexible remote/hybrid) - could be Schedule.
We must not create sections with filler like "not specified". Ensure we have real content.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details, but we can format as lists.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes EEO statements at end; we should remove those. Also remove "Our Story" maybe? It's substantive about company; we could include as maybe "About the company" but not in allowed headings. The instruction says prefer a few substantive sections over many thin ones. Could include "Our Story" as a section but not in allowed headings list; but we could still use with custom heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says use for section headings (e.g. ...). Likely they expect those headings. Safer to stick to those.
Thus we need to map content to those headings. Possibly combine multiple topics under each.
Let's extract:
About the role: The Role As Staff Product Manager, Acquisition at Linktree, you will own ... description.
Responsibilities: What You Will Own bullet list.
Requirements: What We Are Looking For bullet list (experience etc.)
Qualifications: maybe same as Requirements? Could split: Qualifications could be education? Not present. Could omit Qualifications if no specific content. But we need to avoid empty headings. So maybe we skip Qualifications.
Skills: How You Work bullet list (traits).
Benefits: How We’ll Help You Thrive bullet list.
Pay: compensation paragraph.
Schedule: Where And How We Work (flexible remote/hybrid) plus maybe work hours.
We also have "Our Story" which is company description; could be included under About the role? Might be okay to add a separate section like "About Linktree" but not in allowed headings. Could incorporate into About the role? Might be okay to add a section "About Linktree" as but not listed; risk. Better to incorporate into About the role? Might be okay to add a separate section but risk violating instruction. I'd keep to allowed headings.
Thus we will output:
About the role
with custom heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says use for section headings (e.g. ...). Likely they expect those headings. Safer to stick to those.
Thus we need to map content to those headings. Possibly combine multiple topics under each.
Let's extract:
About the role: The Role As Staff Product Manager, Acquisition at Linktree, you will own ... description.
Responsibilities: What You Will Own bullet list.
Requirements: What We Are Looking For bullet list (experience etc.)
Qualifications: maybe same as Requirements? Could split: Qualifications could be education? Not present. Could omit Qualifications if no specific content. But we need to avoid empty headings. So maybe we skip Qualifications.
Skills: How You Work bullet list (traits).
Benefits: How We’ll Help You Thrive bullet list.
Pay: compensation paragraph.
Schedule: Where And How We Work (flexible remote/hybrid) plus maybe work hours.
We also have "Our Story" which is company description; could be included under About the role? Might be okay to add a separate section like "About Linktree" but not in allowed headings. Could incorporate into About the role? Might be okay to add a section "About Linktree" as but not listed; risk. Better to incorporate into About the role? Might be okay to add a separate section but risk violating instruction. I'd keep to allowed headings.
Thus we will output:
About the role
for section headings (e.g. ...). Likely they expect those headings. Safer to stick to those.
Thus we need to map content to those headings. Possibly combine multiple topics under each.
Let's extract:
About the role: The Role As Staff Product Manager, Acquisition at Linktree, you will own ... description.
Responsibilities: What You Will Own bullet list.
Requirements: What We Are Looking For bullet list (experience etc.)
Qualifications: maybe same as Requirements? Could split: Qualifications could be education? Not present. Could omit Qualifications if no specific content. But we need to avoid empty headings. So maybe we skip Qualifications.
Skills: How You Work bullet list (traits).
Benefits: How We’ll Help You Thrive bullet list.
Pay: compensation paragraph.
Schedule: Where And How We Work (flexible remote/hybrid) plus maybe work hours.
We also have "Our Story" which is company description; could be included under About the role? Might be okay to add a separate section like "About Linktree" but not in allowed headings. Could incorporate into About the role? Might be okay to add a section "About Linktree" as but not listed; risk. Better to incorporate into About the role? Might be okay to add a separate section but risk violating instruction. I'd keep to allowed headings.
Thus we will output:
About the role
About the role
... (the role description)
Responsibilities
- ... each bullet from What You Will Own
Requirements
- ... each bullet from What We Are Looking For
Skills
- ... each bullet from How You Work
Benefits
- ... each bullet from How We’ll Help You Thrive
Pay
... compensation paragraph
Schedule
... Where And How We Work description
We must ensure we preserve all substantive information. Need to include details like "Linktree serves a massive global audience..." etc. Let's extract each piece. About the role paragraph: The Role As Staff Product Manager, Acquisition at Linktree, you will own one of the most important growth challenges in our business: bringing more new users into Linktree and building scalable, product-led acquisition loops that expand our reach. Linktree serves a massive global audience of creators, entrepreneurs, businesses, artists, publishers, and brands. Your work will shape how the next generation of users discovers Linktree, moves from a profile or external touchpoint into sign-up, and ultimately enters the product ready to experience value. This is a senior, high-impact product leadership role for someone who thinks deeply about growth loops, funnels, organic acquisition, and experimentation. You will work across the very top of the customer journey — from SEO and profile-to-signup experiences to referrals, landing pages, claim flows, and entirely new tools designed to bring more users into the Linktree ecosystem. You will partner closely with Engineering, Design, Data, Growth Marketing, SEO, Lifecycle, Activation, and executive leadership to define Linktree's acquisition strategy and build the systems that drive sustainable new-user growth at scale. We'll put that in. Responsibilities bullet list from "What You Will Own": each line starts with a verb. List: - Own Linktree's product-led acquisition strategy, with a clear mandate to grow the number of new users entering the Linktree ecosystem. - Own and optimize the profile-to-signup journey, including "Powered by Linktree," "Claim your Linktree," creator discovery, sign-up, authentication, and other pathways that turn visitors into Linktree users. - Identify and build scalable organic acquisition loops across Linktree's massive network of profiles, content, creators, businesses, and audience traffic. - Partner closely with Growth Marketing and SEO to improve organic discovery, landing-page conversion, SEO/AEO performance, and the journey from external discovery into the product. - Own and evolve Linktree's referral strategy, including the product experiences, incentives, and growth mechanics that encourage creators to bring new users into the ecosystem while carefully managing incrementality and cannibalization. - Develop new acquisition products and tools that provide standalone value to creators and businesses while introducing them to Linktree — from social presence and audience-growth tools to new ways of helping prospective users understand how they compare, improve, and grow. - Explore creative, zero-to-one acquisition opportunities across new customer segments, including ways to identify prospective users, create relevant Linktree experiences for them, and build compelling "claim your Linktree" journeys. - Develop a high-velocity experimentation roadmap across acquisition surfaces, focused on increasing qualified traffic, signup conversion, referral growth, and overall new-user acquisition. - Lead deep funnel analysis to understand where prospective users discover Linktree, where they drop off before sign-up, and which interventions have the greatest potential to unlock growth. - Partner closely with the Activation team to create a seamless handoff from acquisition into activation, ensuring the users and segments we bring into Linktree have a clear path to reaching value. - Partner with Data to ensure acquisition channels, loops, funnels, and experiments are well-instrumented and measurable. - Communicate acquisition strategy, experiment results, tradeoffs, and business impact clearly to senior leadership and executive audiences. - Raise the bar for growth product craft at Linktree by bringing strong experimentation discipline, creative growth thinking, and customer empathy into the product organization. We'll put each as