Jobs · OTHR · New York

Vice President, Legal Operations

Annaly Capital Management · New York, NY · 4 wk ago
On-siteOTHR$160k–$250k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes "About Us" and "About This Role". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it). So we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we only include sections when posting has real specific content. We have content: About This Role (description). Could map to "About the role". Also "Key Responsibilities" -> Responsibilities. "Required Qualifications and Skills" -> could be Qualifications and Skills (maybe separate). The posting also has "Eligibility Requirements" (maybe Requirements). Also "Compensation and Benefits" -> Benefits and Pay. They gave salary range. So we can include Pay and Benefits sections. We must not include boilerplate like EEO etc. Remove that. We need to preserve all substantive info. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We need to decide structure: maybe sections: About the role, Responsibilities, Qualifications, Skills, Requirements (eligibility), Pay, Benefits. But we must not create thin sections. Let's see content. About the role: paragraph(s) from "About This Role". We'll put that. Responsibilities: list from "Key Responsibilities". There are bullet-like sentences separated by line breaks. We'll make

    • each. Qualifications: maybe "Required Qualifications and Skills" includes both qualifications and skills. Could split into Qualifications and Skills sections. But we can combine? The instruction says prefer few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one section titled "Qualifications and Skills". But they gave separate headings examples; we can still use one heading if content fits. However they said use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using combined heading, but examples show separate. Safer to follow examples: we could have Qualifications and Skills as separate headings if there is distinct content. The posting lumps them together: "Bachelor’s degree; relevant professional certification (e.g., CLOC) preferred" etc. That's qualifications. Then skills list: proficiency across legal technology landscape, etc. Could split. We also have Eligibility Requirements: location, work auth, background investigation, willingness to work extra hours. That's Requirements. Pay: salary range $160k-$250k/year, plus mention of sign-on bonus, RSU, discretionary awards. That's Pay. Benefits: robust health and wellness benefits, retirement savings, paid time off, tuition and learning reimbursement, backup childcare, paid parental leave, etc. That's Benefits. We need to omit EEO boilerplate. Let's extract content. About This Role paragraph: "The Vice President, Legal Operations will serve as the operational backbone of the Legal & Compliance Department, driving efficiency, cost discipline, and innovation across the function. This role is the bridge between legal strategy and business execution—owning the systems, processes, technology, and vendor relationships that enable lawyers to focus on high-value legal work. You will own efficiency, cost discipline, and innovation across the Legal & Compliance Department, and you will have real latitude to shape the strategy by which the ultimate goals are achieved. A core part of the job is championing artificial intelligence and other emerging technologies within the legal function, ensuring lawyers and staff are equipped to leverage these tools to enhance productivity, quality, and speed." We can keep as

      . Responsibilities bullet points: - Legal Operations Strategy & Continuous Improvement - Design and implement a scalable legal operations framework aligned with Annaly's business-first legal model - Translate Legal leadership priorities into practical processes, tools, and workflows that improve execution - Partner with Legal and Compliance professionals to codify playbooks, templates, and decision frameworks - Technology, AI & Process Optimization - Own the legal technology stack—evaluate, implement, optimize, and maintain platforms such as e-billing, matter management, contract lifecycle management (CLM) and knowledge management systems - Serve as the department's AI champion: identify, pilot, and deploy AI-powered tools (e.g., generative AI for drafting, contract review, legal research, document analysis, and presentations) to augment lawyer workflows and reduce manual effort - Develop training programs, prompt-engineering guides, and best-practice playbooks to help attorneys, legal staff, and governance professionals adopt AI tools effectively, responsibly, and in compliance with ethical and data-governance standards - Develop practical methods to measure and communicate the value delivered by AI tools and related process improvements - Outside Counsel Management & Cost Discipline - Design and oversee a comprehensive outside counsel management program, including panel selection, engagement guidelines, and performance tracking - Enhance billing discipline, alternative fee arrangements, and rate negotiations to optimize spend - Develop, manage, and report on the annual legal department budget, including spend forecasting and variance analysis We can flatten each bullet as

    • with the sub-bullets maybe as nested? But instruction: use
      • for any list of duties/requirements/benefits. Could have nested lists but okay. We'll just make top-level
      • each bullet point (including subpoints). Could also break into separate
      • for each subpoint. Simpler: each line starting with a dash is a
      • . We'll treat the headings like "Legal Operations Strategy & Continuous Improvement" as a
      • maybe bold? But we can keep as plain text. Qualifications: "Bachelor’s degree; relevant professional certification (e.g., CLOC) preferred" "At least 5 years of experience in legal operations, corporate governance support or a related operational role within a corporate legal department, corporate secretary's office, or law firm; we will also consider equivalent experience translating between business needs and technology in another function, such as consulting, product, or business operations" "Demonstrated experience building or scaling legal operations functions, including systems, workflows, and metrics" "Proficiency across the legal technology landscape, including hands-on experience implementing or managing several of the following: CLM, e-billing, matter management, and knowledge management systems, as well as hands-on experience with AI tools in a legal or professional services context (e.g., prompt engineering, workflow automation, responsible AI governance)" "Strong understanding of outside counsel management, legal spend optimization, and budgeting frameworks" "Analytical mindset with proficiency in data analysis, reporting, and dashboarding tools" "Strong project management skills with the ability to execute across multiple initiatives and departments simultaneously" "Excellent communication skills, and the ability to translate between stakeholders who might have different work styles, communication styles, and levels of technological expertise" "Self-motivated, proactive, intellectually curious, creative, and resourceful; takes initiative and ownership of responsibilities; enjoys helping others; embraces cross-functional, enterprise-wide goals" We could split into Qualifications (education, experience, demonstrated experience) and Skills (proficiency, understanding, analytical, project management, communication, personal traits). But we can combine. Requirements (Eligibility): "Based in New York, NY preferred; exceptional remote candidates authorized to work in the United States will be considered" "Must have unrestricted work authorization to work in the United States" "Must be willing to submit to a background investigation" "Must be willing to work additional hours as needed to complete deadline driven projects" Pay: "The salary range for this position at commencement of employment is expected to be between $160,000 and $250,000/year; however, base salary offered may vary depending on multiple individualized factors, including market location, job-related knowledge, skills, and experience." "The total compensation package for this position may also include other elements, such as a sign-on bonus, restricted stock units, and/or discretionary awards, in addition to robust health and wellness benefits, retirement savings, paid time off, tuition and learning reimbursement, back up childcare, paid parental leave and more." We need separate Pay and Benefits sections. Pay: salary range and variable factors, sign-on bonus, RSU, discretionary awards. Benefits: health and wellness, retirement savings, PTO, tuition reimbursement, backup childcare, paid parental leave, etc. We'll split: Pay section includes salary range, sign-on bonus, RSU, discretionary awards. Benefits section includes health and wellness benefits, retirement savings, paid time off, tuition and learning reimbursement, backup childcare, paid parental leave. We must not include "Additional details about total compensation and benefits will be provided during the hiring process." That's okay to keep? It's substantive but maybe generic. We can keep as part of Benefits or Pay? It's about details. We'll keep as a

        in Benefits maybe. Now produce HTML. Structure:

        About the role

        ...

        Responsibilities

        • Legal Operations Strategy & Continuous Improvement
          • Design and implement a scalable legal operations framework aligned with Annaly's business-first legal model
          • Translate Legal leadership priorities into practical processes, tools, and workflows that improve execution
          • Partner with Legal and Compliance professionals to codify playbooks, templates, and decision frameworks
        • Technology, AI & Process Optimization
          • Own the legal technology stack—evaluate, implement, optimize, and maintain platforms such as e-billing, matter management, contract lifecycle management (CLM) and knowledge management systems
          • Serve as the department's AI champion: identify, pilot, and deploy AI-powered tools (e.g., generative AI for drafting, contract review, legal research, document analysis, and presentations) to augment lawyer workflows and reduce manual effort
          • Develop training programs, prompt-engineering guides, and best-practice playbooks to help attorneys, legal staff, and governance professionals adopt AI tools effectively, responsibly, and in compliance with ethical and data-governance standards
          • Develop practical methods to measure and communicate the value delivered by AI tools and related process improvements
        • Outside Counsel Management & Cost Discipline
          • Design and oversee a comprehensive outside counsel management program, including panel selection, engagement guidelines, and performance tracking
          • Enhance billing discipline, alternative fee arrangements, and rate negotiations to optimize spend
          • Develop, manage, and report on the annual legal department budget, including spend forecasting and variance analysis
        But nested lists may be okay. However instruction: use
        • for any list of duties/requirements/benefits. Nested is still
          • . Acceptable. Alternatively flatten: each bullet as separate
          • . Might be simpler. I'll flatten: each line after dash becomes
          • . We'll ignore the headings like "Legal Operations Strategy & Continuous Improvement" as separate
          • maybe with strong? But we can keep as
          • with that heading. Let's produce flattened list:
          • Legal Operations Strategy & Continuous Improvement: Design and implement a scalable legal operations framework aligned with Annaly's business-first legal model
          • Legal Operations Strategy & Continuous Improvement: Translate Legal leadership priorities into practical processes, tools, and workflows that improve execution
          • Legal Operations Strategy & Continuous Improvement: Partner with Legal and Compliance professionals to codify playbooks, templates, and decision frameworks
          • Technology, AI & Process Optimization: Own the legal technology stack—evaluate, implement, optimize, and maintain platforms such as e-billing, matter management, contract lifecycle management (CLM) and knowledge management systems
          • Technology,

Similar jobs

Vice President, Legal

TRG ScreenNew York, NY· 2 wk ago
Legal$180k–$200k/yrapply on job-boards.eu.greenhouse.io