Director, Personalization & CRM Marketing Operations
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as a heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into 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. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
The posting includes:
- About This Role (intro paragraph)
- Why This Role Matters (bullet points? Actually paragraphs)
- What You’ll Do (list of responsibilities)
- How We Work (paragraph)
- What You Bring (requirements/qualifications)
- How We Reward You (benefits list)
- Then some more paragraphs about culture etc (maybe not needed)
- Diversity statement (EEO) - remove.
We need to decide sections: About the role (intro), Responsibilities (What You’ll Do), Requirements/Qualifications (What You Bring), Benefits (How We Reward You). Possibly also "How We Work" could be part of About the role or separate? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include "How We Work" maybe as part of About the role or as a separate section like "Work Environment". But not in list; we can choose to include only those headings that have substantive content. The posting includes "How We Work" describing in-person collaboration. That's substantive. Could be a section like "Work Environment" but not in prescribed list. However we can still use
for any section heading; the examples are not exhaustive. So we can add a heading like "How We Work". That's fine.
We also have "Why This Role Matters" which is like a motivation section; could be part of About the role or separate. Could be a heading like "Why This Role Matters". That's substantive.
We need to avoid filler. No Pay or Schedule sections because not mentioned.
We need to use - for any list of duties/requirements/benefits. So for responsibilities list, we need to convert bullet points into
- . The responsibilities are listed with headings like "Agile Governance & Execution", "AI Innovation & Pilot Leadership", etc. Each has sub-bullets. We need to preserve all substantive information. So we can create a
for responsibilities, each - containing the heading and its details maybe as
inside? But instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we can treat each duty as a
- containing maybe heading and then description. That's okay.
Similarly for requirements: "What You Bring" includes bullet points (starting with "12+ years..." etc). We'll make a
- list.
Benefits: "How We Reward You" includes a list of benefits. We'll make a
- .
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting.
We must remove boilerplate: EEO statement, diversity statement, maybe also the line "Do the best work of your life at Realtor.com® ..."? That's promotional but maybe substantive? It's more fluff but still part of posting. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The promotional paragraphs may be considered not boilerplate but could be kept? It says preserve ALL substantive information; do NOT invent or summarize away detail. The promotional paragraphs are substantive? They are more marketing fluff but still part of posting. I'd keep them as prose
. However they might be considered boilerplate? Not sure. Safer to keep them as they are not explicitly listed to remove. The instruction only says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we keep the rest.
Thus we need to output HTML fragment with sections:
About the Role
... (intro paragraph plus maybe Why This Role Matters? Could combine). But we have separate "Why This Role Matters" heading; we could make that its own
. Let's decide.
We have:
- About This Role (intro paragraph)
- Why This Role Matters (several bullet-like paragraphs)
- What You’ll Do (responsibilities)
- How We Work (paragraph)
- What You Bring (requirements)
- How We Reward You (benefits)
- Additional culture paragraphs (maybe keep as prose under a section like "Our Culture" or just after benefits). Could add a heading "Our Culture". But not required.
We need to avoid too many thin sections; prefer a few substantive sections. Could combine About the Role and Why This Role Matters into one section "About the Role". Or we could have separate sections but that's many. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine intro and why it matters into About the Role. Then Responsibilities, Requirements, Benefits, How We Work (maybe as part of About the Role?). But How We Work is distinct; could be its own section "Work Environment". That's okay.
Thus sections: About the Role (includes intro + why it matters), Responsibilities, How We Work, Requirements, Benefits. That's 5 sections.
We need to ensure we don't create Pay/Schedule sections.
Now we need to extract the exact text.
Let's copy the relevant parts.
**About This Role** paragraph:
"Recognized as the No. 1 site trusted by real estate professionals, Realtor.com® has been at the forefront of online real estate for over 25 years, connecting buyers, sellers, and renters with trusted insights and expert guidance to find their perfect home. Through its robust suite of tools, Realtor.com® not only makes a significant impact on the real estate industry at large, but for consumers, navigating the biggest purchase they will make in their life, by providing a user experience that is easy to use, easy to understand, and most of all, easy to make decisions. Join us on our mission to empower more people to find their way home by breaking barriers to entry, making the right connections, and building confidence through expert guidance. The Director of Personalization \& CRM Marketing Operations will lead and build our CRM \& Personalization ecosystem. This role bridges high\-level business strategy and technical execution, ensuring the continued health and output of our customer engagement and personalization platforms — primarily Braze and Cordial, in addition to a soon\-to\-be\-established CDP (Segment Engage). You will serve as the primary orchestrator between Marketing, Product, and Engineering, keeping critical infrastructure migrations on track, guiding a live AI decisioning proof of concept, and improving our Agile team. You will lead the Ops team’s AI transformation — with the goal to drive more efficiencies and campaign delivery through AI. This is a hands\-on leadership role with real ownership: you will represent CRM Operations in executive reviews, remove blockers for CRM and CDP ops developers, and ensure the team continues to accelerate output while maintaining quality."
**Why This Role Matters** section:
"AI\-forward work: Lead and monitor a live AI decisioning pilot, moving CRM from static automation to predictive engagement. Access to AI tools you need to make yourself and your team as efficient as possible, doubling the team’s output.Cross\-functional hub: You’ll sit at the intersection of Product, Engineering, Data Science, and Marketing — never siloed.Modern stack: Deep daily work in Braze, Cordial, Segment Engage, Hightouch, and Snowflake — the tools that power consumer engagement at scale.High visibility: Represent Operations directly in Weekly Business Reviews alongside senior leadership, with clear impact on revenue metrics."
Note there are no spaces after colons? We'll keep as is.
**What You’ll Do** section includes headings and bullet points.
Let's extract:
"What You’ll Do
Agile Governance \& Execution*Oversee Scrum processes across multiple technical CRM teams, including daily stand\-ups, bi\-weekly sprint planning, retrospectives, and backlog refinement sessions. Hold the team accountable to commitments and push for more innovation and speed.Partner with CRM Product Owners to balance high\-impact initiatives alongside essential backend maintenance and infrastructure work.Identify and remove blockers for developers and engineers to maintain delivery velocity throughout the engagement.Monitor ongoing Snowflake\-to\-Braze and Cordial data imports via Hightouch and future Segment Engage; escalate and resolve data sync failures quickly.AI Innovation \& Pilot Leadership*Manage the AI Decisioning lifecycle through build, launch, and performance monitoring.Lead your team in an AI transformation — accelerating productivity, CRM campaign coding, and ultimately output.Vendor \& Platform Management*Serve as the primary technical point of contact for Braze, Cordial, and Segment Engage, owning bi\-weekly technical check\-ins and solution reviews.Monitor platform health across platforms; triage alerts and coordinate with MarTech and Notifications engineering teams when issues arise.Ensure all MarTech imports have active monitoring and consistent alert naming conventions.Cross\-Functional Stakeholder Alignment*Represent CRM Operations in Weekly Business Reviews — translating complex operational issues into clear performance insights for executive leadership.Partner with Product Marketing, Performance Marketing, Software Engineering, and Analytics to keep the CRM roadmap aligned with broader company goals.Lead bi\-weekly MarTech/CRM Sprint Grooming sessions with Product Owners to review and prioritize development tickets.People Leadership*Manage a team of CRM \& CDP ops developersMaintain weekly 1:1s with a team of CRM ops developers, engineers, and Product Owners to improve culture and unblock work.Provide mentorship and clear direction across CRM Ops, Product Management, Scrum, and cross\-functional engineering partners.Act as the escalation point for complex integration issues, production incidents, or competing sprint priorities."
Note there are asterisks used as delimiters. We need to convert to list items. Each heading before an asterisk is a subsection title. We'll produce
- Agile Governance & Execution: ...
etc.
We need to preserve the content exactly, but we can replace escaped characters like \& with &, \- with -, etc. The original text includes backslashes before special characters likely due to markdown escaping. We should output plain text without those backslashes. So we need to unescape: replace "\&" with "&", "\-" with "-", "\*" maybe not needed. Also there are "\*" used as delimiters; we can ignore them.
Thus we need to produce clean text.
**How We Work** paragraph:
"We balance creativity and innovation on a foundation of in\-person collaboration. For most roles, our employees work three or more days in our offices, where they have the opportunity to collaborate in\-person, adding richness to our culture and knitting us closer together."
Unescape.
**What You Bring** (requirements):
"What You Bring
12\+ years of experience in CRM or marketing operations, with at least 5 years leading technical teams including CRM ops developers.Bachelor’s degree or equivalent experience.Deep hands\-on expertise with enterprise ESP/CRM platforms — specifically Braze and/or Cordial — including campaign architecture, audience logic, and platform administration.Experience leading a CRM ops team at scale (with
for prose. Do NOT repeat job title as a heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into 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. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. The posting includes: - About This Role (intro paragraph) - Why This Role Matters (bullet points? Actually paragraphs) - What You’ll Do (list of responsibilities) - How We Work (paragraph) - What You Bring (requirements/qualifications) - How We Reward You (benefits list) - Then some more paragraphs about culture etc (maybe not needed) - Diversity statement (EEO) - remove. We need to decide sections: About the role (intro), Responsibilities (What You’ll Do), Requirements/Qualifications (What You Bring), Benefits (How We Reward You). Possibly also "How We Work" could be part of About the role or separate? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include "How We Work" maybe as part of About the role or as a separate section like "Work Environment". But not in list; we can choose to include only those headings that have substantive content. The posting includes "How We Work" describing in-person collaboration. That's substantive. Could be a section like "Work Environment" but not in prescribed list. However we can still use
for any section heading; the examples are not exhaustive. So we can add a heading like "How We Work". That's fine.
We also have "Why This Role Matters" which is like a motivation section; could be part of About the role or separate. Could be a heading like "Why This Role Matters". That's substantive.
We need to avoid filler. No Pay or Schedule sections because not mentioned.
We need to use - for any list of duties/requirements/benefits. So for responsibilities list, we need to convert bullet points into
- . The responsibilities are listed with headings like "Agile Governance & Execution", "AI Innovation & Pilot Leadership", etc. Each has sub-bullets. We need to preserve all substantive information. So we can create a
for responsibilities, each - containing the heading and its details maybe as
inside? But instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we can treat each duty as a
- containing maybe heading and then description. That's okay.
Similarly for requirements: "What You Bring" includes bullet points (starting with "12+ years..." etc). We'll make a
- list.
Benefits: "How We Reward You" includes a list of benefits. We'll make a
- .
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting.
We must remove boilerplate: EEO statement, diversity statement, maybe also the line "Do the best work of your life at Realtor.com® ..."? That's promotional but maybe substantive? It's more fluff but still part of posting. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The promotional paragraphs may be considered not boilerplate but could be kept? It says preserve ALL substantive information; do NOT invent or summarize away detail. The promotional paragraphs are substantive? They are more marketing fluff but still part of posting. I'd keep them as prose
. However they might be considered boilerplate? Not sure. Safer to keep them as they are not explicitly listed to remove. The instruction only says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we keep the rest.
Thus we need to output HTML fragment with sections:
About the Role
... (intro paragraph plus maybe Why This Role Matters? Could combine). But we have separate "Why This Role Matters" heading; we could make that its own
. Let's decide.
We have:
- About This Role (intro paragraph)
- Why This Role Matters (several bullet-like paragraphs)
- What You’ll Do (responsibilities)
- How We Work (paragraph)
- What You Bring (requirements)
- How We Reward You (benefits)
- Additional culture paragraphs (maybe keep as prose under a section like "Our Culture" or just after benefits). Could add a heading "Our Culture". But not required.
We need to avoid too many thin sections; prefer a few substantive sections. Could combine About the Role and Why This Role Matters into one section "About the Role". Or we could have separate sections but that's many. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine intro and why it matters into About the Role. Then Responsibilities, Requirements, Benefits, How We Work (maybe as part of About the Role?). But How We Work is distinct; could be its own section "Work Environment". That's okay.
Thus sections: About the Role (includes intro + why it matters), Responsibilities, How We Work, Requirements, Benefits. That's 5 sections.
We need to ensure we don't create Pay/Schedule sections.
Now we need to extract the exact text.
Let's copy the relevant parts.
**About This Role** paragraph:
"Recognized as the No. 1 site trusted by real estate professionals, Realtor.com® has been at the forefront of online real estate for over 25 years, connecting buyers, sellers, and renters with trusted insights and expert guidance to find their perfect home. Through its robust suite of tools, Realtor.com® not only makes a significant impact on the real estate industry at large, but for consumers, navigating the biggest purchase they will make in their life, by providing a user experience that is easy to use, easy to understand, and most of all, easy to make decisions. Join us on our mission to empower more people to find their way home by breaking barriers to entry, making the right connections, and building confidence through expert guidance. The Director of Personalization \& CRM Marketing Operations will lead and build our CRM \& Personalization ecosystem. This role bridges high\-level business strategy and technical execution, ensuring the continued health and output of our customer engagement and personalization platforms — primarily Braze and Cordial, in addition to a soon\-to\-be\-established CDP (Segment Engage). You will serve as the primary orchestrator between Marketing, Product, and Engineering, keeping critical infrastructure migrations on track, guiding a live AI decisioning proof of concept, and improving our Agile team. You will lead the Ops team’s AI transformation — with the goal to drive more efficiencies and campaign delivery through AI. This is a hands\-on leadership role with real ownership: you will represent CRM Operations in executive reviews, remove blockers for CRM and CDP ops developers, and ensure the team continues to accelerate output while maintaining quality."
**Why This Role Matters** section:
"AI\-forward work: Lead and monitor a live AI decisioning pilot, moving CRM from static automation to predictive engagement. Access to AI tools you need to make yourself and your team as efficient as possible, doubling the team’s output.Cross\-functional hub: You’ll sit at the intersection of Product, Engineering, Data Science, and Marketing — never siloed.Modern stack: Deep daily work in Braze, Cordial, Segment Engage, Hightouch, and Snowflake — the tools that power consumer engagement at scale.High visibility: Represent Operations directly in Weekly Business Reviews alongside senior leadership, with clear impact on revenue metrics."
Note there are no spaces after colons? We'll keep as is.
**What You’ll Do** section includes headings and bullet points.
Let's extract:
"What You’ll Do
Agile Governance \& Execution*Oversee Scrum processes across multiple technical CRM teams, including daily stand\-ups, bi\-weekly sprint planning, retrospectives, and backlog refinement sessions. Hold the team accountable to commitments and push for more innovation and speed.Partner with CRM Product Owners to balance high\-impact initiatives alongside essential backend maintenance and infrastructure work.Identify and remove blockers for developers and engineers to maintain delivery velocity throughout the engagement.Monitor ongoing Snowflake\-to\-Braze and Cordial data imports via Hightouch and future Segment Engage; escalate and resolve data sync failures quickly.AI Innovation \& Pilot Leadership*Manage the AI Decisioning lifecycle through build, launch, and performance monitoring.Lead your team in an AI transformation — accelerating productivity, CRM campaign coding, and ultimately output.Vendor \& Platform Management*Serve as the primary technical point of contact for Braze, Cordial, and Segment Engage, owning bi\-weekly technical check\-ins and solution reviews.Monitor platform health across platforms; triage alerts and coordinate with MarTech and Notifications engineering teams when issues arise.Ensure all MarTech imports have active monitoring and consistent alert naming conventions.Cross\-Functional Stakeholder Alignment*Represent CRM Operations in Weekly Business Reviews — translating complex operational issues into clear performance insights for executive leadership.Partner with Product Marketing, Performance Marketing, Software Engineering, and Analytics to keep the CRM roadmap aligned with broader company goals.Lead bi\-weekly MarTech/CRM Sprint Grooming sessions with Product Owners to review and prioritize development tickets.People Leadership*Manage a team of CRM \& CDP ops developersMaintain weekly 1:1s with a team of CRM ops developers, engineers, and Product Owners to improve culture and unblock work.Provide mentorship and clear direction across CRM Ops, Product Management, Scrum, and cross\-functional engineering partners.Act as the escalation point for complex integration issues, production incidents, or competing sprint priorities."
Note there are asterisks used as delimiters. We need to convert to list items. Each heading before an asterisk is a subsection title. We'll produce
- Agile Governance & Execution: ...
etc.
We need to preserve the content exactly, but we can replace escaped characters like \& with &, \- with -, etc. The original text includes backslashes before special characters likely due to markdown escaping. We should output plain text without those backslashes. So we need to unescape: replace "\&" with "&", "\-" with "-", "\*" maybe not needed. Also there are "\*" used as delimiters; we can ignore them.
Thus we need to produce clean text.
**How We Work** paragraph:
"We balance creativity and innovation on a foundation of in\-person collaboration. For most roles, our employees work three or more days in our offices, where they have the opportunity to collaborate in\-person, adding richness to our culture and knitting us closer together."
Unescape.
**What You Bring** (requirements):
"What You Bring
12\+ years of experience in CRM or marketing operations, with at least 5 years leading technical teams including CRM ops developers.Bachelor’s degree or equivalent experience.Deep hands\-on expertise with enterprise ESP/CRM platforms — specifically Braze and/or Cordial — including campaign architecture, audience logic, and platform administration.Experience leading a CRM ops team at scale (with
- . The responsibilities are listed with headings like "Agile Governance & Execution", "AI Innovation & Pilot Leadership", etc. Each has sub-bullets. We need to preserve all substantive information. So we can create a
- for responsibilities, each
- containing the heading and its details maybe as
inside? But instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we can treat each duty as a
- containing maybe heading and then description. That's okay.
Similarly for requirements: "What You Bring" includes bullet points (starting with "12+ years..." etc). We'll make a
- list.
Benefits: "How We Reward You" includes a list of benefits. We'll make a
- .
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting.
We must remove boilerplate: EEO statement, diversity statement, maybe also the line "Do the best work of your life at Realtor.com® ..."? That's promotional but maybe substantive? It's more fluff but still part of posting. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The promotional paragraphs may be considered not boilerplate but could be kept? It says preserve ALL substantive information; do NOT invent or summarize away detail. The promotional paragraphs are substantive? They are more marketing fluff but still part of posting. I'd keep them as prose
. However they might be considered boilerplate? Not sure. Safer to keep them as they are not explicitly listed to remove. The instruction only says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we keep the rest. Thus we need to output HTML fragment with sections:
About the Role
... (intro paragraph plus maybe Why This Role Matters? Could combine). But we have separate "Why This Role Matters" heading; we could make that its own
. Let's decide. We have: - About This Role (intro paragraph) - Why This Role Matters (several bullet-like paragraphs) - What You’ll Do (responsibilities) - How We Work (paragraph) - What You Bring (requirements) - How We Reward You (benefits) - Additional culture paragraphs (maybe keep as prose under a section like "Our Culture" or just after benefits). Could add a heading "Our Culture". But not required. We need to avoid too many thin sections; prefer a few substantive sections. Could combine About the Role and Why This Role Matters into one section "About the Role". Or we could have separate sections but that's many. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine intro and why it matters into About the Role. Then Responsibilities, Requirements, Benefits, How We Work (maybe as part of About the Role?). But How We Work is distinct; could be its own section "Work Environment". That's okay. Thus sections: About the Role (includes intro + why it matters), Responsibilities, How We Work, Requirements, Benefits. That's 5 sections. We need to ensure we don't create Pay/Schedule sections. Now we need to extract the exact text. Let's copy the relevant parts. **About This Role** paragraph: "Recognized as the No. 1 site trusted by real estate professionals, Realtor.com® has been at the forefront of online real estate for over 25 years, connecting buyers, sellers, and renters with trusted insights and expert guidance to find their perfect home. Through its robust suite of tools, Realtor.com® not only makes a significant impact on the real estate industry at large, but for consumers, navigating the biggest purchase they will make in their life, by providing a user experience that is easy to use, easy to understand, and most of all, easy to make decisions. Join us on our mission to empower more people to find their way home by breaking barriers to entry, making the right connections, and building confidence through expert guidance. The Director of Personalization \& CRM Marketing Operations will lead and build our CRM \& Personalization ecosystem. This role bridges high\-level business strategy and technical execution, ensuring the continued health and output of our customer engagement and personalization platforms — primarily Braze and Cordial, in addition to a soon\-to\-be\-established CDP (Segment Engage). You will serve as the primary orchestrator between Marketing, Product, and Engineering, keeping critical infrastructure migrations on track, guiding a live AI decisioning proof of concept, and improving our Agile team. You will lead the Ops team’s AI transformation — with the goal to drive more efficiencies and campaign delivery through AI. This is a hands\-on leadership role with real ownership: you will represent CRM Operations in executive reviews, remove blockers for CRM and CDP ops developers, and ensure the team continues to accelerate output while maintaining quality." **Why This Role Matters** section: "AI\-forward work: Lead and monitor a live AI decisioning pilot, moving CRM from static automation to predictive engagement. Access to AI tools you need to make yourself and your team as efficient as possible, doubling the team’s output.Cross\-functional hub: You’ll sit at the intersection of Product, Engineering, Data Science, and Marketing — never siloed.Modern stack: Deep daily work in Braze, Cordial, Segment Engage, Hightouch, and Snowflake — the tools that power consumer engagement at scale.High visibility: Represent Operations directly in Weekly Business Reviews alongside senior leadership, with clear impact on revenue metrics." Note there are no spaces after colons? We'll keep as is. **What You’ll Do** section includes headings and bullet points. Let's extract: "What You’ll Do Agile Governance \& Execution*Oversee Scrum processes across multiple technical CRM teams, including daily stand\-ups, bi\-weekly sprint planning, retrospectives, and backlog refinement sessions. Hold the team accountable to commitments and push for more innovation and speed.Partner with CRM Product Owners to balance high\-impact initiatives alongside essential backend maintenance and infrastructure work.Identify and remove blockers for developers and engineers to maintain delivery velocity throughout the engagement.Monitor ongoing Snowflake\-to\-Braze and Cordial data imports via Hightouch and future Segment Engage; escalate and resolve data sync failures quickly.AI Innovation \& Pilot Leadership*Manage the AI Decisioning lifecycle through build, launch, and performance monitoring.Lead your team in an AI transformation — accelerating productivity, CRM campaign coding, and ultimately output.Vendor \& Platform Management*Serve as the primary technical point of contact for Braze, Cordial, and Segment Engage, owning bi\-weekly technical check\-ins and solution reviews.Monitor platform health across platforms; triage alerts and coordinate with MarTech and Notifications engineering teams when issues arise.Ensure all MarTech imports have active monitoring and consistent alert naming conventions.Cross\-Functional Stakeholder Alignment*Represent CRM Operations in Weekly Business Reviews — translating complex operational issues into clear performance insights for executive leadership.Partner with Product Marketing, Performance Marketing, Software Engineering, and Analytics to keep the CRM roadmap aligned with broader company goals.Lead bi\-weekly MarTech/CRM Sprint Grooming sessions with Product Owners to review and prioritize development tickets.People Leadership*Manage a team of CRM \& CDP ops developersMaintain weekly 1:1s with a team of CRM ops developers, engineers, and Product Owners to improve culture and unblock work.Provide mentorship and clear direction across CRM Ops, Product Management, Scrum, and cross\-functional engineering partners.Act as the escalation point for complex integration issues, production incidents, or competing sprint priorities." Note there are asterisks used as delimiters. We need to convert to list items. Each heading before an asterisk is a subsection title. We'll produce
- Agile Governance & Execution: ... etc. We need to preserve the content exactly, but we can replace escaped characters like \& with &, \- with -, etc. The original text includes backslashes before special characters likely due to markdown escaping. We should output plain text without those backslashes. So we need to unescape: replace "\&" with "&", "\-" with "-", "\*" maybe not needed. Also there are "\*" used as delimiters; we can ignore them. Thus we need to produce clean text. **How We Work** paragraph: "We balance creativity and innovation on a foundation of in\-person collaboration. For most roles, our employees work three or more days in our offices, where they have the opportunity to collaborate in\-person, adding richness to our culture and knitting us closer together." Unescape. **What You Bring** (requirements): "What You Bring 12\+ years of experience in CRM or marketing operations, with at least 5 years leading technical teams including CRM ops developers.Bachelor’s degree or equivalent experience.Deep hands\-on expertise with enterprise ESP/CRM platforms — specifically Braze and/or Cordial — including campaign architecture, audience logic, and platform administration.Experience leading a CRM ops team at scale (with
- .
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting.
We must remove boilerplate: EEO statement, diversity statement, maybe also the line "Do the best work of your life at Realtor.com® ..."? That's promotional but maybe substantive? It's more fluff but still part of posting. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The promotional paragraphs may be considered not boilerplate but could be kept? It says preserve ALL substantive information; do NOT invent or summarize away detail. The promotional paragraphs are substantive? They are more marketing fluff but still part of posting. I'd keep them as prose
- list.
Benefits: "How We Reward You" includes a list of benefits. We'll make a
- for any list of duties/requirements/benefits, and
- containing the heading and its details maybe as