Corporate Counsel, Commercial & Employment

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting content: Company Overview, The Role, Key Responsibilities, Qualifications/Skills, Nice to Have, To Be a Strong Fit..., Why You'll Love Working With Us, etc. We need to extract substantive info. We should not repeat job title as heading. No Job ID. We need to include sections: About the role (maybe from "The Role" paragraph). Responsibilities (Key Responsibilities). Requirements (maybe from Qualifications/Skills). Qualifications (maybe separate? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills. Actually they list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which sections to include based on content. We have content about role description, responsibilities, qualifications/skills, nice to have, cultural fit, benefits (Why You'll Love Working With Us mentions competitive salary and benefits package, flexible working hours, dynamic work environment). No explicit pay amount or schedule details. So we should not include Pay or Schedule sections because no specific content. Benefits we have some: competitive salary and benefits package, flexible working hours, dynamic work environment. That's enough for Benefits. We also have "Why You'll Love Working With Us" which includes benefits. So we can put Benefits section. We need About the role: from "The Role" paragraph: description of Corporate Counsel, Commercial & Employment, key partner, drafting, negotiating, advising on commercial agreements, supporting employment-related matters, cross-functional. Responsibilities: list from Key Responsibilities bullet points. Requirements: maybe from Qualifications/Skills (mandatory). Qualifications: maybe separate? The instruction includes both Requirements and Qualifications headings. We need to decide what goes where. Usually Requirements are mandatory qualifications; Qualifications could be nice-to-have? But they have separate Nice to Have section in posting. We could map Requirements to the mandatory qualifications (J.D., 5+ years experience, etc.) and Qualifications to the Nice to Have? But they said "Qualifications" as a heading; we could put the Nice to Have there. However they also have "Skills" heading separate. Could put skills under Skills heading. We need to avoid filler. We'll produce sections:

About the role

...

Responsibilities

• ...
...

Requirements

• J.D. from an accredited law school and active membership in good standing with at least one U.S. state bar.
• Approximately 5+ years of relevant legal experience, ideally combining experience at a leading law firm and/or an in-house legal team at a high‑growth technology company.
• Significant experience drafting and negotiating sophisticated commercial agreements.
• Strong understanding of commercial contracting principles and the ability to independently manage agreements from initial review through execution.
• Experience advising on employment matters is strongly preferred.
• Excellent legal judgment with an ability to assess risk in the context of broader business objectives.
• Demonstrated ability to communicate complex legal concepts clearly and effectively to non‑legal stakeholders.
• Comfortable operating autonomously in a fast‑paced, high‑growth environment where priorities can evolve quickly.
• Strong cross‑functional partnership skills and a low‑ego, solutions‑oriented approach.
• Exceptional written and verbal communication skills.
• Ability to identify opportunities to improve processes and use technology, including AI‑enabled tools, to make legal work more efficient and scalable.

Qualifications

• Experience supporting a healthcare, health‑tech, technology, SaaS, or consumer business.
• Experience negotiating agreements involving enterprise customers, strategic partnerships, technology, data, or other complex commercial relationships.
• Exposure to privacy, product counseling, healthcare regulatory matters, or other issues relevant to a technology‑enabled healthcare business.
• Experience building contract templates, negotiation playbooks, approval frameworks, or other scalable legal processes.
• Day‑to‑day usage of a CLM to manage contract workflows, document management, and recordkeeping.
• Experience working closely with People teams on employment‑related matters.

Skills

