Director of Product Counsel
Atlassian · San Francisco, CA · 1 mo ago
RemoteRemoteMarketing$230k–$300k/yrFull-time
We need to output only HTML fragment, no markdown fences. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content.
We have content: Overview (maybe "About the role"?). The posting includes "Overview Working at Atlassian ..." which is about work location flexibility, hiring anywhere, etc. That could be "About the role" or maybe "Overview". But we must use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have responsibilities: bullet list under "What You'll Do". Also "Your future team" paragraph.
We have background/requirements: "Your background" includes required experience, JD, license, etc. That's qualifications/requirements.
We have "Compensation" with pay ranges per zone. That's Pay section.
We have "Benefits & Perks" section: description of benefits, link.
We have "About Atlassian" maybe not needed as heading? Could be "About the role"? Actually "About Atlassian" is company overview, not role. Could be omitted or put under "About the role"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings.
We have no explicit Skills section separate from qualifications; but we could include skills under Qualifications or Skills. Probably better to have Qualifications and Skills separate if content fits. The posting mentions "Strong generalist product counseling skillset", "simplifier skillset", "strong writing skills", "comfort using technology", "enthusiasm for building processes". Those could be Skills.
We have no explicit Schedule info (remote/hybrid). The overview mentions flexible work location: "Atlassians can choose where they work – whether in an office, from home, or a combination of the two." That's schedule/location flexibility. Could be Schedule section.
We have no explicit Requirements separate from Qualifications; but we could treat Requirements as the mandatory items (8+ years experience, JD, license, background). Qualifications could be preferred/bonus items (familiar with Atlassian tools). However the instruction: prefer few substantive sections over many thin ones. Might combine Requirements and Qualifications into one? But headings are separate; we can include both if they have content.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, legal, etc. Remove duplicated lines, application instructions. The posting includes EEO statement at end; we should remove that. Also remove "All your information will be kept confidential according to EEO guidelines." etc. Also remove "In line with local law, identity verification..." etc. Also remove "To provide you the best experience..." etc. Also remove "To learn more about our culture and hiring process..." etc. Also remove "Please visit go.atlassian.com/payzones..." maybe keep as part of Pay? It's about pay zones; we can keep that as part of Pay section but not as separate heading.
We need to preserve all substantive information. So we need to keep the description of flexible work, responsibilities, background, compensation ranges, benefits perks, about Atlassian maybe? The "About Atlassian" is substantive but not role-specific; but we could include under "About the role"? Actually "About the role" could contain overview of role and work environment. The "About Atlassian" is company description; maybe we can include under "About the role" as part of role context? Or we could omit because not required? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the Atlassian description. Where to put? Could be under "About the role" as a paragraph about the company. Or we could create a separate heading like "About Atlassian" but not in allowed list. Since only allowed headings are those, we should fit it into one of them. Probably "About the role" is appropriate to include both role overview and company info.
Thus sections:
- About the role: includes overview of flexible work, Atlassian description, maybe "Your future team" paragraph? Actually "Your future team" is part of responsibilities? It describes team. Could go under Responsibilities or About the role. I'd put under About the role as context.
- Responsibilities: list of duties from "What You'll Do" bullet points.
- Requirements: mandatory items: 8+ years experience, JD, license, background in law firm and in-house, strong generalist product counseling skillset, ability to quickly understand unfamiliar product surfaces, comfort navigating ambiguity, demonstrated agility to dive into complex technical architectures, simplify skillset, strong writing skills, comfort using technology, energized by fast-paced agile environment, enthusiasm for building processes from scratch, natural fluency working asynchronously and collaborating through modern team tooling. Also maybe "Bonus for candidates who are familiar with Atlassian tools." That's a bonus, could be Qualifications.
- Qualifications: maybe "Bonus for candidates who are familiar with Atlassian tools." Also maybe "Preferred: experience in B2B Enterprise SaaS". Actually that is in requirements. Could treat that as part of Requirements. Qualifications could be empty? Better to combine Requirements and Qualifications into one section? But we need to follow headings; we can have both if they have content. Qualifications could contain the bonus and maybe "Preferred: experience in B2B Enterprise SaaS". But that is already in requirements. Might be redundant.
Given instruction: prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section called "Requirements". But we need to use headings exactly as given? It says use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content.
We have content: Overview (maybe "About the role"?). The posting includes "Overview Working at Atlassian ..." which is about work location flexibility, hiring anywhere, etc. That could be "About the role" or maybe "Overview". But we must use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have responsibilities: bullet list under "What You'll Do". Also "Your future team" paragraph.
We have background/requirements: "Your background" includes required experience, JD, license, etc. That's qualifications/requirements.
We have "Compensation" with pay ranges per zone. That's Pay section.
We have "Benefits & Perks" section: description of benefits, link.
We have "About Atlassian" maybe not needed as heading? Could be "About the role"? Actually "About Atlassian" is company overview, not role. Could be omitted or put under "About the role"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings.
We have no explicit Skills section separate from qualifications; but we could include skills under Qualifications or Skills. Probably better to have Qualifications and Skills separate if content fits. The posting mentions "Strong generalist product counseling skillset", "simplifier skillset", "strong writing skills", "comfort using technology", "enthusiasm for building processes". Those could be Skills.
We have no explicit Schedule info (remote/hybrid). The overview mentions flexible work location: "Atlassians can choose where they work – whether in an office, from home, or a combination of the two." That's schedule/location flexibility. Could be Schedule section.
We have no explicit Requirements separate from Qualifications; but we could treat Requirements as the mandatory items (8+ years experience, JD, license, background). Qualifications could be preferred/bonus items (familiar with Atlassian tools). However the instruction: prefer few substantive sections over many thin ones. Might combine Requirements and Qualifications into one? But headings are separate; we can include both if they have content.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, legal, etc. Remove duplicated lines, application instructions. The posting includes EEO statement at end; we should remove that. Also remove "All your information will be kept confidential according to EEO guidelines." etc. Also remove "In line with local law, identity verification..." etc. Also remove "To provide you the best experience..." etc. Also remove "To learn more about our culture and hiring process..." etc. Also remove "Please visit go.atlassian.com/payzones..." maybe keep as part of Pay? It's about pay zones; we can keep that as part of Pay section but not as separate heading.
We need to preserve all substantive information. So we need to keep the description of flexible work, responsibilities, background, compensation ranges, benefits perks, about Atlassian maybe? The "About Atlassian" is substantive but not role-specific; but we could include under "About the role"? Actually "About the role" could contain overview of role and work environment. The "About Atlassian" is company description; maybe we can include under "About the role" as part of role context? Or we could omit because not required? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the Atlassian description. Where to put? Could be under "About the role" as a paragraph about the company. Or we could create a separate heading like "About Atlassian" but not in allowed list. Since only allowed headings are those, we should fit it into one of them. Probably "About the role" is appropriate to include both role overview and company info.
Thus sections:
- About the role: includes overview of flexible work, Atlassian description, maybe "Your future team" paragraph? Actually "Your future team" is part of responsibilities? It describes team. Could go under Responsibilities or About the role. I'd put under About the role as context.
- Responsibilities: list of duties from "What You'll Do" bullet points.
- Requirements: mandatory items: 8+ years experience, JD, license, background in law firm and in-house, strong generalist product counseling skillset, ability to quickly understand unfamiliar product surfaces, comfort navigating ambiguity, demonstrated agility to dive into complex technical architectures, simplify skillset, strong writing skills, comfort using technology, energized by fast-paced agile environment, enthusiasm for building processes from scratch, natural fluency working asynchronously and collaborating through modern team tooling. Also maybe "Bonus for candidates who are familiar with Atlassian tools." That's a bonus, could be Qualifications.
- Qualifications: maybe "Bonus for candidates who are familiar with Atlassian tools." Also maybe "Preferred: experience in B2B Enterprise SaaS". Actually that is in requirements. Could treat that as part of Requirements. Qualifications could be empty? Better to combine Requirements and Qualifications into one section? But we need to follow headings; we can have both if they have content. Qualifications could contain the bonus and maybe "Preferred: experience in B2B Enterprise SaaS". But that is already in requirements. Might be redundant.
Given instruction: prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section called "Requirements". But we need to use headings exactly as given? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; we can choose which to include. So we could include only About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's fewer sections. Skills could be omitted if covered in Requirements. Qualifications omitted.
Thus sections:
- About the role: includes overview of flexible work, Atlassian description, maybe "Your future team" paragraph.
- Responsibilities: bullet list of duties.
- Requirements: includes experience, JD, license, background, skillset, ability to navigate ambiguity, agility, simplifier skillset, writing skills, tech comfort, fast-paced enthusiasm, building processes, async collaboration, bonus for Atlassian tools familiarity (maybe as preferred). Also mention B2B Enterprise SaaS experience.
- Benefits: description of perks and benefits, link.
- Pay: pay ranges per zone, plus note about geographic pay zones and link.
- Schedule: mention flexible work location (office, home, hybrid) and ability to choose.
We must not include filler like "commensurate with experience". Not present.
Now produce HTML fragment.
Structure:
About the role
About the role
... paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
...
Pay
...
Schedule
...
Make sure to preserve all substantive info. Let's extract details. Overview paragraph: "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." Also "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 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 need to remove EEO boilerplate and accommodation line? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO statement, accommodation line, identity verification line? Those are legal/EEO. So we should strip those. Keep the motivational statement about unleashing potential, etc. That's not EEO. So we keep: "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." We can also keep the sentence about hiring anywhere? Already in overview. Thus About the role paragraph(s) combine overview and Atlassian mission. Now Responsibilities: bullet points from "What You'll Do": - 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. Also there is a paragraph "Your future team 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 could be part of About the role or Responsibilities. I'd put in About the role as it describes team and role expectations. Now Requirements: list from "Your background": - 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