Lifecycle Operations Manager
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content from posting.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate like interview process, why work for us, etc. Keep substantive info.
We need sections: About the role (maybe from "Who We're Looking For" and description). Responsibilities (list of duties). Requirements (maybe experience). Qualifications (education). Skills (maybe specific). Benefits (list perks). Pay (not mentioned, so omit). Schedule (mention remote-first/hybrid). Ensure we only include sections with real content.
Let's parse.
Posting content:
- Intro: "Who We're Looking For - Lifecycle Operations Manager Clearlink is building a centralized Lifecycle Marketing function ..."
- "The Impact You Will Make" maybe part of About the role.
- "What You Own": bullet list of ownership.
- "Build and scale lifecycle programs": bullet list.
- "Own the platform and the data layer": bullet list.
- "Drive growth through analytics": bullet list.
- "Partner across the business": bullet list.
- "How You'll Work": bullet list.
- "What You Bring": bullet list of requirements.
- "Perks That Set Us Apart": list of benefits.
- "Interviewing at Clearlink": boilerplate to remove.
- "Why Work For Us": boilerplate.
- "Clearlink Partners & Awards": boilerplate.
- "Clearlink Values": maybe not needed? Could be considered culture but maybe not required; but it's substantive? Might be considered fluff but could be kept? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Values maybe not boilerplate but could be considered fluff. Safer to omit.
Thus sections:
About the role: combine intro and impact description.
Responsibilities: combine "What You Own", "Build and scale lifecycle programs", "Own the platform and the data layer", "Drive growth through analytics", "Partner across the business", "How You'll Work". Could be many bullet points.
Requirements: maybe "What You Bring" includes experience, education, etc. Could be Requirements.
Qualifications: maybe education (Bachelor's degree). Could be separate.
Skills: maybe specific skills: Iterable, Digioh, analytics, email authentication, vendor management, communication.
Benefits: list perks.
Schedule: remote-first/hybrid details.
Pay: not mentioned, omit.
Let's craft.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We must not create empty sections.
Let's draft HTML.
First, About the role: prose summarizing.
We'll take paragraphs: "Clearlink is building a centralized Lifecycle Marketing function to power scalable, compliant, performance-driven email programs across our portfolio of brands — including Highspeedinternet, The Penny Hoarder, CableTV and Reviews.org. We're looking for a Lifecycle Operations Manager to own the platforms, data, and programs that make that possible. This role sits at the intersection of product, marketing technology, and analytics. You'll be the hands-on owner of our lifecycle messaging platform (Iterable) and our onsite data capture and identity layer (Digioh), and you'll use that infrastructure to build, test, and scale email programs that grow audience and drive revenue across brands. You'll operate under a business-partner model: you own the channel, the infrastructure, and the best practices, while individual brand teams retain control over audience strategy, messaging, and content. You'll work closely with a Director-level lifecycle strategy lead, brand marketing teams, and our Data/IT organization to keep every program healthy, compliant, and performing. Clearlink is a remote-friendly company, prioritizing virtual and in-person collaboration. This is a remote-first role for candidates who are located outside of Utah and outside of commuting distance. For candidates residing within 50 miles of our Salt Lake City, Utah office, a hybrid schedule of 2-3 days in-office is required."
That's good.
Responsibilities: list bullet points from sections.
Let's extract bullet-like sentences:
From "What You Own":
- Own the email product and lifecycle platform: Iterable implementation — configuration, segmentation logic, and automation workflows — and Digioh as our onsite capture and identity layer, accountable for programs and KPIs they drive across brands.
- Own data quality and deliverability: health of sending infrastructure and customer data — authentication, inbox placement, list hygiene — across every brand.
- Own testing and optimization: analytics and testing discipline behind lifecycle programs, turning results into a backlog of what to build, fix, or scale next.
From "Build and scale lifecycle programs":
- Build and maintain lifecycle programs, segmentation logic, and automation workflows in Iterable across acquisition, onboarding, engagement, and retention.
- Manage subscriber and identity data flows between Digioh, Iterable, and internal systems, ensuring a clean, unified view of the customer across brands.
- Implement and evolve testing frameworks — A/B and multivariate testing, personalization logic, and send-time optimization — as a standard part of how programs are built.
- Grow quality subscribers through capture strategy, placement analysis, and ongoing optimization of subscriber lifetime value.
From "Own the platform and the data layer":
- Own ESP configuration and implementation in Iterable, and the onsite capture/identity layer in Digioh, across all supported brands.
- Ensure consistent implementation of authentication protocols (SPF, DKIM, DMARC) and keep pace with evolving mailbox provider and sender requirements.
- Monitor inbox placement, domain/IP reputation, and complaint rates (e.g., via Google Postmaster Tools), and resolve issues before they impact deliverability.
- Coordinate with IT and Data teams on integrations, tracking, and data warehouse sync so lifecycle data stays reliable and accessible.
- Manage ESP and vendor relationships, holding partners accountable to cost and performance.
From "Drive growth through analytics":
- Report on campaign, program, and channel performance, translating results into clear recommendations for brand and lifecycle leadership.
- Identify new growth opportunities based on program data, emerging lifecycle/email trends, and the competitive landscape.
- Ensure program health metrics — deliverability, engagement, list quality — are visible and trending in the right direction across every brand on the platform.
From "Partner across the business":
- Work under a business-partner model with brand marketing teams: you own the infrastructure and best practices, they own audience strategy, messaging, and content.
- Partner with the Director-level lifecycle strategy lead to keep execution aligned with cross-brand governance, compliance, and best practices.
- Support brand teams in adopting shared lifecycle infrastructure, making their day-to-day experience with the platform a measure of your success.
From "How You'll Work":
- Hold platform-wide standards while adapting to the distinct needs of each brand you support.
- Create order and documentation where a shared, cross-brand system is still being defined.
- Balance hands-on technical execution with the analytical rigor to know what's actually working.
- Move quickly on testing and iteration rather than waiting for a fully-formed plan.
We can combine into a single
list.
Requirements: from "What You Bring":
- Hands-on experience with Iterable or a comparable enterprise ESP/lifecycle messaging platform — configuration, segmentation, and automation.
- Experience with Digioh or a comparable onsite data capture / identity tool is strongly preferred.
- Strong analytics skills: comfort with A/B and multivariate testing, campaign reporting, and turning data into a prioritized roadmap.
- Working knowledge of email authentication and deliverability (SPF, DKIM, DMARC) and how mailbox provider policies affect inbox placement.
- 5+ years of experience in email marketing, marketing technology, or product management, ideally supporting multiple brands or business units.
- Experience managing vendor relationships and holding partners accountable for cost and performance.
- Excellent communication skills, with the ability to work in a business-partner model — owning infrastructure and standards while brand teams own strategy and content.
- Bachelor's degree in Marketing, Business, a related field, or equivalent experience.
We could split Requirements (experience) and Qualifications (education) and Skills (specific tools). But we can also follow instruction: use headings for sections only when posting has real specific content. We have content for Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. Let's decide.
Qualifications: Bachelor's degree.
Skills: Hands-on experience with Iterable, Digioh, analytics, email authentication, vendor management, communication.
Requirements: 5+ years experience, etc.
But there is overlap. To avoid duplication, we can keep one Requirements section covering experience, skills, education. However instruction says prefer few substantive sections over many thin ones. So maybe combine into Responsibilities and Requirements (including qualifications and skills) and Benefits and Schedule.
But we need to use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can omit those not needed. So we will include About the role, Responsibilities, Requirements, Benefits, Schedule. Possibly also Qualifications if we have distinct content (Bachelor's degree). Could put that under Requirements though.
Better to follow instruction: include a section ONLY when posting has real, specific content for it. So we can include Qualifications if we have Bachelor's degree. That's specific. Skills we have specific tools. So we could include Qualifications and Skills.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule.
We must not repeat job title as heading.
Now craft HTML.
We'll need to escape any HTML special characters? Not needed.
Let's produce:
About the role
... prose ...
Responsibilities
- ...
...
Requirements
- 5+ years of experience in email marketing, marketing technology, or product management, ideally supporting multiple brands or business units.
- Experience managing vendor relationships and holding partners accountable for cost and performance.
- Excellent communication skills, with the ability to work in a business-partner model — owning infrastructure and standards while brand teams own strategy and content.
Qualifications
- Bachelor's degree in Marketing, Business, a related field, or equivalent experience.
Skills
- Hands-on experience with Iterable or a comparable enterprise ESP/lifecycle messaging platform — configuration, segmentation, and automation.
- Experience with Digioh or a comparable onsite data capture / identity tool (strongly preferred).
- Strong analytics skills: comfort with A/B and multivariate testing, campaign reporting, and turning data into a prioritized roadmap.
- Working knowledge of email authentication and deliverability (SPF, DKIM, DMARC) and how mailbox provider policies affect inbox placement.
Benefits
- Low-cost, competitive health coverage (domestic partners included) with employer-paid counseling services.
- 401(k) matching after two months of employment, employer matching starting at ~3%.
- Employer-paid lifestyle spending stipends for physical, financial, and emotional wellbeing.
- Competitive time-off balances that accrue weekly (paid weekly).
- 2 weeks of paid parental leave during the first year and up to 9 weeks after one year of employment.
- Generous paid holidays plus additional flex holidays for cultural diversity.
- Flex schedule: remote-first; hybrid requirement for those within 50 miles of Salt Lake City office (in-office Tuesdays and Thursdays, Wednesday flex day).
- Employer-paid life insurance (including coverage for dependents and spouses).
- Employee Resource Groups (ERGs) to foster connections and celebrate diversity.
Schedule
Remote-first role; candidates
for prose. We must not create empty sections. Let's draft HTML. First, About the role: prose summarizing. We'll take paragraphs: "Clearlink is building a centralized Lifecycle Marketing function to power scalable, compliant, performance-driven email programs across our portfolio of brands — including Highspeedinternet, The Penny Hoarder, CableTV and Reviews.org. We're looking for a Lifecycle Operations Manager to own the platforms, data, and programs that make that possible. This role sits at the intersection of product, marketing technology, and analytics. You'll be the hands-on owner of our lifecycle messaging platform (Iterable) and our onsite data capture and identity layer (Digioh), and you'll use that infrastructure to build, test, and scale email programs that grow audience and drive revenue across brands. You'll operate under a business-partner model: you own the channel, the infrastructure, and the best practices, while individual brand teams retain control over audience strategy, messaging, and content. You'll work closely with a Director-level lifecycle strategy lead, brand marketing teams, and our Data/IT organization to keep every program healthy, compliant, and performing. Clearlink is a remote-friendly company, prioritizing virtual and in-person collaboration. This is a remote-first role for candidates who are located outside of Utah and outside of commuting distance. For candidates residing within 50 miles of our Salt Lake City, Utah office, a hybrid schedule of 2-3 days in-office is required." That's good. Responsibilities: list bullet points from sections. Let's extract bullet-like sentences: From "What You Own": - Own the email product and lifecycle platform: Iterable implementation — configuration, segmentation logic, and automation workflows — and Digioh as our onsite capture and identity layer, accountable for programs and KPIs they drive across brands. - Own data quality and deliverability: health of sending infrastructure and customer data — authentication, inbox placement, list hygiene — across every brand. - Own testing and optimization: analytics and testing discipline behind lifecycle programs, turning results into a backlog of what to build, fix, or scale next. From "Build and scale lifecycle programs": - Build and maintain lifecycle programs, segmentation logic, and automation workflows in Iterable across acquisition, onboarding, engagement, and retention. - Manage subscriber and identity data flows between Digioh, Iterable, and internal systems, ensuring a clean, unified view of the customer across brands. - Implement and evolve testing frameworks — A/B and multivariate testing, personalization logic, and send-time optimization — as a standard part of how programs are built. - Grow quality subscribers through capture strategy, placement analysis, and ongoing optimization of subscriber lifetime value. From "Own the platform and the data layer": - Own ESP configuration and implementation in Iterable, and the onsite capture/identity layer in Digioh, across all supported brands. - Ensure consistent implementation of authentication protocols (SPF, DKIM, DMARC) and keep pace with evolving mailbox provider and sender requirements. - Monitor inbox placement, domain/IP reputation, and complaint rates (e.g., via Google Postmaster Tools), and resolve issues before they impact deliverability. - Coordinate with IT and Data teams on integrations, tracking, and data warehouse sync so lifecycle data stays reliable and accessible. - Manage ESP and vendor relationships, holding partners accountable to cost and performance. From "Drive growth through analytics": - Report on campaign, program, and channel performance, translating results into clear recommendations for brand and lifecycle leadership. - Identify new growth opportunities based on program data, emerging lifecycle/email trends, and the competitive landscape. - Ensure program health metrics — deliverability, engagement, list quality — are visible and trending in the right direction across every brand on the platform. From "Partner across the business": - Work under a business-partner model with brand marketing teams: you own the infrastructure and best practices, they own audience strategy, messaging, and content. - Partner with the Director-level lifecycle strategy lead to keep execution aligned with cross-brand governance, compliance, and best practices. - Support brand teams in adopting shared lifecycle infrastructure, making their day-to-day experience with the platform a measure of your success. From "How You'll Work": - Hold platform-wide standards while adapting to the distinct needs of each brand you support. - Create order and documentation where a shared, cross-brand system is still being defined. - Balance hands-on technical execution with the analytical rigor to know what's actually working. - Move quickly on testing and iteration rather than waiting for a fully-formed plan. We can combine into a single
- list.
Requirements: from "What You Bring":
- Hands-on experience with Iterable or a comparable enterprise ESP/lifecycle messaging platform — configuration, segmentation, and automation.
- Experience with Digioh or a comparable onsite data capture / identity tool is strongly preferred.
- Strong analytics skills: comfort with A/B and multivariate testing, campaign reporting, and turning data into a prioritized roadmap.
- Working knowledge of email authentication and deliverability (SPF, DKIM, DMARC) and how mailbox provider policies affect inbox placement.
- 5+ years of experience in email marketing, marketing technology, or product management, ideally supporting multiple brands or business units.
- Experience managing vendor relationships and holding partners accountable for cost and performance.
- Excellent communication skills, with the ability to work in a business-partner model — owning infrastructure and standards while brand teams own strategy and content.
- Bachelor's degree in Marketing, Business, a related field, or equivalent experience.
We could split Requirements (experience) and Qualifications (education) and Skills (specific tools). But we can also follow instruction: use headings for sections only when posting has real specific content. We have content for Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. Let's decide.
Qualifications: Bachelor's degree.
Skills: Hands-on experience with Iterable, Digioh, analytics, email authentication, vendor management, communication.
Requirements: 5+ years experience, etc.
But there is overlap. To avoid duplication, we can keep one Requirements section covering experience, skills, education. However instruction says prefer few substantive sections over many thin ones. So maybe combine into Responsibilities and Requirements (including qualifications and skills) and Benefits and Schedule.
But we need to use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can omit those not needed. So we will include About the role, Responsibilities, Requirements, Benefits, Schedule. Possibly also Qualifications if we have distinct content (Bachelor's degree). Could put that under Requirements though.
Better to follow instruction: include a section ONLY when posting has real, specific content for it. So we can include Qualifications if we have Bachelor's degree. That's specific. Skills we have specific tools. So we could include Qualifications and Skills.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule.
We must not repeat job title as heading.
Now craft HTML.
We'll need to escape any HTML special characters? Not needed.
Let's produce:
- ... ...
- 5+ years of experience in email marketing, marketing technology, or product management, ideally supporting multiple brands or business units.
- Experience managing vendor relationships and holding partners accountable for cost and performance.
- Excellent communication skills, with the ability to work in a business-partner model — owning infrastructure and standards while brand teams own strategy and content.
- Bachelor's degree in Marketing, Business, a related field, or equivalent experience.
- Hands-on experience with Iterable or a comparable enterprise ESP/lifecycle messaging platform — configuration, segmentation, and automation.
- Experience with Digioh or a comparable onsite data capture / identity tool (strongly preferred).
- Strong analytics skills: comfort with A/B and multivariate testing, campaign reporting, and turning data into a prioritized roadmap.
- Working knowledge of email authentication and deliverability (SPF, DKIM, DMARC) and how mailbox provider policies affect inbox placement.
- Low-cost, competitive health coverage (domestic partners included) with employer-paid counseling services.
- 401(k) matching after two months of employment, employer matching starting at ~3%.
- Employer-paid lifestyle spending stipends for physical, financial, and emotional wellbeing.
- Competitive time-off balances that accrue weekly (paid weekly).
- 2 weeks of paid parental leave during the first year and up to 9 weeks after one year of employment.
- Generous paid holidays plus additional flex holidays for cultural diversity.
- Flex schedule: remote-first; hybrid requirement for those within 50 miles of Salt Lake City office (in-office Tuesdays and Thursdays, Wednesday flex day).
- Employer-paid life insurance (including coverage for dependents and spouses).
- Employee Resource Groups (ERGs) to foster connections and celebrate diversity.
About the role
... prose ...
Responsibilities
Requirements
Qualifications
Skills
Benefits
Schedule
Remote-first role; candidates