Maybe we could list skills like legal judgment, communication, cross‑functional partnership, etc. But many already in Requirements. Could combine? However we need a Skills section only if there is specific content. We could extract skills from the posting: "Excellent legal judgment", "Ability to assess risk", "Communicate complex legal concepts", "Comfortable operating autonomously", "Strong cross‑functional partnership skills", "Exceptional written and verbal communication skills", "Ability to identify opportunities to improve processes and use technology". Those are more like skills. But they overlap with Requirements. Might be okay to put them under Skills. However we already used Requirements for mandatory qualifications; Skills could be the abilities. Let's do that. But we need to avoid duplication? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Duplication is okay if it's present in posting? The posting has those items under Qualifications/Skills. They are not duplicated elsewhere. So we can put them under Skills. Thus we need to split the Qualifications/Skills bullet list into Requirements (mandatory) and Skills (abilities). The posting lumps them together under "Qualifications/Skills". We need to decide which are requirements vs skills. The list includes: J.D., 5+ years experience, significant experience drafting..., strong understanding..., experience advising on employment matters..., excellent legal judgment..., ability to communicate..., comfortable operating autonomously..., strong cross‑functional partnership..., exceptional written and verbal..., ability to identify opportunities... Those could be considered requirements/skills. The "Nice to Have" list is separate. Thus we could treat the first block as Requirements (mandatory) and the second block as Skills (abilities). But the instruction says we have both Requirements and Qualifications headings. Could treat Requirements as the mandatory qualifications (J.D., experience, etc.) and Qualifications as the Nice to Have. Then Skills could be something else? But we already used Qualifications for Nice to Have. Then we still need Skills heading; we could put the abilities (legal judgment, communication, etc.) there. That would avoid duplication. Let's map: - About the role: from The Role paragraph. - Responsibilities: Key Responsibilities list. - Requirements: Mandatory qualifications (J.D., 5+ years, experience drafting..., strong understanding..., experience advising on employment matters...). Actually the list includes many items; we could treat all items under Qualifications/Skills as requirements, but we need to separate. Better: Requirements: J.D., 5+ years experience, significant experience drafting..., strong understanding..., experience advising on employment matters... (these are more like baseline). Skills: Excellent legal judgment, ability to assess risk, communicate complex concepts, comfortable operating autonomously, strong cross‑functional partnership, exceptional written/verbal communication, ability to identify opportunities to improve processes and use technology. Qualifications: Nice to Have list. Benefits: from Why You'll Love Working With Us: competitive salary and benefits package, flexible working hours, dynamic work environment where creativity and innovation are encouraged, mission-driven, diverse and inclusive workforce. We should not include Pay or Schedule. Now produce HTML. We need to ensure we don't include boilerplate like EEO, scam warning, etc. Remove those. Let's craft. About the role paragraph: Combine sentences: "Function is seeking a Corporate Counsel, Commercial & Employment to join our growing Legal team. This attorney will be a key partner to teams across the business, with primary responsibility for drafting, negotiating, and advising on a broad range of commercial agreements while also supporting employment-related legal matters as Function continues to scale. This is a highly cross-functional role for someone who combines strong legal judgment with a practical, business-oriented approach. You’ll work closely with stakeholders across Sales, Partnerships, Marketing, Product, People, Finance, and Operations, helping teams move quickly while thoughtfully managing legal and business risk." That's good. Responsibilities: list each bullet from Key Responsibilities. Let's extract them exactly: - Draft, review, and negotiate a broad range of commercial agreements, including customer, vendor, partnership, services, SaaS, technology, licensing, confidentiality, and other strategic agreements. - Serve as a trusted legal partner to business teams: providing practical, commercially minded counsel that balances business objectives with appropriate risk management. - Partner closely with stakeholders to help structure and negotiate complex commercial relationships and enable efficient deal execution. - Develop a strong understanding of Function's products, business model, and strategic priorities to provide proactive legal guidance as the company scales. - Support the People team on employment-related legal matters, including employee relations, policies, performance and separation matters, and other day-to-day employment questions, in partnership with internal and external resources as appropriate. - Identify emerging legal risks and translate complex legal issues into clear, actionable guidance for business stakeholders. - Help develop and improve contract templates, playbooks, policies, processes, and legal operations that allow the Legal team to scale effectively. - Partner cross-functionally with Product, Marketing, Finance, Operations, People, and other teams on legal issues that arise across the business. - Manage outside counsel strategically when specialized expertise is required. We'll put each as

. Requirements (mandatory): list: - J.D. from an accredited law school and active membership in good standing with at least one U.S. state bar. - Approximately 5+ years of relevant legal experience, ideally combining experience at a leading law firm and/or an in-house legal team at a high‑growth technology company. - Significant experience drafting and negotiating sophisticated commercial agreements. - Strong understanding of commercial contracting principles and the ability to independently manage agreements from initial review through execution. - Experience advising on employment matters is strongly preferred. We could also include "Experience advising on employment matters is strongly preferred" as requirement (though preferred). Keep. Skills: list: - Excellent legal judgment with an ability to assess risk in the context of broader business objectives. - Demonstrated ability to communicate complex legal concepts clearly and effectively to non-legal stakeholders. - Comfortable operating autonomously in a fast-paced, high-growth environment where priorities can evolve quickly. - Strong cross-functional partnership skills and a low-ego, solutions-oriented approach. - Exceptional written and verbal communication skills. - Ability to identify opportunities to improve processes and use technology, including AI-enabled tools, to make legal work more efficient and scalable. Qualifications (Nice to Have): list: - Experience supporting a healthcare, health‑tech, technology, SaaS, or consumer business. - Experience negotiating agreements involving enterprise customers, strategic partnerships, technology, data, or other complex commercial relationships. - Exposure to privacy, product counseling, healthcare regulatory matters, or other issues relevant to a technology‑enabled healthcare business. - Experience building contract templates, negotiation playbooks, approval frameworks, or other scalable legal processes. - Day‑to‑day usage of a CLM to manage contract workflows, document management, and recordkeeping. - Experience working closely with People teams on employment‑related matters. Benefits: from Why You'll Love Working With Us: "We value our team at Function and offer a competitive salary and benefits package, flexible working hours, and a dynamic work environment where creativity and innovation are encouraged." Also mention mission, diversity, etc. Could include: "competitive salary and benefits package, flexible working hours, dynamic work environment encouraging creativity and innovation, mission-driven culture, commitment to diversity and inclusion." We'll put as

• ... maybe combine into one

  or list. Better to use

  for prose. Benefits could be a

  summarizing. Let's do:

  Benefits

  We offer a competitive salary and benefits package, flexible working hours, and a dynamic work environment where creativity and innovation are encouraged