Director of Lifecycle Marketing

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Inspira Education" (company description) then "The Role", "What You'll Do", "Who You Are", "What We Look For", "Why you'll love Inspira". Also benefits listed: Health, dental, vision insurance, base plans 100% employer paid, Pre-tax benefits (FSA, DCFSA, HSA, Commuter), Flexible paid time off (PTO) and paid holidays, 401(k) with company match. Also schedule: "This is an in-person role requiring 5 days/week in our NYC office (Gramercy)." So we need sections: About the role? Actually we should not repeat job title. Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to include sections only when posting has real specific content. We have content for About the role? The "The Role" paragraph describes role. Could map to "About the role". Responsibilities: "What You'll Do". Requirements/Qualifications/Skills: "Who You Are" and "What We Look For". Benefits: list. Schedule: in-person 5 days/week NYC office. Pay: not mentioned, so omit Pay section. Also we might include "About Inspira Education" as maybe "About the company"? Not in allowed headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should not add other headings. So we need to fit content into those. Could put company description under "About the role"? Might be odd but permissible. Or we could omit company description? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep company description. But we cannot add a heading not in list. Could we embed it in a

before first heading? The instruction: 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...). It might be okay to have other headings but they'd be non-standard. Safer to stick to allowed headings and put company description in a

before first heading or within About the role section. Probably best: start with a

containing company description, then

About the role

with the role description paragraph. Then

Responsibilities

with

of What You'll Do items. Then

Requirements

with
of Who You Are items (experience, expertise). Then maybe

Skills

for technical skills (HubSpot, Braze, SQL, HTML, etc). Then

Benefits

with list. Then

Schedule

