Principal Machine Learning Systems Engineer

We need to output HTML fragment with sections: Overview? Actually Overview is not a heading per list: they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. We have sections: Overview (maybe not needed). Responsibilities, Qualifications, Compensation (Pay), Benefits & Perks, About Atlassian (maybe About the role? Actually About Atlassian is about company, not role. Could be omitted? They said include a section ONLY when posting has real specific content. About Atlassian is generic but still content. Might be considered "About the role"? Not exactly. Could we include "About Atlassian" as a section? The allowed headings list includes "About the role". Not "About Atlassian". But we could treat it as "About the role"? Might be better to omit because it's not role-specific. However they said "Prefer a few substantive sections over many thin ones." The About Atlassian is generic boilerplate but still content. Might be considered boilerplate? It's not EEO etc. It's about company mission. Might be okay to include as a section with heading maybe "About Atlassian"? Not in allowed list but they gave examples, not exhaustive? They said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect those headings. Probably we should stick to those. So we will have sections: Responsibilities, Qualifications, Pay, Benefits. Possibly also "Overview"? Not in list. Could treat overview as part of responsibilities? But we have an "Overview Working at Atlassian" paragraph about flexible work etc. That could be considered "About the role"? Not exactly. Might be better to include as a

before sections? The instruction: Output ONLY the HTML fragment. No requirement to have a heading for overview. We can just include a

for that overview text before sections. We must not repeat job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The text includes EEO statement at end: "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." That's EEO boilerplate; should be removed. Also "About Atlassian" paragraph includes mission statement etc. That's not EEO; it's about company. Might keep? It's not in allowed headings but could be a

before sections. We need to preserve all substantive information. So we need to keep the overview paragraph about flexible work, hiring anywhere, etc. Keep responsibilities bullet points, qualifications bullet points, compensation details (pay zones), benefits description. We must not create sections with filler like "commensurate with experience". Not present. We need to use

• for any list of duties/requirements/benefits. So responsibilities list, qualifications list, benefits list (though benefits is prose but we can make list if they list items). The benefits 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 ." That's not a list; we can keep as

  . We need to include Pay section with the pay zones details. Use

  Pay

  then maybe a

  describing zones and ranges. Could also make a

  but not required. We need Benefits section:

  Benefits

  then

  . We need Qualifications section:

  Qualifications

  then
  • ... etc. Responsibilities:

    Responsibilities

    then
    . We might also include "Overview" as a

    before sections. Check for duplicated lines: The text includes "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." That's fine. Now produce HTML fragment. We must not include or . Just the fragment. Let's craft:

    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.

    Responsibilities

    • As a Principal ML System Engineer in the Rovo & AI Engineering org, you will contribute to Atlassian’s biggest bet and fastest area of growth, Rovo Chat.
    • You will bring the latest bleeding edge innovations to the product and build agent harnesses that deliver a step function improvement in quality, reliability and latency.
    • You will have the opportunity to lead other engineers to drive involved projects from technical design to launch.
    • You will also collaborate with other teams and internal customers to set expectations, gather input and communicate results.
    • Your role is pivotal, stretching beyond these tasks, ensuring AI's transformative potential is realized across our offerings.

    Qualifications

    • On your first day, we’ll expect you to have 7+ years of experience as a software developer
    • Experience building customer facing Gen AI Applications at scale
    • Experience pushing the state of the art to achieve breakthrough quality and reliability
    • Deep understanding of Machine Learning projects lifecycle
    • Experience leading and supporting senior engineers and working cross functionally
    • It would be great, but not required if you have Expertise in taking a platform approach to building product features, enabling multi team contributions
    • Experience with efficiently scaling and deploying Machine Learning models

    Pay

    At Atlassian, we strive to design equitable, explainable, and competitive compensation programs. To support this goal, the baseline of our range is higher than that of the typical market range, but in turn we expect to hire most candidates near this baseline. Base pay within the range is ultimately determined by a candidate's skills, expertise, or experience. 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: $236,700 - $309,025 Zone B: $213,000 - $278,123 Zone C: $196,400 - $256,491 This role may also be eligible for benefits, bonuses, commissions, and equity. 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.

    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 .

    We should also maybe include "About Atlassian" as a

    before sections? The overview already includes some. The "About Atlassian" paragraph after benefits is generic mission statement. Could be considered boilerplate? It's not EEO but still generic. Might be okay to include as a

    after benefits? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This is not those. So we could keep it. But they said prefer few substantive sections over many thin ones. Adding another paragraph may be okay. But we already have overview paragraph. The About Atlassian paragraph is similar to overview but more about mission. Could be considered redundant? Might be okay to keep. Let's include it as a

    after benefits. Thus final HTML:

    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.

    Responsibilities

    ...

    Qualifications

    ...

    Pay

    ...

    Benefits

    ...

    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 that the About Atlassian paragraph includes EEO statement again, which we were supposed to remove. Indeed the About Atlassian paragraph includes EEO lines: "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." That's EEO boilerplate; must be removed. So we need to strip that out. Keep only the earlier part: "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 Atl