Director of People Technology & Data
Legora · New York, NY · 1 mo ago
On-siteInformation Technology$224k–$263k/yrFull-time
We need to output HTML fragment with sections: About Us? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings if appropriate? They said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; we could also add other headings if needed but better to stick to those. The "What’s In It For You" includes Global collaboration, Competitive package, Meaningful work, In-person environment. Those could be considered Benefits or maybe part of Benefits. But we already have Benefits section for medical etc. Could combine them under Benefits? Might be okay to have a separate section like "What’s In It For You" but not in examples. Safer to incorporate those points into Benefits section as additional bullets.
Thus Benefits bullets: Global collaboration: Partner with teams and clients across Europe, APAC, and North America. Competitive package: Comprehensive salary, benefits, and tools for success. Meaningful work: Your efforts shape how thousands of lawyers use AI daily. In-person environment: Union Square office designed for ambitious builders and company provided lunch daily. Then the specific benefits list.
We need to preserve all substantive information; we should not lose any.
Let's extract content.
About Us paragraph: "Legora is redefining how legal work gets done. Not built for lawyers, built with them. We work alongside the world’s best legal teams, who expect excellence, precision, and speed, and we hold ourselves to the same bar. Our AI-native workspace lets legal professionals move faster, think more clearly, and operate with sharper precision. By analysing thousands of documents in minutes and powering end-to-end workflows, we cut through complexity, teams can focus on what matters: judgment, strategy, and outcomes. 1,000+ customers across 50+ countries trust us, including Cleary Gottlieb, Goodwin, Linklaters, White & Case, Dentons, and Barclays. We’ve scaled to $100M+ in ARR, with teams across Europe, North America and APAC, and continue to expand through acquisitions including Qura, Walter AI and Graceview. We partner with world-class performers: including Aaron Judge and the New York Yankees, Ludvig Åberg (and his caddie), and campaigns featuring Jude Law. Joining Legora means three things. We lean in: ownership over titles, outcomes over intentions.We fight for excellence: high standards, direct, ego-free feedback.We grow together: as a team and with our customers. Mission before ego. Everyone contributes. No one coasts. If you’re driven by impact, pace, and raising the bar. This is the place."
That's about us. Should we include as a section? Possibly "About the role" is for role description, not about company. But we could include an "About Us" section using
.
Now Qualifications: from "What You Bring". Bullets:
- 10+ years of experience in HR technology, HRIS, enterprise systems or related technology leadership, including experience leading teams and delivering large-scale transformation.
- Deep HRIS expertise, ideally including leading a global HRIS HCM implementation and establishing the platform's long-term operating model.
- Experience designing and managing HR technology ecosystems, including integrations, security, data architecture and global system governance.
- A strong product mindset, with the ability to translate business and employee needs into intuitive, scalable technology solutions.
- Experience building People analytics and data governance capabilities, with a strong understanding of workforce data and its application to business decisions.
- A track record of using automation and emerging technologies to simplify processes, improve experiences and increase operational efficiency.
- Experience operating in a high-growth, international environment, with an understanding of the challenges of scaling systems across multiple entities and jurisdictions.
- The ability to balance strategic architecture and long-term thinking with pragmatic execution. You know when to build for the future and when to ship a simpler solution now.
We'll list each as .
Now Benefits: from "What’s In It For You" plus "Benefits & Perks". Let's list:
Global collaboration: Partner with teams and clients across Europe, APAC, and North America.
Competitive package: Comprehensive salary, benefits, and tools for success.
Meaningful work: Your efforts shape how thousands of lawyers use AI daily.
In-person environment: Union Square office designed for ambitious builders and company provided lunch daily.
Benefits & Perks: We invest in our people with a comprehensive, thoughtfully designed benefits package:
- Medical, Dental & Vision
- Multiple medical plan options through Aetna and Kaiser Permanente
- HSA or Healthcare FSA (based on plan selection)
- Dental plans via MetLife
- Vision plans via Vision Care
- Family Support: Generous parental leave, Free access to Maven Clinic, Dependent Care FSA, Free One Medical membership for employees and dependents
- Additional Perks: Pre-tax commuter benefits, Life Insurance + STD/LTD, 401(K) with generous company match, Unlimited PTO, Robust voluntary benefits, including identity protection (via Aura), legal coverage via MetLife, pet savings programs, and more
We need to preserve all. We'll create bullets for each distinct item. Might be many; we can group but keep substance.
We'll create
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings if appropriate? They said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings when we have content. The posting includes "About Us", "The Role", "What You’ll Do", "What You Bring", "What’s In It For You", "Benefits & Perks", "Compensation Range". Also there is a line about "Global collaboration: ..." etc.
We need to map to headings: "About the role" maybe corresponds to "The Role". "Responsibilities" corresponds to "What You’ll Do". "Requirements" or "Qualifications" corresponds to "What You Bring". "Benefits" corresponds to "Benefits & Perks". "Pay" corresponds to "Compensation Range". "Schedule" maybe not present; we should not create if not present. Also "Skills" maybe not separate.
We must not repeat job title as heading; we don't have job title explicitly. We'll ignore.
We need to preserve all substantive information, remove boilerplate: EEO statement, maybe also "Legora is an Equal Opportunity Employer" etc. Also remove navigation, cookie, legal, etc. There's none besides that.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
About the role
... content from "The Role" paragraph(s).
Responsibilities
- ... each bullet from "What You’ll Do".
Qualifications
- ... each bullet from "What You Bring".
Benefits
- ... each bullet from "Benefits & Perks".
Pay
Compensation Range: $223,550 - $263,000
Potentially also include "Global collaboration" etc as part of "What’s In It For You". That could be part of Benefits? Or maybe a separate section like "What’s In It For You" but not in list of allowed headings. The instruction says use those headings as examples, but we can also use other headings if needed? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; we could also add other headings if needed but better to stick to those. The "What’s In It For You" includes Global collaboration, Competitive package, Meaningful work, In-person environment. Those could be considered Benefits or maybe part of Benefits. But we already have Benefits section for medical etc. Could combine them under Benefits? Might be okay to have a separate section like "What’s In It For You" but not in examples. Safer to incorporate those points into Benefits section as additional bullets.
Thus Benefits bullets: Global collaboration: Partner with teams and clients across Europe, APAC, and North America. Competitive package: Comprehensive salary, benefits, and tools for success. Meaningful work: Your efforts shape how thousands of lawyers use AI daily. In-person environment: Union Square office designed for ambitious builders and company provided lunch daily. Then the specific benefits list.
We need to preserve all substantive information; we should not lose any.
Let's extract content.
About Us paragraph: "Legora is redefining how legal work gets done. Not built for lawyers, built with them. We work alongside the world’s best legal teams, who expect excellence, precision, and speed, and we hold ourselves to the same bar. Our AI-native workspace lets legal professionals move faster, think more clearly, and operate with sharper precision. By analysing thousands of documents in minutes and powering end-to-end workflows, we cut through complexity, teams can focus on what matters: judgment, strategy, and outcomes. 1,000+ customers across 50+ countries trust us, including Cleary Gottlieb, Goodwin, Linklaters, White & Case, Dentons, and Barclays. We’ve scaled to $100M+ in ARR, with teams across Europe, North America and APAC, and continue to expand through acquisitions including Qura, Walter AI and Graceview. We partner with world-class performers: including Aaron Judge and the New York Yankees, Ludvig Åberg (and his caddie), and campaigns featuring Jude Law. Joining Legora means three things. We lean in: ownership over titles, outcomes over intentions.We fight for excellence: high standards, direct, ego-free feedback.We grow together: as a team and with our customers. Mission before ego. Everyone contributes. No one coasts. If you’re driven by impact, pace, and raising the bar. This is the place."
That's about us. Should we include as a section? Possibly "About the role" is for role description, not about company. But we could include an "About Us" section using About Us
though not in examples. The instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It may be interpreted that we should use those headings for sections; but we could also add an About Us heading if we want. However they said "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It may be interpreted that we should use those headings for sections; but we could also add an About Us heading if we want. However they said "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." They didn't forbid other headings. But they gave examples; maybe they expect us to use those headings only. However the posting includes an "About Us" section that is substantive; we need to preserve it. If we cannot create a heading for it, we could fold it into a
under maybe "About the role"? But that would be mixing. Better to create a heading "About Us". The instruction didn't explicitly forbid; it just gave examples. I'd include an
About Us
with the paragraph. Now "The Role" paragraph: "This role owns the technology, products and data intelligence that enable Legora's People function to scale, and make it easier for employees and managers to get things done. From implementing our global HRIS to building intuitive employee experiences and unlocking the value of our people data, you'll create an infrastructure that scales ahead of the business. You'll bring a product mindset to People technology, choosing the right tools to deliver the best experience. You'll balance a stable, secure core technology stack with the flexibility to experiment with new tools, automation and AI. You'll lead a growing team and work closely with your stakeholders to turn complex business requirements into simple, scalable solutions." We'll put that underAbout the role
maybe? Actually we already used About Us; we could rename The Role to About the role. SoAbout the role
with that paragraph. Now Responsibilities: list from "What You’ll Do". Let's extract bullet points: - People Tech Stack: Define and own the People technology roadmap, architecture and investment priorities. Build a secure, integrated technology ecosystem that supports our global growth, with a stable HRIS at its core and specialist tools where they deliver a better experience. Ensure systems are secure, connected and scalable. Partner with IT to manage integrations, access controls, security, release management and platform reliability. - HRIS implementation: From requirements and design through to configuration, testing, deployment and adoption. Own the long-term platform strategy and continuous improvement, working with implementation partners, IT and functional stakeholders. - People Products: Establish a product-led approach to People technology. Understand user needs, and design intuitive digital experiences for employees, managers and the People team. Choose the right tool for the job, leveraging automation and AI to simplify processes, remove manual work and create better experiences. - People Intelligence: Build the data infrastructure, governance and analytics capabilities that enable better workforce decisions. Establish common data definitions, quality standards and clear data ownership, ensuring a reliable single source of truth. Develop the analytics roadmap and turn trusted workforce data into actionable insights for the business. - Leadership: Build and lead a high-performing People Technology & Data team. Manage implementation partners and specialist vendors, establish clear delivery accountabilities and build strong relationships across People, IT, Finance and the business. We'll make each as- with
- for each bullet.
Now Pay: compensation range.
Now we should not include EEO statement.
Now output HTML.
Let's craft.
We'll start with
About Us
...
ThenAbout the role
...
ThenResponsibilities
- ...
Qualifications
- ...
Benefits
- ...
Pay
Compensation Range: $223,550 - $263,000
Make sure no extra whitespace issues. Now produce final