Senior Growth Marketing Manager | Housing

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Benefits, Pay (if present), maybe Skills? The posting includes "About EliseAI" (company description) but we should not repeat job title as heading. Should we include "About EliseAI"? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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. We need to include sections only when posting has real, specific content. The posting includes "About EliseAI" (company overview). Should we include a section for that? The allowed headings list includes "About the role", not "About EliseAI". 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 suggests those as examples. Probably we should include "About EliseAI" as a section? It's not in the list but could be considered a heading. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected sections. They didn't say we cannot have other headings, but they want us to use those headings for sections. The posting includes "About EliseAI" which is a company overview; maybe we should include it under a heading like "About EliseAI" but not required. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." It doesn't forbid other headings. However they gave examples; we can include "About EliseAI" as a heading if we want, but maybe better to follow the pattern: include sections for About the role, Responsibilities, Requirements, Benefits, Pay. Also maybe "Qualifications" could be merged with Requirements. The posting has "Requirements" section. Also "Why Join" section includes benefits and culture; but we already have Benefits section. The "Why Join" includes growth and impact etc. Could be considered part of Benefits or culture; but we can include as a separate section like "Why Join EliseAI"? Not in list. Might be better to incorporate into Benefits or maybe a "Culture" section not required. Since they said prefer a few substantive sections over many thin ones, we could combine "Why Join" into Benefits or maybe a separate "About EliseAI" and "Why Join". But we need to preserve all substantive information. Let's think: The posting includes: - About EliseAI (company description) - About The Role (role description) - Key Responsibilities (list) - Requirements (list) - Why Join Growth and impact (paragraph about growth, impact, learning) - Benefits (list) - Job Compensation Range (Pay) - Additional details about total compensation and benefits will be provided... - EEO boilerplate etc (remove) - At-will employment etc (remove) - Fair Chance Ordinance etc (remove) - Accommodation contact (maybe minor metadata, could be folded into a short p or drop) We need to remove boilerplate: EEO, at-will, fair chance, accommodation contact? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO paragraph, at-will, fair chance, accommodation contact. Also remove duplicated lines (none). Also remove application instructions (none present besides maybe contact for accommodation). So we drop those. We need to preserve all substantive information: company description, role description, responsibilities, requirements, why join (growth and impact), benefits, pay. We need to format with

headings and

