Senior Digital Success Manager

We need to output HTML fragment with sections: Overview (maybe not a heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The posting includes Overview, Responsibilities, Pay Ranges, Qualifications, Compensation (duplicate), Benefits & Perks, About Atlassian (maybe not needed). We should only include sections that have real specific content. Overview is a paragraph; we can put it as

maybe under no heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must have a heading for overview; we can just put

for overview. Then

Responsibilities

with

• items. Then

  Pay

  with the pay ranges. Then

  Qualifications

  with list. Then

  Benefits

  with description. Possibly also

  About the role

  but we have overview; maybe we treat overview as About the role. But instruction says use

  for section headings (e.g. About the role, Responsibilities...). So we could make Overview as About the role heading. However they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings. Overview is not job title. So we can use

  About the role

  for overview paragraph. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the Atlassian EEO statement, accommodation line, identity verification line, etc. Also duplicate compensation paragraph appears twice; we should keep only one instance. Also duplicate Pay Ranges appears twice; keep one. We need to keep the benefits description: "Atlassian offers a wide range of perks and benefits designed to support you, your family and to help you engage with your local community. Our offerings include health and wellbeing resources, paid volunteer days, and so much more. To learn more, visit go.atlassian.com/perksandbenefits ." That's substantive. We need to keep the "About Atlassian" paragraph? It's somewhat generic but maybe considered boilerplate? It's about mission, not specific to role. Might be considered boilerplate; but it's not EEO/legal. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Atlassian" is not explicitly listed; but it's generic company description. Might be considered boilerplate? Not sure. Safer to keep it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The About Atlassian paragraph is substantive about company mission. I'd keep it as a section maybe

  About Atlassian

  but they didn't list that as example heading; but we could still use

  About Atlassian

  . However they said use

  for section headings (e.g. About the role, Responsibilities...). The e.g. list is not exhaustive; we can add other headings as needed. So we can include About Atlassian. But we need to avoid filler like "commensurate with experience". Not present. Now structure:

  About the role

  Overview paragraph text.

  Responsibilities

  • ...
  ...

  Pay

  In the United States, we have three geographic pay zones. For this role, our current base pay ranges for new hires in each zone are: Zone A: $148,696 - $194,130; Zone B: $133,826 - $174,717; Zone C: $123,417 - $161,128.

  Maybe also include note about compensation eligibility: "This role may also be eligible for benefits, bonuses, commissions, and equity." That's substantive; we can include in Pay section or separate Compensation section. Since they said prefer few substantive sections over many thin ones, we could incorporate that note into Pay section.

  Qualifications

  • Experience in Digital/Adoption Marketing and/or Digital Customer Success
  • Proven track record of influencing cross-functional partners to improve customer outcomes and experiences
  • Strong prioritization skills, with the ability to manage multiple concurrent projects from inception to completion

  Benefits

  Atlassian offers a wide range of perks and benefits designed to support you, your family and to help you engage with your local community. Our offerings include health and wellbeing resources, paid volunteer days, and so much more. To learn more, visit go.atlassian.com/perksandbenefits.

  About Atlassian

  At Atlassian, we're motivated by a common goal: to unleash the potential of every team. Our software products help teams all over the planet and our solutions are designed for all types of work. Team collaboration through our tools makes what may be impossible alone, possible together. We believe that the unique contributions of all Atlassians create our success. To ensure that our products and culture continue to incorporate everyone's perspectives and experience, we never discriminate based on race, religion, national origin, gender identity or expression, sexual orientation, age, or marital, veteran, or disability status. All your information will be kept confidential according to EEO guidelines. To provide you the best experience, we can support with accommodations or adjustments at any stage of the recruitment process. Simply inform our Recruitment team during your conversation with them. To learn more about our culture and hiring process, visit go.atlassian.com/crh . In line with local law, identity verification (which may include use of biometric data) is a condition of employment with Atlassian for employment fraud purposes.

  But note: The About Atlassian paragraph includes EEO guidelines and accommodation statement, identity verification line. Those are boilerplate/legal. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The About Atlassian includes EEO guidelines and accommodation statement, identity verification. Those are likely to be removed. So we should strip those lines. Keep only the mission statement: "At Atlassian, we're motivated by a common goal: to unleash the potential of every team. Our software products help teams all over the planet and our solutions are designed for all types of work. Team collaboration through our tools makes what may be impossible alone, possible together. We believe that the unique contributions of all Atlassians create our success." That's the substantive part. The rest is boilerplate. So we should output only that. Thus About Atlassian section will contain just that mission paragraph. Now ensure we didn't include any duplicated content. Also we need to ensure we didn't include any application instructions (like "Please visit go.atlassian.com/payzones for more information...") That's part of compensation paragraph but it's not application instruction; it's informational about pay zones. Might be okay to keep? The instruction: remove duplicated lines, and application instructions. The pay zone link is not an application instruction; it's just reference. Could keep. However the compensation paragraph includes: "Please visit go.atlassian.com/payzones for more information on which locations are included in each of our geographic pay zones. However, please confirm the zone for your specific location with your recruiter." That's somewhat instructional but not exactly application instruction; it's about pay zones. Might be considered part of compensation details. I'd keep it. But we already have Pay section with ranges; we could incorporate that note there. Now produce HTML fragment. Let's craft:

  About the role

  The Digital and Agentic Success team is pivotal to Atlassian, tasked with ensuring the adoption and retention of our 300k global customer base. Our next opportunity lies in enhancing engagements through omni-channel alignment with personalized customer journeys at scale — regardless of segment. The foundational elements are in place; this role focuses on experimenting with co-ordinated plays, identifying effective strategies, and scaling them quickly. There's no named book of business but the expectation is to bring the same ownership and customer-first urgency to cross-functional programs that a CSM brings to individual accounts. A builder mentality is a must. You should be comfortable with ambiguity and bring structure, speed, and continuous improvement. Success is measured not only by the programs you launch today, but by the autonomous experiences you enable tomorrow.

  Responsibilities

  • Align message consistency and timing across email, in-app, community, learning, AI agents and human channels so each customer touchpoint reinforces the same core actions to maximize adoption
  • Partner with Product and Data Science/Analytics to identify product telemetry signals to underpin and measure programmatic outreach that can be executed by humans, automation or AI agents
  • Partner with Product, Marketing and Customer Success to identify proven use-case content to optimize for distribution across omni-channel plays
  • Unlock wall-to-wall expansion by championing product agnostic, team-persona targeting
  • Leverage tech and automation to build pathways for customers between digital/agentic and frontline teams
  • Lead change through cross-functional influence, data-backed hypothesis and experimentation
  • Nurture cross-functional relationships, establishing regular feedback rhythms to maximize impact
  • Proactively optimize ways of working, sharing craft expertise, demonstrating mentorship across the team
  • Frame work in terms of revenue and customer impact

  Pay

  In the United States, we have three geographic pay zones. For this role, our current base pay ranges for new hires in each zone are: Zone A: $148,696 - $194,130; Zone B: $133,826 - $174,717; Zone C: $123,417 - $161,128. This role may also be eligible for benefits, bonuses, commissions, and equity. For more information on which locations are included in each zone, visit go.atlassian.com/payzones; please confirm your zone with your recruiter.

  Qualifications

  • Experience in Digital/Adoption Marketing and/or Digital Customer Success
  • Proven track record of influencing cross-functional partners to improve customer outcomes and experiences
  • Strong prioritization skills, with the ability to manage multiple concurrent projects from inception to completion

  Benefits

  Atlassian offers a wide range of perks and benefits designed to support you, your family and to help you engage with your local community. Our offerings include health and wellbeing resources, paid volunteer days, and so much more. To learn more, visit go.atlassian.com/perksandbenefits.

  About Atlassian

  At Atlassian, we're motivated by a common goal: to unleash the potential of every team. Our software products help teams all over the planet and our solutions are designed for all types of work. Team collaboration through our tools makes what may be impossible alone, possible together. We believe that the unique contributions of all Atlassians create our success.

  Check for any leftover boilerplate