Senior Enterprise Delivery Manager, Migrations

We need to output HTML fragment with sections: Overview? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. We have content: Overview (Working at Atlassian) includes description of remote work, hiring anywhere, why apply, role description. That could be "About the role" or "Overview". Probably "About the role". Then "Responsibilities" list. Then "Compensation" includes Pay ranges. Then "Qualifications". Then "Benefits & Perks". Then "About Atlassian" maybe not needed? It's generic company description; could be omitted? It's not a required heading; but we could include as "About Atlassian" maybe not in list. The instruction says prefer few substantive sections over many thin ones. The About Atlassian is generic boilerplate; might be considered boilerplate? It's not EEO etc but still generic. Might be okay to include as "About Atlassian". However they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The About Atlassian paragraph is not EEO but still generic marketing. Might be okay to keep? The instruction: "Prefer a few substantive sections over many thin ones." Could combine Overview and About Atlassian into one "About the role" section? But we have separate sections: Overview (role description) and About Atlassian (company). Might be better to have "About the role" covering the overview and why apply, and maybe skip About Atlassian as it's not specific to role. However they said preserve ALL substantive information; do NOT invent or summarize away detail. The About Atlassian paragraph is substantive? It's generic but still part of posting. Might be considered boilerplate but not EEO. Safer to include as a section "About Atlassian". But the instruction list of headings does not include About Atlassian; but they gave examples, not exhaustive. Could use

for any section heading. So we can use "About Atlassian". Let's include. We need to use

