Director of Product Counsel

We need to output HTML fragment with sections only when there is real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to parse the posting. We have sections: Overview (maybe not needed). "Working at Atlassian" is about work location flexibility, hiring anywhere. Could be part of "About the role"? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings if present. We have: - Overview: includes "Working at Atlassian" (flexible work, hiring anywhere). Could be "About the role"? Actually "About the role" would describe the role, team, mission. The posting includes "Your future team" and description of team, mission. That could be "About the role". Also "Overview Working at Atlassian" maybe part of "About the role" or separate? We'll treat as "About the role". - Responsibilities: clearly present with bullet list (Your future team, What You'll Do). We'll put under

Responsibilities

with

• items. - Requirements: The posting includes "Your background" with bullet points of experience, JD, license, etc. That's qualifications/requirements. Could be under

  Requirements

  or

  Qualifications

  . The instruction lists both Requirements and Qualifications as possible headings. We need to decide which to use. Usually Requirements = mandatory qualifications; Qualifications = preferred? But we can combine. The posting has "Your background" with required items: 8+ years experience, JD, license, background in law firm and in-house, strong generalist product counseling skillset, comfort navigating ambiguity, demonstrated agility, simplifier skillset, strong writing, comfort using tech, enthusiasm for building processes, bonus for familiarity with Atlassian tools. That seems like requirements. We'll put under

  Requirements

  . - Skills: maybe not separate; we could omit if not distinct. The posting mentions skills within background. We'll not create a Skills section unless there is explicit skills list separate. There's not. - Benefits: The posting includes "Benefits & Perks" section describing health and wellbeing resources, paid volunteer days, etc. So we should have

  Benefits

  with
  • items. - Pay: The posting includes "Compensation" with pay ranges per zone. So we need

    Pay

    with details. - Schedule: Not mentioned (no schedule info). So we omit Schedule. - Also there is "About Atlassian" and EEO etc. Those are boilerplate to remove. We should remove EEO/equal-opportunity/scams etc. Also remove navigation/cookie/legal boilerplate. The "About Atlassian" paragraph is generic company description; is that considered boilerplate? It's not EEO but it's about company mission. Might be considered part of "About the role"? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Atlassian" is not explicitly listed to remove, but it's generic company description; could be considered part of "About the role"? However we already have "About the role" covering role specifics. The generic Atlassian mission may be considered boilerplate? Not sure. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The Atlassian mission statement is substantive? It's generic but still about company. Might be okay to keep as part of "About the role" or separate section? There's no heading for "About the company". Since we only allowed headings list, we could put it under "About the role" as extra paragraph. Or we could omit if considered boilerplate. I'd keep it as part of "About the role" because it's about the company and role context. We also have "Compensation" section with pay ranges and note about geographic pay zones. We'll include that under Pay. We also have "Benefits & Perks" section. We also have "Overview Working at Atlassian" about flexible work; could be part of "About the role". We'll include. Now we need to output HTML fragment only, no /, no markdown fences. We'll structure:

    About the role

    ... paragraphs combining overview, working at Atlassian, future team description.

    Responsibilities

    • Navigate the Frontier: Counsel product and engineering teams on emerging, first-impression legal and regulatory issues, especially across AI/ML technologies, data governance, intellectual property, and platform architectures.
    • Flex Across Domains: Apply a versatile generalist approach to comfortably pivot across products, technical stacks, and subject areas as business priorities evolve.
    • Define the AI Era Playbook: Partner with cross-functional teams to design repeatable frameworks, launch checklists, and scalable legal guardrails that enable R&D teams to ship AI features with velocity and confidence.
    • Act as the Legal Hub: Serve as the primary legal partner and "front door" for product initiatives, collaborating closely with Legal SMEs (Privacy, IP, Commercial, Regulatory) to deliver cohesive, business-first guidance.
    • Shape Team Culture & Practice: Help mature our growing Product Counsel function by bringing fresh ideas, experimenting with new ways of working, and leveraging modern tech and async tools to scale our impact.

    Requirements

    • 8+ years of legal experience counseling software products, ideally in the B2B Enterprise SaaS space, with experience supporting fast-moving Product and Engineering teams.
    • Required Juris Doctor, with a license to practice law in your jurisdiction.
    • Background in a law firm and in-house legal team.
    • Strong generalist product counseling skillset, with the ability to quickly understand unfamiliar product surfaces, technical architectures, and business models.
    • Comfort navigating ambiguity and novel issues, including evaluating emerging AI, data, IP, regulatory, and platform questions where there may not be a clear playbook.
    • Demonstrated agility to dive into complex technical architectures, synthesize inputs from multiple legal disciplines, and adapt quickly to unfamiliar product surfaces.
    • You have a simplifier skillset (no legalese for our Product teams), strong writing skills to excel in our async environment, comfort using technology to get your work done (we love our own tools!), and you're energized by a fast-paced and agile working environment.
    • Enthusiasm for building processes and artifacts from scratch, with natural fluency working asynchronously and collaborating through modern team tooling.
    • Bonus for candidates who are familiar with Atlassian tools.

    Benefits

    • Health and wellbeing resources
    • Paid volunteer days
    • ... (the posting says "and so much more") but we should not invent. We'll keep the two explicit items and maybe a generic "and more" but that's vague. Better to list only what is explicitly stated: health and wellbeing resources, paid volunteer days. The phrase "and so much more" is vague; we could include as a bullet: "and other perks and benefits". But that's somewhat filler. I'd include just the two explicit items; the phrase "and so much more" is not specific. We'll omit that.

    Pay

    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.

    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: $229,500 - $299,625
    • Zone B: $206,550 - $269,663
    • Zone C: $190,485 - $248,689
    We should not include Schedule heading. Check for any duplicated lines: we have not. We must ensure we didn't include any boilerplate like EEO etc. We removed the "About Atlassian" paragraph and EEO lines. Did we inadvertently include any? We included "About the role" paragraph that includes overview and future team description. We need to verify that we didn't include any EEO lines. The original had: "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." We omitted all that. Good. Now check that we didn't miss any substantive content: The "Overview Working at Atlassian" about flexible work and hiring anywhere. Did we include that? We included in About the role paragraph? We haven't yet added that. Let's add a sentence: "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." We'll include that in About the role. Also "Your future team" description we included as part of About the role? We have not yet added that. We need to incorporate that. The "Your future team" paragraph: "We are building the future of teamwork at Atlassian, and our Product Counsel team is at the heart of that transformation. We operate as strategic partners and trusted advisors embedded directly alongside R&D and product leaders. As AI reshapes software and the way teams collaborate, we are redefining how Legal enables rapid, responsible product innovation. We are looking for a creative, adaptable Director of Product Counsel who thrives on novel questions, brings a strong generalist toolkit, and is energized by the opportunity to shape our team’s operating model and playbook for the AI era." That's substantive; we should include in About the role. Thus About the role will have multiple paragraphs: maybe combine into one

    with multiple sentences, or separate

    elements. The instruction: Use

    for prose. We can have multiple

    elements under the heading. We'll do:

    About the role

    Atlassians can choose where they work – whether in an office, from home, or a combination of the two. That way, Atlassians have more control