Senior AB Journey Manager - Onboarding

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. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. We need to parse the posting. Content sections: - "The role and its impact": description of role, impact. Could be "About the role" or "Role overview". Use

About the role

then

with description. - "The Team And How They Connect": description of team. Could be "Team" or "About the team". Use

Team

maybe. - "Where And How You Can Work": location, flexible hybrid. Could be "Work Arrangement" or "Location". Use

Location & Work Arrangement

maybe but we need to stick to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot invent other headings. So we must map content to these allowed headings only. If content doesn't fit, we may need to omit? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning these are examples, but we should use those headings when appropriate. It says "include a section ONLY when the posting has real, specific content for it". So we can use those headings if content matches. If not, we could maybe not use a heading? But we need to output HTML fragment; we could still use

with appropriate heading like "About the role", "Team" is not in list; maybe we could put team info under "About the role" or "Responsibilities"? Better to stick to allowed headings. Let's see what content fits: - About the role: we have description of role and impact. Good. - Responsibilities: we have bullet points of what you will do: design and optimise onboarding journeys, own acquisition and onboarding performance funnel, map touchpoints, use research, behavioural data, funnel analytics, design experiments, turn results into roadmap, bring teams along, scale what works, set vision, build tracking, campaign brief, playbook. That's responsibilities. - Requirements / Qualifications / Skills: The posting lists "Here are some of the things we're looking for, for this role" with bullet points: solid grounding in B2B marketing or customer journey strategy, ideally SaaS/fintech, commercial results; experimentation; data-driven decision making; influencing without formal authority; comfort with ambiguity; curiosity about accountants/bookkeepers. These could be Requirements or Qualifications or Skills. We can split: Requirements (experience), Qualifications (maybe same), Skills (specific). But we need to avoid thin sections. Could combine into one "Requirements" section with list. - Benefits: The posting has "Compensation & Total Rewards" with base salary range, variable pay, benefits list. So we can have Benefits section (list of benefits) and Pay section (salary range and variable pay). Schedule: Not mentioned explicitly; maybe flexible hybrid but not schedule. Could omit Schedule if no specific content. - Location: Not in allowed headings; maybe we could put location under "About the role" or "Responsibilities"? But we have "Where And How You Can Work" content: based in Bay Area office, flexible hybrid, boost days, etc. This could be placed under "About the role" or maybe under "Benefits"? Not ideal. Could we create a "Schedule" section? Not exactly schedule. Could we treat location as part of "About the role"? Might be okay to include location details in About the role paragraph. We must not invent headings not in list. So we will not create a heading for location. We'll embed location details in About the role or maybe in a

after About the role. We must not include boilerplate like EEO, etc. The posting includes some lines about AI screening, etc. That's boilerplate; we should remove. We must preserve all substantive information. Let's extract substantive content: About the role & impact paragraph: "The role and its impact As our Senior AB Journey Manager for Onboarding, you will design and optimise the onboarding journeys that accountants and bookkeepers move through when they first partner with Xero. Your work will shorten the time it takes a new partner to get real value from Xero, lift activation rates, and build the foundation for long term revenue growth across one of our most important channels. You will own the acquisition and onboarding performance funnel, mapping how product, digital, AI and human led touchpoints connect for each entry point and partner segment, then using research, behavioural data and funnel analytics to find the friction worth removing and the moments worth improving. From there, you will Go Bold by designing and running experiments that test new onboarding models, offers, messaging and channel mixes, using propensity scoring and AI powered personalisation to reach the right partner with the right action at the right moment. You will turn results into a prioritised roadmap, bring Product, Marketing, Sales and Customer Success along with you, and Go Further by scaling what works into globally aligned playbooks that regional teams can tailor to their own partners. This role sits where strategy meets execution, so you will be as comfortable setting a twelve month vision as you are building the tracking, the campaign brief or the playbook that makes it real." We can put that in