• for lists,

  for prose. We should not include headings with filler text. So each heading must have substantive content. Potential sections: - About EliseAI (company overview) – could be

  About EliseAI

  with

  ... - About the role –

  About the Role

  with

  ... - Responsibilities –

  Key Responsibilities

  with
  • ... - Requirements –

    Requirements

    with
    • ... - Why Join EliseAI – maybe

      Why Join EliseAI

      with

      ... - Benefits –

      Benefits

      with
      • ... - Pay –

        Pay

        or

        Compensation

        with

        ... The instruction examples include Pay, Benefits, Schedule. So we can use Pay. We need to avoid creating Schedule section if not present. We should not include Qualifications or Skills unless present; we have Requirements which could be considered qualifications; but we can keep Requirements. We need to ensure we don't repeat job title as heading. The job title is "Senior Growth Marketing Manager". We are not using that as heading. Now let's extract content. About EliseAI paragraph: "At EliseAI, we're improving the industries that matter most: housing and healthcare. Everyone needs a place to live and access to quality healthcare, yet both are often harder to secure than they should be. By integrating AI agents deeply into existing workflows, we make them more efficient, reduce costs, and improve the experience for everyone. Housing: We simplify how renters tour apartments, sign leases, submit maintenance requests, and stay connected with their property team—bringing everything they need for their home into one place.Healthcare: We make it easy to schedule appointments, complete intake forms, and we help patients communicate with providers, so everyone can focus on health instead of paperwork. With EliseAI, organizations reduce manual work, improve accessibility, and deliver a seamless experience across essential services. We recently raised a $250 million Series E round led by Andreessen Horowitz to accelerate this mission." We need to preserve that exactly, maybe minor formatting. About The Role: "We are looking for a Senior Growth Marketing Manager to drive our paid acquisition strategy and website conversion optimization efforts. This is a high-impact, cross-functional role sitting at the intersection of GTM, data, and product. You’ll design and optimize full-funnel performance campaigns across paid channels (LinkedIn, Meta, Google Search, and others) and drive experimentation to improve lead quality and conversion rates on our website. You’ll also partner closely with product marketing, design, engineering, and GTM teams to test hypotheses, uncover insights, and scale what works to drive measurable pipeline growth. This role is ideal for someone who thrives in a high-velocity testing environment, obsesses over data-driven decision making, and has a track record of building efficient, scalable growth systems." Key Responsibilities list: - Own and optimize paid acquisition channels (LinkedIn, Meta, SEM, and emerging platforms) to drive qualified pipeline and ROI - Manage full-funnel performance metrics and identifying new opportunities for efficiency and scale - Design and run new growth experiments: define hypotheses, structure A/B tests, analyze performance, and translate learnings into repeatable playbooks - Lead website conversion rate optimization (CRO) efforts in partnership with product and design teams: experimenting with landing pages, messaging, and UX flows to improve conversion - Collaborate cross-functionally to dial in attribution, messaging, and conversion goals - Continuously evolve our marketing stack: evaluate and implement tools that enhance automation, analytics, and campaign efficiency - Attract top-tier talent to join our driven team - Move at rocket speed, build something massive. We’re scaling fast, solving real client problems with precision and ambition. Here, you own your impact; full autonomy, no micromanagement, no fluff. We hire the best, expect the best, and give you the masterclass of your career. It’s hard, it’s intense, and it’s the most rewarding work you’ll ever do. If you’re hungry, driven, and ready to build something massive, climb aboard. Note: The last bullet seems to be a paragraph not a bullet; but it's part of responsibilities? Actually after "Attract top-tier talent to join our driven team" there is a paragraph about culture. Might be better to treat that as part of "Why Join" but it's under responsibilities block. However we can keep it as a bullet? It's not a bullet; it's a paragraph. We could treat it as a separate paragraph under responsibilities. But the instruction: Use

        • for any list of duties/requirements/benefits. So we should only use
          • for items that are list items. The responsibilities list includes bullet points; the final paragraph is not a bullet. So we should output
            • for each bullet, and then a

              for the paragraph after the list. Thus responsibilities: list items 1-6 (maybe 7 if we count attract top-tier talent as bullet). Actually "Attract top-tier talent to join our driven team" is a bullet point (starts with a verb). Then after that there is a paragraph about moving at rocket speed etc. So we will have 7 bullet items? Let's see: Bullet list from posting: Own and optimize paid acquisition channels (LinkedIn, Meta, SEM, and emerging platforms) to drive qualified pipeline and ROI Manage full-funnel performance metrics and identifying new opportunities for efficiency and scale Design and run new growth experiments: define hypotheses, structure A/B tests, analyze performance, and translate learnings into repeatable playbooks Lead website conversion rate optimization (CRO) efforts in partnership with product and design teams: experimenting with landing pages, messaging, and UX flows to improve conversion Collaborate cross-functionally to dial in attribution, messaging, and conversion goals Continuously evolve our marketing stack: evaluate and implement tools that enhance automation, analytics, and campaign efficiency Attract top-tier talent to join our driven team Then paragraph: "Move at rocket speed, build something massive. We’re scaling fast, solving real client problems with precision and ambition. Here, you own your impact; full autonomy, no micromanagement, no fluff. We hire the best, expect the best, and give you the masterclass of your career. It’s hard, it’s intense, and it’s the most rewarding work you’ll ever do. If you’re hungry, driven, and ready to build something massive, climb aboard." Thus we will output

              with 7
              • items, then a

                for that paragraph. Requirements list: - 6+ years of experience in growth, performance marketing, or growth product roles at high-growth technology companies - Proven success scaling paid channels efficiently while deploying large spend - Deeply familiarity with CRO frameworks, testing methodologies, and landing page optimization - Strong analytical skills: comfortable in GA4, Looker, or other BI tools - An “always-be-testing” mindset and comfort working in fast-paced, independent environments - Working knowledge of Salesforce, HubSpot, and other similar systems - A collaborative and creative mindset, energized by solving complex growth problems - Willingness to work in person at our office 4-5 days a week All bullet points. Why Join section: "Why Join Growth and impact. It’s not often that you can get in on the ground floor of a funded (unicorn!) startup that’s scaling so fast. That means that instead of following a playbook, you’ll be writing it. Every single day you will be challenged to identify how we can scale and execute on it. You’ll learn what works when you succeed and what doesn’t when you fail. Either way, the rest of the team will be here to support you." We need to preserve that exactly.