Legal Director, Contracts

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: 1. Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for lists,

  for prose 3. Do NOT repeat the job title as a heading 4. Do NOT put Job ID/requisition numbers as headings 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Looking at the job posting, I see it's duplicated multiple times. I need to extract the unique content. The posting has: - Company description (Carta) - Team description (Carta Law Contracts team) - Problems You'll Solve (with subsections: Oversight & Quality, Finance, Growth, Tech & Product, Client Relations, HR & People) - About You (qualifications) - Salary information (with specific ranges for different locations) - Some boilerplate at the end (EEO, E-Verify, privacy, etc.) I should structure this into sections: 1. About the Company (or About the Role) - but the rule says "About the role" as a heading example. The company description is more about the company. I'll use "About the Company" or "About the Role"? The rule says "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I think "About the Company" is appropriate for the company description. But the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. I'll use "About the Company" for the company description. 2. The Team You'll Work With - could be a section. 3. The Problems You'll Solve - this is essentially responsibilities. Could be "Responsibilities" or "The Problems You'll Solve". I'll use "Responsibilities" as it's a standard heading. 4. About You - this is qualifications/requirements. Could be "Qualifications" or "Requirements". I'll use "Qualifications". 5. Salary - this is Pay. The posting has specific salary ranges. So I'll include a "Pay" section. 6. Benefits - the posting mentions "Exceptional Benefits" but doesn't detail them. It says "Carta’s Compensation Package Includes a Market Competitive Salary, Equity For All Full Time Roles, Exceptional Benefits, And, For Applicable Roles, Commissions Plans." But no details. The rule says never create Benefits sections unless the posting actually states them. It states "Exceptional Benefits" but no details. I think I should not create a Benefits section because there's no substantive content. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states "Exceptional Benefits" but that's not specific. I'll omit Benefits. 7. Schedule - not mentioned. 8. There's also "At Carta, you're not just an employee..." which is culture/values. Could be a section "Culture & Values" or similar. But the rule says prefer a few substantive sections. I'll include it as part of "About the Company" or a separate "Culture" section. I'll include it as a separate section "Culture & Values" because it's substantive. Now, I need to remove duplicates. The posting is repeated three times. I'll take the unique content. Let me parse the unique content: Company description: "Carta is the connected platform and AI-native ecosystem for private capital. Built to replace fragmented tools with a single system of record, Carta brings together the software, services, and legal infrastructure that founders use to manage equity, fund managers use to run administration and reporting, and legal teams use to close transactions. Trusted by 55,000 companies and 1.8M+ equity holders in 160+ countries, and 10,000 funds and SPVs representing $250B+ in assets under management, Carta is transforming how private capital operates. Recognized by Fortune, Forbes, Fast Company, Inc. and Great Places to Work. For more information about our offices and culture, check out our Carta careers page." Team description: "You’ll be joining our Carta Law Contracts team – specifically within the Contracts – North Americas function. Our Contracts team manages the full lifecycle of commercial contracts for clients – from first review through to execution. You'll be the direct day-to-day contact for sophisticated investment fund and asset manager clients, working alongside fellow lawyers and paralegals. This team delivers high volumes of pre-M&A contract work at speed, supported by AI-backed tools. As Legal Director, you’ll lead a group of client accounts and the lawyers who serve them, report to the Regional Managing Director, and be accountable for the quality, speed and growth of that portfolio." Problems You'll Solve (Responsibilities): - Oversight & Quality: Supervise all client accounts in your group for quality, service levels and performance, rather than hands-on delivery; Act as final decision-maker on complex escalations or performance issues beyond Managing Lawyer (ML) authority; Drive holistic playbook reviews across the team; Own client onboarding and conversion; liaise with Customer Success (CS) to identify blockers; Uphold the culture and vision set by Carta Law and keep the team aligned; Manage lawyer and client allocation across accounts, with Managing Director oversight - Finance: Ensure billing information in the Carta Law app is accurate; Provide delivery inputs into forecasting models, such as productivity assumptions; Keep team productivity aligned with agreed forecast assumptions; Manage revenue for your accounts: convert demand to output, flag demand slowdowns or spikes to Customer Success, and approve one-off discounts and special pricing - Growth: Participate in sales pitches; Surface frontline client insights to guide sales targeting and priorities - Tech & Product: Identify opportunities for tech enablement and automation across the team; Contribute delivery insights to tech R&D workshops; Drive adoption of new tech, ensure training is completed, and guide how the team approaches tasks - Client Relations: Own client onboarding and conversion for clients; Liaise with and delegate responsibility to Managing Lawyers as appropriate; Be responsible for the health of the clients assigned to you - HR & People: Manage and coach lawyers: performance reviews, development plans, expense approval and annual leave; Provide input to the Training team on onboarding and ongoing training topics; Support training on playbooks and client standards; Manage resourcing and hiring demand for lawyer roles; conduct end-of-probation reviews; Lead interviews for lawyer-level hires; Handle internal escalations on lawyer conduct and performance; Monitor team utilisation, wellbeing and morale About You (Qualifications): - Qualified attorney in a relevant jurisdiction, 5+PQE - Based in one of our Canadian or US offices: Being in one of our offices allows the Legal Director to coach the team and shape its culture in person - it also enables face-to-face client meetings, pitches and escalations, deepening relationships and supporting retention - Contracts Expertise & Knowledge: Deep knowledge of commercial contracts across all contracts documents product types offered - People Management & Coaching: Strong coaching instinct; ability to develop lawyers, balance performance across multiple teams, and build team capability - Commercial Awareness: Financial literacy to interpret P&L drivers, optimise efficiency, and flag commercial risks upward - Client & Escalation Management: Confidence to own and resolve complex client escalations independently - Analytical & Critical Thinking: Ability to dissect complex requests, interrogate data on team performance, and draw sound conclusions under ambiguity - Operational Leadership: Process discipline to hold teams accountable to quality, SLAs and output standards - Problem Solving: Works on issues requiring deep knowledge of organizational objectives; establishes and assures adherence to budgets, schedules and performance expectations - Leading by Example: Demonstrates Carta operating values through consistent kindness, respect, and inclusive leadership Culture/Values: "At Carta, you’re not just an employee. You’re a builder who is creating infrastructure that accelerates innovation and empowers more ownership. Cartans are helpful, relentless, unconventional and kind; representing Carta’s Identity Traits. They work collaboratively and cross functionally to challenge the status quo; working towards a common goal of creating more owners in the private markets." Salary: "Carta’s Compensation Package Includes a Market Competitive Salary, Equity For All Full Time Roles, Exceptional Benefits, And, For Applicable Roles, Commissions Plans. Our Minimum Cash Compensation (salary + Commission If Applicable) Range For This Role Is: $171,300 - $214,200 in Hamilton Township, NJ and Denver, CO; $191,500 - $239,400 in Seattle, WA; $161,300 - $201,600 in Sandy, UT. Final offers may vary from the amount listed based on geography, candidate experience and expertise, and other factors." Boilerplate at end: EEO, E-Verify, privacy, etc. - remove. Now, I need to output HTML fragment with sections. I'll structure as:

  About the Company

  ...

  The Team You'll Work With

  ...

  Responsibilities

  • Oversight & Quality: ...
  ... but better to have subheadings? The rule says use

  for section headings. For subsections within responsibilities, I could use

  but the rule only mentions

  . However, the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other heading levels. But to keep it simple, I'll use

  for main sections and within Responsibilities, I'll use a list with bold labels. Alternatively, I could make each responsibility area a separate

  ? That would be many sections. The rule says "Prefer a few substantive sections over many thin ones." So I'll keep Responsibilities as one section with a list of items, each item being a responsibility area with its bullets. But the responsibility areas have multiple bullet points. I could do nested lists. However, the rule says "Use

  • for any list of duties/requirements/benefits". So I can have a top-level list for each responsibility area, and within each, a nested list for the specific duties. But HTML nested lists are okay. I'll do:

    Responsibilities

    • Oversight & Quality
      • Supervise all client accounts in your group for quality, service levels and performance, rather than hands-on delivery
      • Act as final decision-maker on complex escalations or performance issues beyond Managing Lawyer (ML) authority
      ...
    ...
    That's acceptable. Similarly for Qualifications. For Pay, I'll include the salary ranges. Now, I need to ensure I don't include any boilerplate. The duplicated lines are removed. Let's write the HTML. Note: The job title "Legal Director, Contracts" appears multiple times but I should not repeat it as a heading. The page already shows it. I'll start with About the Company, then The Team, then Responsibilities, then Qualifications, then Culture & Values, then Pay. I'll omit Benefits and