. Team section: "The Team And How They Connect You will join the Accountant and Bookkeeper Journeys team within Xero's Customer Growth and Engagement group, a small team of journey managers who each look after a stage of the partner lifecycle, from onboarding through to upsell and loyalty. The team is remote and async by design, with members across the United States, the United Kingdom, Australia and New Zealand, and a manager based in the UK. You will work as a peer to the other senior journey managers, sharing what you learn as you go, and partnering closely with regional go to market teams so journey work connects to the partner cohorts that matter most. The team is currently working on ➔ Building the personalised onboarding journey strategy for the second half of FY27 across three to four priority accountant and bookkeeper segments ➔ Running a cross channel experimentation roadmap that tests digital only against sales led activation models, and the blends in between ➔ Putting partner propensity scoring, behavioural signals and AI driven personalisation to work so outreach lands at the right moment rather than in bulk ➔ Next up, designing post activation workflows and an attribution framework that links journey work directly to revenue, partner growth and early engagement" We could put under "About the role" as well, but maybe better as separate "Team" heading not allowed. Could we put under "Responsibilities"? Not exactly. Could we put under "About the role" as part of role description? Might be okay to include team info in About the role paragraph. But we have a lot of content; maybe we can create a section "Team" but not allowed. 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 says use those for section headings. It might be okay to use other headings if needed, but they gave examples. Safer to stick to those. However, we need to include team info somewhere. Could we incorporate team info into "About the role" paragraph? That would be lengthy but acceptable. Where and how you can work: "Where And How You Can Work This role is based in our Bay Area office in San Mateo, and we offer a flexible, hybrid set up so you can work from a mix of home and the office. We come together on designated boost days for the planning, problem solving and connection that is simply better in person, and our office spaces are built for collaboration with quieter corners for focused work. Because your team spans the UK, Australia and New Zealand, some flexibility in your hours will help, and in return we care about outcomes rather than where you sit." We could embed this in About the role or maybe under "Benefits"? Not benefits. Could be under "Schedule"? Not exactly schedule but could mention flexible hours. However schedule section is for work schedule details; we could put flexible hybrid info there. The instruction says include Schedule section only if posting actually states them. It does mention flexible hybrid, boost days, flexibility in hours. That's schedule-related. So we can create a

Schedule

with that content. Compensation & Total Rewards: We need Pay section (base salary range, variable pay) and Benefits section (list of benefits). Let's extract: Pay: "The Expected Base Salary Range For This Role Is $162,400 - $243,600 USD Individual pay is determined by various factors, including geography, level of experience, and the specific skills you bring to the role. In addition to base pay, Xero’s roles are eligible for the following forms of variable compensation: Variable Pay: Permanent employees are eligible to participate in our annual bonus and equity (RSU) programs. You may also be eligible for performance-based cash or equity (RSUs) incentives depending on your role level, and company performance." Benefits: "Comprehensive Benefits: Medical, dental, vision, 401(k) match, and 21 days PTO, 10 days of Wellbeing leave, 5 days of Xtra Leave, 1 volunteer day, 12 paid holidays, paid parental leave. Further information included on our Xero Perks page." We should output Benefits as

• items. Now Requirements/Qualifications/Skills: "Here are some of the things we're looking for, for this role ➔ You will bring solid grounding in B2B marketing or customer journey strategy, ideally gained in a SaaS or fintech business, with commercial results you can point to ➔ Experimentation is where you do your best work, from designing a clean A/B test to reading the results honestly and deciding what deserves to scale ➔ Data is how you make decisions, whether that is funnel analytics, behavioural signals, customer segmentation or propensity models ➔ You Go Together by influencing Product, Marketing, Sales and Customer Success as a genuine partner, without relying on formal authority ➔ Ambiguity does not slow you down, and you Go Fast by shipping, learning and refining rather than waiting for a perfect plan ➔ Curiosity about accountants and bookkeepers sits behind your work, because the nuance between segments is where good journey design comes from Apply even if your experience isn't a perfect match! At Xero, we hire based on your skills, passion, and the unique perspective you can bring to enhance our culture and team." We can put these under

  Requirements

  as a list. We could also split into Qualifications and Skills but not needed; we can keep one Requirements section. Now we need to ensure we don't repeat job title as heading. We won't. We need to output only HTML fragment, no /, no markdown. Let's structure:

  About the role

  ... (including role impact, team, location maybe)

  But we have a lot of content; maybe we split into multiple paragraphs. We need to preserve all substantive information. Let's craft About the role paragraph covering role impact, team, location, work arrangement. We'll combine: Paragraph 1: Role impact description. Paragraph 2: Team description. Paragraph 3: Where and how you can work (location, flexible hybrid, boost days, flexibility). That's three

  under same heading? Usually you can have multiple

  under heading. Now Responsibilities: we need to list duties. Use

  • . Responsibilities bullet points from earlier: design and optimise onboarding journeys, own acquisition and onboarding performance funnel, mapping touchpoints, using research, behavioural data, funnel analytics to find friction and