with in-person 5 days/week NYC office. No Pay. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO etc. Also remove navigation/legal etc. The posting includes EEO statement at end; we should remove that. Also remove "For more information about our company, please visit our website: Inspira Education Group." That's boilerplate; remove. We need to preserve all substantive information: company description, role description, responsibilities list, who you are list, what we look for list (maybe combine with requirements?), benefits list, schedule. We need to avoid filler like "commensurate with experience" etc. Not present. Let's extract details. Company description paragraph: "Inspira Education Group is one of the fastest-growing edtech startups in the US. We started with a simple mission to democratize access to high-quality coaching so that every student in the world has an equal opportunity to access the best opportunities. As the world’s leading network of top admissions coaches in medical, legal, business, and college studies, we’re building software and services in one place—disrupting long-entrenched application processes with products and experiences that strive to provide an equal platform for candidates from diverse backgrounds worldwide. As one of the fastest-growing edtech firms in the world, we are backed by some of the leading venture capital firms and investors in the world, including Zeev Ventures, Quiet Capital, Craft Ventures and Jeff Fluhr (Founder of Stubhub)." That's substantive. The Role paragraph: "We’re looking for a strategic, hands-on Director of Lifecycle Marketing to drive acquisition and engagement across our portfolio of brands. In this role, you’ll own our full CRM communication strategy by optimizing engagement with existing contacts while expanding our email list and driving more free consultations. You’ll lead campaign execution, A/B testing, and personalization efforts, supported by a CRM Manager, to maximize performance without compromising brand integrity. You’ll collaborate closely with marketing, product, and sales teams to refine our push notification strategy and deepen app engagement. You’ll thrive in this role if you’re a data-driven marketer with a strong analytical mindset, deep expertise in platforms like Braze, Iterable, or HubSpot, and a passion for continuous experimentation. You’re comfortable balancing strategic thinking with tactical execution and enjoy working cross-functionally with Sales, SEO, Performance Marketing, Online Events, Customer Success, and Social Media teams to launch programs that deliver results. Your north star metric? Consultations generated from our contact database. If you’re excited to build impactful lifecycle programs that create meaningful customer relationships and drive real business outcomes then we’d love to hear from you. This is an in-person role requiring 5 days/week in our NYC office (Gramercy)." Note: The last sentence about in-person role is schedule; we might move that to Schedule section. What You'll Do list (each line starts with a verb). We'll convert to
• . List: - Own the end-to-end strategy and execution of lifecycle marketing programs, building clear and personalized user journeys that drive acquisition, engagement, conversion, and retention - Analyze cohort and segment performance regularly to uncover trends, understand the “why” behind user behavior, and develop actionable insights that inform strategy - Develop and execute a robust experimentation roadmap to increase acquisition, engagement, and lifetime value through A/B testing and continuous optimization - Create and manage sophisticated email and SMS campaigns, including drip sequences, targeted newsletters, transactional messages, and upgrade flows, all aimed at increasing product engagement and driving conversion - Identify drop-off points within the user journey and implement targeted, trigger-based campaigns to address friction and improve key KPIs - Ensure compliance with deliverability best practices and maintain a strong sender reputation across all messaging platforms (email and SMS) - Leverage customer segmentation and persona development to tailor messaging, offers, and campaigns that resonate with high-potential customer groups - Collaborate closely with the data team to define and build end-to-end lifecycle reporting and track performance across channels - Lead and grow a team of lifecycle marketers, acting as both a player and coach — mentoring team members, advocating for their work, and rolling up your sleeves to contribute directly when needed - Ensure consistent and personalized messaging across the funnel, delivering the right message to the right person at the right time through the right channel - Track and report on campaign performance and KPIs, such as lead volume, conversion rates, pipeline growth, LTV, and ROI; provide recommendations to optimize results - Forecast marketing outcomes and track progress toward growth and revenue goals - Stay on the cutting edge of AI and martech tools, proactively identifying and implementing technologies that improve efficiency, personalization, and performance across lifecycle programs Who You Are list (requirements): - 6–8+ years of lifecycle marketing experience, ideally in high-consideration or long-sales-cycle environments that require thoughtful lead nurturing strategies - 2–3 years of experience managing and scaling high-performing teams - Deep expertise in HubSpot; familiarity with Braze, Iterable, or similar tools is a strong plus - Proficiency in email and SMS marketing automation, including segmentation, triggers, and personalized flows - Bonus points for experience working with customer data platforms (CDPs) like Simon Data, Iterable, or Optimove - Basic working knowledge of SQL and comfort querying data - Strong understanding of HTML and template scripting languages (e.g., Jinja, Django, or ESP-specific templating systems) - Exceptional copywriting skills with a proven ability to engage target audiences and iterate on messaging based on performance data - Highly analytical mindset, with a track record of using data to inform campaign strategy and drive measurable results - Familiarity with Looker or experience in data transformation is a plus - A balance of creative thinking and analytical rigor. Someone who can conceptualize big ideas and dive into the data - Comfortable rolling up your sleeves and getting into the weeds. A builder, not just a strategist - Able to translate data into clear insights and actionable marketing strategies What We Look For list (cultural traits): - A passion for cultivating authentic connections - Individuals who embody a winning attitude - A mindset fueled by curiosity - Determination to hustle and overcome challenges - An infectious enthusiasm and adaptability - Boundless energy and relentless tenacity We could combine Who You Are and What We Look For into Requirements and Skills sections. But we have headings: Requirements, Qualifications, Skills. We could put experience/education under Requirements, technical skills under Skills, and cultural traits under Qualifications? Or just use Requirements for all. But we need to avoid thin sections. Perhaps: - Requirements: experience, team management, expertise in HubSpot, familiarity with Braze/Iterable, proficiency in email/SMS automation, CDP experience, SQL, HTML/template scripting, copywriting, analytical mindset, Looker/data transformation, creative/analytical balance, builder mindset, translating data. - Skills: maybe we could separate technical skills: HubSpot, Braze/Iterable, email/SMS automation, CDP, SQL, HTML/template scripting, Looker. But that duplicates. Better: Use Requirements for experience and expertise, Skills for technical proficiencies, Qualifications for cultural traits. Let's map: Requirements (

  Requirements

  ): - 6–8+ years of lifecycle marketing experience, ideally in high-consideration or long-sales-cycle environments that require thoughtful lead nurturing strategies - 2–3 years of experience managing and scaling high-performing teams Qualifications (

  Qualifications

  ): - A passion for cultivating authentic connections - Individuals who embody a winning attitude - A mindset fueled by curiosity - Determination to hustle and overcome challenges - An infectious enthusiasm and adaptability - Boundless energy and relentless tenacity Skills (

  Skills

  ): - Deep expertise in HubSpot; familiarity with Braze, Iterable, or similar tools is a strong plus - Proficiency in email and SMS marketing automation, including segmentation, triggers, and personalized flows - Bonus points for experience working with customer data platforms (CDPs) like Simon Data, Iterable, or Optimove - Basic working knowledge of SQL and comfort querying data - Strong understanding of HTML and template scripting languages (e.g., Jinja, Django, or ESP-specific templating systems) - Exceptional copywriting skills with a proven ability to engage target audiences and iterate on messaging based on performance data - Highly analytical mindset, with a track record of using data to inform campaign strategy and drive measurable results - Familiarity with Looker or experience in data transformation is a plus - A balance of creative thinking and analytical rigor. Someone who can conceptualize big ideas and dive into the data - Comfortable rolling up your sleeves and getting into the weeds. A builder, not just a strategist - Able to translate data into clear insights and actionable marketing strategies But note some items overlap with Requirements (like analytical mindset). Might be okay. Alternatively, we could just have Requirements and Skills and omit Qualifications. But we have cultural traits; they are substantive. Could put them under Requirements as well. But then we would have many items under