• for any list of duties/requirements/benefits. So responsibilities list, qualifications list, benefits list. We need to use

  for prose. We need to include Pay section only if posting states them. It does: Pay Ranges with zones. So we need a Pay section with that info. Schedule: not mentioned, so omit. Benefits: we have Benefits & Perks section with description but not a list; we could still make a

  describing benefits. Could also list perks? Not given as list. So just

  . We need to preserve all substantive information: include the overview paragraphs, why apply, role description, responsibilities bullet points, qualifications bullet points, benefits description, pay ranges, about Atlassian paragraph. We need to remove duplicated lines, cookie/navigation/legal/EEO etc. The posting includes EEO statement at end: "All your information will be kept confidential according to EEO guidelines..." etc. That's boilerplate; remove. Also the line about identity verification etc maybe also boilerplate? It's about local law identity verification; could be considered legal; maybe remove. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove the EEO paragraph and the identity verification line. Also remove "To provide you the best experience..." accommodation line? That's also part of EEO? Might be considered accommodation statement; could be considered EEO-related; better remove. Also "To learn more about our culture and hiring process..." maybe keep? It's about culture; not EEO. Might be okay but could be considered generic. I'd keep it as part of About Atlassian? Actually it's separate after EEO. Might be considered boilerplate but not EEO. Safer to keep? The instruction: remove EEO/equal-opportunity/scam-warning boilerplate. That line is not EEO. It's about culture and hiring process. Could keep. But we also have "About Atlassian" section earlier that includes mission statement etc. That's fine. We need to ensure we don't include any filler like "commensurate with experience". Not present. Now craft HTML. Structure:

  About the role

  Overview paragraphs: Working at Atlassian... Why should you apply... The Senior Enterprise Delivery Manager is responsible...

  Then

  Responsibilities

  • ... each responsibility line.
  Then

  Qualifications

  • ... each qualification line.
  Then

  Benefits & Perks

  Atlassian offers a wide range of perks and benefits...

  Then

  Pay

  At Atlassian, we strive to design equitable... (compensation paragraph) plus the pay ranges table? We need to preserve the pay ranges. Could present as

  • Zone A: $156,600 - $204,450
  etc.
  Or as

  ... For this role, our current base pay ranges for new hires in each zone are: Zone A: $156,600 - $204,450; Zone B: $141,300 - $184,475; Zone C: $130,500 - $170,375.

  That's fine. Then

  About Atlassian

  At Atlassian, we're motivated by a common goal...

  plus maybe the culture/hiring process line. We need to ensure we didn't include any duplicated lines. Let's extract exact text. Overview section: "Overview Working at Atlassian Atlassians can choose where they work – whether in an office, from home, or a combination of the two. That way, Atlassians have more control over supporting their family, personal goals, and other priorities. We can hire people in any country where we have a legal entity. Why should you apply to this role? The Senior Enterprise Delivery Manager is responsible for ushering Atlassian’s largest, most complex customers through their transition into the cloud. As the primary stakeholder, you will act as a reliable strategic advisor and technical consultant to senior customer decision-makers, while also leading the delivery and governance of large-scale Cloud migrations. You bring both business acumen and technical fluency. You will work closely with customer stakeholders and cross-functional teams—including Sales, Solutions, Support, Product Management, Channel Partners, and Engineering—to help navigate architectural decisions, risk mitigation, performance guardrails, and adoption planning. This role is ideal for someone who thrives at the intersection of strategy, data, and execution — whether you come from delivery management, DevOps, QA/testing, or engineering. It requires proven expertise in developing and influencing customer cloud strategies and enabling technical adoption of cloud features, including AI. You understand how data moves, systems integrate, and migrations succeed (or fail). You will identify potential challenges and implement effective solutions that guide toward positive outcomes and ultimately lead Atlassian’s most strategic customers to Cloud." We need to split into sentences but keep as paragraph. Responsibilities list: "Migration Strategy: Lead end-to-end cloud transformation engagements by evaluating customer environments and aligning technical execution with business outcomes." "Risk Management: Facilitate migration readiness assessments, interpret guardrail results, and recommend actionable remediations (i.e. SQL-based analysis, app remediations, automation deltas, workflow redesign)." "Technical Architecture: Understand and communicate the role of APIs, webhooks, and automation components in customer environments — explaining how they translate to Cloud and what requires refactor or replacement." "Trusted Advisor: Act as a trusted advisor to senior leadership and other technical executives, guiding decision-making through data-backed insights." "Delivery Excellence: Govern the migration lifecycle through disciplined execution, measurable outcomes, and coordination with support & engineering teams — from discovery to UAT completion and go-live." "Drive Accountability: Drive team accountability through clearly defined milestones, transparent reporting, proactive risk management and optimal resourcing." "Stakeholder Management: Lead all project communications, plan reviews, and steering committee to guide project direction. Maintain effective communication with stakeholders to advocate for the team and meet customer objectives." "Escalation Management: Act as the escalation point for customers to drive urgency on critical blockers during migrations." "Team Leadership: Mentor peers on technical literacy and lead internal enablement efforts, including training workshops and playbook development. Model a consultative, data-driven mindset expected of Atlassian’s delivery leaders." "Industry Insight: Stay ahead of industry trends and integrate insights into customer interactions. Propose innovative solutions to business challenges." Qualifications list: "Extensive experience working in or around software delivery — roles such as Delivery Manager, DevOps Engineer, QA/Test Lead, Systems Engineer, or Support Lead are a plus" "Proven track record leading data migration, systems integrations, or platform transformations." "Knowledge of APIs, automations, and integration patterns, including how they translate between on-prem and cloud." "Strong understanding of the software development lifecycle (SDLC) — able to connect process, tooling, and delivery outcomes." "Strong ability to influence customer decision-making through expertise in delivery knowledge and value discussions." "Skilled in negotiating effectively with senior-level decision-makers and c-suite executives." "Demonstrated leadership, teamwork, and mentorship skills that enhance team learning and engagement." "Over 10 years of professional experience as a technical program/delivery manager responsible for complex technology projects for enterprise customers." "Bachelor’s or advanced degree in engineering, computer science, or equivalent professional experience." Benefits & Perks paragraph: "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 ." Pay paragraph: "At Atlassian, we strive to design equitable, explainable, and competitive compensation programs. We follow consistent hiring practices and account for each candidate's skills, knowledge, and experience when setting base pay within the range. 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. This role may also be eligible for benefits, bonuses, commissions, and equity." Then pay ranges: "Role 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: $156,600 - $204,450 Zone B: $141,300 - $184,475 Zone C: $130,500 - $170,375" Note there is a stray "Role" at start; maybe it's "Role In The United States". We'll keep as is. About Atlassian paragraph: "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