HR & Legal Technology Operations Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Company" and then description of role. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. The posting includes responsibilities (multiple bullet-like paragraphs). It includes requirements (list). It includes preferred qualifications (list). It includes benefits (some description). It includes pay: "The base salary range for this role is listed above." Actually they say "The base salary range for this role is listed above." No explicit range given. So we should not include Pay section because no specific numbers. Schedule: not mentioned. Skills: not explicit separate list; maybe we can combine under Requirements? But we need to follow rules: Use headings only when posting has real specific content. We have About the role? The posting includes description of role after company info. Could treat that as "About the role". We'll include that as a

maybe. The "About The Company" is not a role heading; but we could include as part of About the role? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have heading "About the role". Provide prose summarizing role description. We'll include that. Responsibilities: we have many paragraphs under "Responsibilities". We'll convert each bullet-like sentence into

inside

. We need to preserve all substantive information; not invent or summarize away detail. So we need to list each responsibility as separate
• . The responsibilities are grouped under headings: Technology Partnership & Functional Alignment, BambooHR Stabilization & Maturation (Near-Term Priority), Legal Technology & Operations Enablement, HR Platform Strategy & Roadmap, AI, Automation & Innovation, Technology Landscape Oversight. We could keep those as subheadings? But only allowed headings are the specified list; we cannot add extra headings. So we should just list all responsibilities as items under a single
  . However we might lose grouping but that's okay; we must preserve all info. We'll create
  • for each responsibility sentence. Similarly Requirements: list each bullet. Preferred Qualifications: could be under "Qualifications" heading? The spec includes Qualifications as a possible heading. We'll treat Preferred Qualifications as under "Qualifications". We'll include both required and preferred? Actually Requirements heading is for required qualifications. Qualifications heading could be for preferred? We'll include both under Requirements and Qualifications? Let's decide: Use Requirements for the required bullet list. Use Qualifications for the preferred qualifications list. That seems appropriate. Skills: Not explicitly listed; we could omit. Benefits: The posting mentions benefits: medical, dental, vision insurance, retirement savings plan, gender neutral parental leave, unlimited paid time off, flexible time off, year-round half-day Fridays, hybrid 3 day in office, 2 day at home work environment, bonus eligibility (200% of target over last seven fiscal years), equity. Also total compensation philosophy offers competitive pay and benefits, bonus eligibility, equity, flexible time off, year-round half-day Fridays, hybrid 3 day in office, 2 day at home work environment. We'll include Benefits section with
    listing each benefit. Pay: Not specific numbers, so omit. Schedule: Not specific beyond hybrid description; but that's more work arrangement; could be considered Schedule? The posting mentions hybrid 3 day in office, 2 day at home work environment. That's schedule info. Could include Schedule section with that detail. However the instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state hybrid schedule. So we can include Schedule with that detail. But we already included hybrid schedule in Benefits maybe; better to put schedule separate. We'll include Schedule section with

    describing hybrid 3 day in office, 2 day at home. Now we need to strip boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes some legal text at end: "This job description is intended to describe the general nature..." etc. Also privacy notice, AI tools statement. Those are boilerplate; we should remove them. Also the line "Visit our Career Page to learn more about our team: https://www.elfbeauty.com/work-with-us" maybe considered boilerplate? It's not navigation but could be considered company info; but it's a link to career page; might be considered boilerplate? Probably we should keep it as part of About the Company? But it's not substantive role info; it's a link to learn more about team. Might be considered navigation? Safer to remove. Also "Under e.l.f.’s annual bonus program, employees are eligible to earn up to 200% of their target bonus when company performance exceeds defined goals." That's benefits/compensation; we keep. Now produce HTML. Structure:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Qualifications

    • ...
    ...

    Benefits

    • ...
    ...

    Schedule

    Hybrid work environment: 3 days in office, 2 days at home.

    We must ensure we don't include headings with empty content. Now craft the content. About the role: combine the paragraphs after company description: "The HR & Legal Technology Operations Manager serves as ...". Let's extract: "The HR & Legal Technology Operations Manager serves as the enterprise-wide point of accountability for the technology ecosystem supporting the People and Legal functions. This is first and foremost a Technology leadership role with strong business partnership responsibilities — owning the health, roadmap, integration, governance, and continuous improvement of the applications and capabilities that enable both functions. This role acts as the U.S.-based bridge between HR, Legal, and Technology teams, translating functional needs and business outcomes into scalable, secure, supportable technology solutions. The role brings technical judgment, enterprise architecture awareness, and delivery discipline while building trusted partnerships with People and Legal leaders." We'll put that in

    . Now responsibilities list: need to capture each bullet under each subheading. Let's list them: From Technology Partnership & Functional Alignment: - Serve as the primary Technology partner to the People and Legal organizations, bringing the credibility to challenge, the judgment to listen, and clear accountability for technology outcomes - Translate HR and Legal operational needs into scalable technology capabilities, roadmaps, integrations, and delivery priorities - Engage with People and Legal leadership to align technology investments with functional strategy, enterprise architecture, security, data, and operating standards - Proactively identify opportunities to simplify processes, improve user experience, reduce manual work, and strengthen controls through technology and automation - Provide leaders with clear visibility into application roadmaps, delivery progress, risks, dependencies, and capability improvements From BambooHR Stabilization & Maturation (Near-Term Priority): - Assess the current BambooHR implementation and identify gaps in configuration, data quality, integration, security, supportability, and process coverage - Drive a structured stabilization effort: clean up the environment, establish governance, close adoption gaps, and build a sustainable technology operating model - Partner with HR Operations to clarify and document the core HR processes that technology must enable, translating process requirements into system design and configuration - Establish clear system ownership, support models, release practices, and change management disciplines to ensure BambooHR delivers consistent value - Build the data and integration foundation — including employee master data, organizational hierarchy, interfaces, and reporting — required for future platform evolution From Legal Technology & Operations Enablement: - Own the technology landscape supporting Legal, including the roadmap, lifecycle, support model, integrations, and continuous improvement of Legal applications - Partner with Legal leadership and Legal Operations to translate business processes into effective technology solutions across areas such as contract lifecycle management, legal intake and workflow, e-signature, document and knowledge management, and other legal operations capabilities - Assess the current Legal application portfolio for capability gaps, duplication, risk, adoption, integration needs, and opportunities for rationalization or automation - Establish technology governance and operating discipline for Legal systems, including ownership, access, data, vendor management, release planning, support, and lifecycle management - Ensure Legal technology solutions integrate appropriately with the broader enterprise ecosystem, including ERP, procurement, HR, identity, collaboration, and data platforms - Identify practical opportunities to use AI and automation to improve contract review, intake, knowledge retrieval, workflow efficiency, and other Legal operations use cases while partnering with Security, Privacy, and Legal stakeholders on appropriate controls From HR Platform Strategy & Roadmap: - Own the long-term HCM platform technical roadmap, evaluating organizational and technical readiness to scale beyond the current solution as the business grows - Partner with People leadership to assess platform fit — including capability gaps, integration complexity, security, data, supportability, and total cost of ownership — without anchoring prematurely to any single vendor - Lead the Technology workstream for structured, objective platform and vendor evaluations, bringing market knowledge, architecture judgment, and enterprise standards - Ensure platform decisions account for integration with the broader enterprise technology landscape, including ERP, finance, supply chain, identity, data, and collaboration platforms - Stay current on the enterprise HCM market, emerging capabilities, and best-fit criteria for high-growth organizations From AI, Automation & Innovation: - Maintain a forward-looking perspective on how AI and automation are reshaping HR and Legal technology, while grounding recommendations in clear business use cases, data readiness, risk, and enterprise standards - Evaluate and pilot capabilities that can reduce administrative burden, improve decision quality, accelerate workflows, and improve employee or functional user experience - Partner with HR, Legal, Security, Data, Architecture, and Technology leadership to shape practical AI roadmaps for the supported functions - Ensure data, integration, access, and governance foundations are sufficient to support responsible AI and analytics capabilities as they mature From Technology Landscape Oversight: - Serve as the single point of Technology visibility for HR and Legal applications and related SaaS platforms - Maintain a clear view of the value, health, lifecycle, cost, technical debt, and risk profile of each solution, rationalizing the portfolio over time to reduce fragmentation - Ensure integrations and dependencies across HR, Legal, and the broader enterprise technology and data environment are understood, documented, monitored, and governed - Oversee the health and evolution of connected HR systems such as ATS, LMS, workforce management, total rewards, and employee engagement platforms, as well as Legal systems supporting contracts, workflow, documents, and related operations - Ensure high standards for data integrity, system interoperability, access controls, privacy, security, auditability, and compliance with enterprise technology standards - Own or coordinate vendor and SaaS lifecycle management for the supported portfolio, including performance, roadmap alignment, renewals, and technical dependencies Now Requirements list: - Bachelor’s degree in Information Systems, Computer Science, Business, Human Resources, or related field. - 7+ years of experience owning or supporting enterprise applications in a business-facing Technology capacity, with meaningful experience in HR technology; exposure to Legal technology is strongly preferred - Proven track record as a trusted Technology partner to functional leadership — able to translate business needs while maintaining clear technology ownership and standards - Hands-on experience with at least one enterprise-grade HCM platform (SAP SuccessFactors, Workday, Oracle HCM, or equivalent) - Demonstrated experience stabilizing, maturing, or optimizing an underdeveloped enterprise application environment, not just implementing net-new systems - Strong understanding of core HR processes including Hire-to-Retire, Recruit-to-Onboard, Talent Management, Learning & Development, and Workforce Planning - Working knowledge of Legal technology and Legal Operations processes, such as contract lifecycle management, e-signature, legal intake/workflow, and document or knowledge management - Experience managing SaaS applications, integrations, data flows, access, vendors, and application lifecycle practices across enterprise platforms - Practical