Director, Product Growth

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. We need to parse the posting and extract relevant content. Let's identify sections: - About the role: description of role, what they do, etc. Could be the paragraph starting "At Roofr, we’re obsessed..." but that's more company intro. The role description: "Roofr is looking for a Director, Product Growth to own how we grow through the product..." etc. Also "What You’ll be measured on", "What You’ll get to do", "What You’ll bring to the role". Could map to Responsibilities, Requirements, Qualifications, Skills. We need to decide sections: maybe About the role (company overview), Responsibilities (What You’ll get to do), Requirements (What You’ll bring to the role), Qualifications (maybe same as Requirements), Skills (maybe specific skills). Benefits (What we offer). Pay (Compensation Band). Schedule (maybe not present). The posting does not mention schedule specifics (like full-time, remote). It mentions remote first culture, weekly Friday paydays, but not schedule. Could include Schedule if we have info like "Remote first culture" but that's not schedule. Probably no Schedule section. We must not create sections with filler like "not specified". So only include sections with real content. Let's extract: About the role: Could be the initial paragraph about Roofr and the role purpose. Let's craft a concise paragraph preserving info: "At Roofr, we’re obsessed with our customers... We started by building essential sales tools... We created a CRM that connects these solutions... With a clear roadmap ahead, we’re excited to continue expanding... We have an amazing culture, strong financials, and best-in-class company metrics. It’s an exciting time to be part of an extraordinary startup that is already successful, yet still early enough to offer its team significant growth, equity, and the opportunity to make a real impact. This position is for an existing vacancy. Roofr is looking for a Director, Product Growth to own how we grow through the product. You’ll work at the intersection of product, data, and go-to-market: designing the activation and expansion paths that keep contractors engaged, surfacing product signals that unlock sales conversations, and building a stronger self-serve experience anchored in friction-less SMB UI/UX. You’ll report to the CPO, sit on the product leadership team, and lead a cross-functional Growth team that includes Engineering, Design, Data Science, and a Principal PM as your direct report. Initial building blocks are already in place. We have a clear activation metric that guides both our self-serve and sales-assist motion, a hybrid model that is actively evolving, and an AI product line in AI Receptionist that is ready to scale. The job is to take what’s working, sharpen it, and build on top of it." That seems appropriate for About the role. Responsibilities: Could be "What You’ll get to do" bullet list. Let's extract bullet points: - Orchestrate the hybrid motion with Sales: Identify the product signals that indicate a contractor is ready for a sales conversation and build the playbooks that turn those signals into pipeline, across both new subscriber acquisition and expansion of the existing base - Drive activation and expansion: Own the in-product experience that gets new contractors to value fast and design the expansion loops that drive deeper adoption and multi-product retention across the customer base - Grow self-serve revenue: Own the self-serve motion across transactional and subscription products, with particular focus on Measure+ and in-product upgrade paths - Lead the team and the metrics: Lead the Growth team, including Engineering, Design, and Data Science, build a fast experimentation culture, and own the growth metrics that matter to leadership Also "What You’ll be measured on" could be considered responsibilities or metrics. But we can incorporate as part of responsibilities or separate section? The spec says use headings for sections like Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could treat "What You’ll be measured on" as part of Responsibilities or maybe as a separate section like "Key Metrics". But not in allowed headings. Could incorporate into Responsibilities. Requirements: "What You’ll bring to the role" bullet list. Extract: - 8 to 12+ years of product growth experience in B2B SaaS; vertical SaaS is a strong plus - Real experience building a hybrid product-led and sales-led motion. You have felt the friction of making these work together, not just read about it - Strong activation and expansion instincts. You know how to design user journeys that drive measurable improvement in time-to-value and long-term retention - Experience working across both transactional and subscription revenue models - Comfortable running experiments end to end: designing them, setting success criteria, and shipping without waiting for perfect conditions - Fluent in growth metrics like activation rate, adoption, expansion revenue, and NRR. You run your own analysis - Experience with tools like Amplitude, HubSpot, and Snowflake or a comparable data warehouse - Experience building or scaling an AI-powered product is a meaningful differentiator - Able to lead and develop cross-functional teams in an environment where everyone doesn’t work for you. You work alongside your team, not just above it - Clear communicator at every level, from executive to analyst - Based in the US or Canada Qualifications: Could be similar to Requirements; maybe we can combine. But we need to avoid duplication. Could treat Requirements as qualifications. But we need to follow spec: we can have both Requirements and Qualifications if content distinct. However the posting lumps them together. Could split: Requirements = experience, Qualifications = skills/tools? But better to have one section for Requirements/Qualifications combined? The spec says we can include sections only when posting has real specific content. It doesn't forbid having both Requirements and Qualifications if we can differentiate. But we risk duplication. Safer to have one section, maybe "Requirements" covering both experience and skills. Or we could have "Requirements" for experience and "Skills" for tools/competencies. Let's see. Skills: Could list specific skills: product growth, hybrid motion, activation, experimentation, metrics fluency, tools (Amplitude, HubSpot, Snowflake), AI product experience, leadership, communication. But we already have those in Requirements. Might be okay to put them under Skills. Let's decide: - About the role: paragraph as above. - Responsibilities: bullet list of What You’ll get to do. - Requirements: bullet list of experience and qualifications (8-12+ years, hybrid motion experience, activation instincts, transactional/subscription, experiments, metrics fluency, tools, AI experience, leadership, communication, US/Canada). - Skills: maybe we can list specific competencies like "Product growth strategy, Hybrid motion design, Activation & expansion, Experimentation, Growth metrics analysis, Amplitude, HubSpot, Snowflake, AI product scaling, Cross-functional team leadership, Communication". But that repeats. Might be considered duplication. Safer to omit Skills section if content overlaps heavily with Requirements. The spec says prefer a few substantive sections over many thin ones. So we can combine Requirements and Skills into one section, maybe label it "Requirements". Or we could label it "Qualifications". Let's choose "Requirements". Then we can omit Skills. Benefits: "What we offer (US + Canada)" bullet list. Extract: - Vacation/Paid Time Off: 1st week of employment is mandatory PTO! Start your journey with Roofr by decompressing and recharging - we will see you in week 2! - 1 Friday off per month (we call those our laundry days!) - Company wide paid shutdown for the week between Christmas and New Years - Flexible time off - 80% employer-paid benefits in the U.S. and 100% employer-paid premiums for Extended Healthcare and Dental in Canada - RRSP/401k match - Generous Parental Leave policy - Perks: We host an annual company retreat with great team building activities - Ample learning and development opportunities to continue growing your career - Home office setup stipend - Internet and phone allowance - Remote first culture - Weekly Friday paydays! Also AI Notice and Important Notice are boilerplate/legal; we should remove them. Also EEO statement remove. Pay: Compensation Band: $250,000.00 - $300,000.00 USD. Also description about compensation ranges. We'll include that. Schedule: Not present; we omit. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include any markdown code fences. Let's craft. First, About the role:

  About the role

  then

  with the paragraph. Second, Responsibilities:

  Responsibilities

  then
  with each bullet. Third, Requirements:

  Requirements

  then
  with each bullet. Fourth, Benefits:

  Benefits

  then
  with each bullet. Fifth, Pay:

  Pay

  then

  with compensation band and note. Make sure to preserve all substantive info; we must not lose any detail. Let's write the About the role paragraph exactly as we extracted, preserving details. Paragraph: "At Roofr, we’re obsessed with our customers. We constantly gather feedback to shape, prioritize, and launch the products they truly need. That’s what makes Roofr’s CRM special. We started by building essential sales tools like aerial roof measurements and digital sales proposals. But when our customers asked for a simple, affordable way to manage and scale their entire businesses, we listened. So, we created a CRM that connects these solutions—along with payments, material ordering, and more—into a seamless, powerful platform. With a clear roadmap ahead, we’re excited to continue expanding and leading the market with innovative products. We have an amazing culture, strong financials, and best-in-class company metrics. It’s an exciting time to be part of an extraordinary startup that is already successful, yet still early enough to offer its team significant growth, equity, and the opportunity to make a real impact. This position is for an existing vacancy. Roofr is looking for a Director, Product Growth to own how we grow through the product. You’ll work at the intersection of product, data, and go-to-market: designing the activation and expansion paths that keep contractors engaged, surfacing product signals that unlock sales conversations, and building a stronger self-serve experience anchored in friction-less SMB UI/UX. You’ll report to the CPO, sit on the product leadership team, and lead a cross-functional Growth team that includes Engineering, Design, Data Science, and a Principal PM as your direct report. Initial building blocks are already in place. We have a clear activation metric that guides both our self-serve and sales-assist motion, a hybrid model that is actively evolving, and an AI product line in AI Receptionist that is ready to scale. The job is to take what’s working, sharpen it, and build on top of it." Check for any boilerplate: no. Now Responsibilities bullets: - Orchestrate the hybrid motion with Sales: Identify the product signals that indicate a contractor is ready for a sales conversation and build the playbooks that turn those signals into pipeline, across both new subscriber acquisition and expansion of the existing base - Drive activation and expansion: Own the in-product experience that gets new contractors to value fast and design the expansion loops that drive deeper adoption and multi-product retention across the customer base - Grow self-serve revenue: Own the self-serve motion across transactional and subscription products, with particular focus on Measure+ and in-product upgrade paths - Lead the team and the metrics