About this evidence
Part 1 of the Institute for Legal Engineering™ research series examines the varied work described as ‘legal engineering’ and the questions this raises about occupational identity and professional recognition. This note explains the exploratory evidence used in that discussion and provides links to the underlying sources.
The collection contains 50 records: 44 recruitment records and six first-person or organisational accounts. It illustrates differences in role titles, responsibilities, organisational settings and entry expectations. It is an exploratory collection, not a representative employment-market sample.
What the collection covers
The evidence brings together an initial collection of 25 records and a further 25 selected advertisements from continental Europe. The initial collection includes roles titled Legal Engineer, related roles and accounts of work. The European collection focuses on Legal Engineer and close title variants.
| Component | Recruitment records | Accounts of work | Total |
|---|---|---|---|
| Initial collection | 19 | 6 | 25 |
| Continental European collection | 25 | 0 | 25 |
| Total | 44 | 6 | 50 |
The continental European collection contains advertisements from 20 named employers across seven countries, including Switzerland. Several employers appear more than once because they advertised distinct roles.
| Country | Advertisements |
|---|---|
| Germany | 8 |
| Netherlands | 2 |
| Poland | 2 |
| Switzerland | 4 |
| Sweden | 3 |
| Italy | 2 |
| France | 4 |
| Total | 25 |
The initial collection also includes material associated with the UK, US and Asia, including Malaysia, India and South Korea. Some sources cover multiple locations or describe an organisation’s work without identifying a single workplace. The index therefore preserves relevant location qualifications rather than assigning every record to one country.
How sources were selected and counted
The initial collection was assembled on 13 October 2026. Source checks and the continental European collection followed on 15 October, with targeted further checks of selected initial records on 19 October. These dates describe collection and checking, rather than the publication dates of the underlying sources. The European collection was not rechecked in the 19 October update.
The continental European selection required a named employer, an identifiable advertisement, a continental European location and substantive information about responsibilities. The initial collection has a broader scope: it also includes adjacent roles, a counsel role, an intermediary advertisement and accounts of work. Related titles are retained as published; their inclusion does not establish that all the work belongs to one occupation.
Recruitment records are counted by advertisement, rather than by office location or presumed number of hires. Alternative hosts, translations and materially parallel reposts were not automatically counted as additional advertisements. Potential duplicates and records lacking sufficient information were excluded from the selected European collection. Separate advertisements from the same employer were retained where the evidence identified distinct roles, including different customer segments or pre-sale and post-sale functions.
The six accounts of work are identified separately from recruitment advertisements. They provide attributed descriptions of activities and professional identities, rather than additional vacancies.
Reading the source index
The index links to employer pages, employer-authored recruitment listings, an intermediary advertisement and first-person or organisational accounts. Some recruitment systems displayed little substantive text on direct access; in those cases, substantive employer text available through search indexing informed the research. Indexed text can reflect an earlier version of a page. A title-only search result was insufficient for a detailed comparison of responsibilities or entry requirements.
Recruitment pages can change, close or redirect. The links identify the sources recorded at the time of the research; they do not indicate that the vacancies remain open or that every page remains accessible. The underlying research record contains selected extracts and summaries, rather than complete archived copies of every source.
Record identifiers allow sources to be traced across the research. The European identifiers retain gaps because records considered but not selected are omitted from this index.
Initial collection
| ID | Organisation or attributed account | Title and location as recorded | Kind | Source |
|---|---|---|---|---|
| 01 | bp | Legal Engineer; body says Legal Technology & Innovation Analyst / London, UK | Recruitment record | Source |
| 02 | bp | Legal Engineer / Kuala Lumpur, Malaysia | Recruitment record | Source |
| 03 | LexisNexis | Legal Engineer / Farringdon, UK | Recruitment record | Source |
| 04 | Harvey | Legal Engineer, EMEA / London, UK | Recruitment record | Source |
| 05 | Harvey | Legal Engineer (In-House) / New York, US | Recruitment record | Source |
| 06 | Harvey | Legal Engineer, Product Specialist / Seoul, South Korea | Recruitment record | Source |
| 07 | Harvey | Legal Engineer, Product Specialist Manager / Chicago, US | Recruitment record | Source |
| 08 | Legora | Legal Engineer / London, UK | Recruitment record | Source |
| 09 | Lawhive | Legal Engineer / London, UK | Recruitment record | Source |
| 10 | Chamelio | Legal Engineer / United States, remote | Recruitment record | Source |
| 11 | Redgate | Legal Operations Engineer / Cambridge, UK | Recruitment record | Source |
| 12 | Simpson Thacher & Bartlett | Legal Technologist / US offices listed in vacancy | Recruitment record | Source |
| 13 | Wordsmith | Legal Solutions Engineer / Header: Edinburgh and London; body: Edinburgh default office | Recruitment record | Source |
| 14 | Ashby | Legal Ops Manager / Location not confirmed from the available source text | Recruitment record | Source |
| 15 | Nevis Wealth | Legal Counsel / New York, US; on-site | Recruitment record | Source |
| 16 | e.l.f. Beauty | HR & Legal Technology Operations Manager / Multiple US locations/remote options | Recruitment record | Source |
| 17 | Cascade Asset Management Company | Legal Operations Analyst / Kirkland, Washington, US | Recruitment record | Source |
| 18 | Spellbook | Solutions Engineer / Remote US; body also permits Canada | Recruitment record | Source |
| 19 | Jobgether listing for an unnamed partner | Senior Legal Operations & Admin Executive / India, remote | Recruitment record | Source |
| 20 | Orbital Witness; Tassneem Attia | Legal Engineer / UK context; London office described | Narrative account | Source |
| 21 | Orbital Witness; Tessa Worrell | Legal Engineer / New York, US | Narrative account | Source |
| 22 | Summize team | Legal Engineer / Location not assigned from article | Narrative account | Source |
| 23 | TLT; Kiera Dale | Legal Technologist / UK organisational context | Narrative account | Source |
| 24 | Addleshaw Goddard; Alex Gray | Legal Technologist / UK organisational context | Narrative account | Source |
| 25 | Harvey team; includes Nehan Sethi | Legal Engineer / Global team account | Narrative account | Source |
Selected continental European advertisements
| ID | Employer | Title and location as recorded | Source |
|---|---|---|---|
| E01 | Gansel Rechtsanwälte | Legal Engineer (m/w/d) – Voll- oder Teilzeit / Berlin / Germany | Source |
| E02 | CMS Hasche Sigle | Legal Engineer (m/w/d) Automation / Berlin / Germany | Source |
| E03 | CMS Hasche Sigle | (Senior) Legal Engineer (m/w/d) AI Adoption / Eight German office options in one advert / Germany | Source |
| E04 | CMS Hasche Sigle | Senior Legal Engineer (m/w/d) AI / Development / Eight German office options in one advert / Germany | Source |
| E05 | LUPP + PARTNER | Legal Engineer / Jurist (m/w/d) – KI & Legal Tech / München, Frankfurt am Main, Hamburg / Germany | Source |
| E06 | KRAUS GHENDLER RUVINSKIJ | Legal Engineer (m/w/d) / Köln; application footer also mentions Berlin / Germany | Source |
| E07 | Legal Mind | Legal Engineer / Amsterdam / Netherlands | Source |
| E08 | HVG Law | Legal Engineer / Rotterdam / Netherlands | Source |
| E13 | Dentons Business Services EMEA | Senior Legal Engineer (Dentons Business Services EMEA) / Warszawa / Poland | Source |
| E15 | Omnilex | Legal Engineer – German-speaking / Zürich / Switzerland | Source |
| E17 | Schellenberg Wittmer | Legal Engineer 60–80% / Zürich or Genève / Switzerland | Source |
| E18 | DeepJudge | Legal Workflow Engineer / Zurich HQ / Switzerland | Source |
| E19 | Legartis Technology AG | Legal AI Engineer (Zurich) / Zurich / Switzerland | Source |
| E21 | Freda | Legal Engineer / Stockholm / Sweden | Source |
| E22 | Harvey | Legal Engineer, Sweden / Stockholm / Sweden | Source |
| E23 | Advokatfirman Lindahl | Legal Engineer / Stockholms län / Sweden | Source |
| E25 | Lexroom | Legal Engineer / Italian Market (Milan) / Milano / Italy | Source |
| E26 | Irnerius | AI Advisor – Legal Engineer / Milano / Italy | Source |
| E31 | Mueller.legal Rechtsanwälte | Legal Engineer (m/w/d) / Berlin / Germany | Source |
| E32 | Harvey | Legal Engineer (Transactional or In-house) / Paris / France | Source |
| E33 | Harvey | Legal Engineer, Product Specialist / Paris / France | Source |
| E34 | Legora | Legal Engineer, Law Firms / Paris / France | Source |
| E35 | Legora | Legal Engineer, In-House / Paris / France | Source |
| E38 | Wolters Kluwer | Legal Engineer – Public Sector (Libra – Legal AI Assistant) / Warszawa / Poland | Source |
| E41 | Grubel | Founding Legal Engineer / Munich or Tübingen / Germany | Source |
Qualifications relevant to interpretation
HVG Law (E08). The source check on 15 October 2026 recorded the statement “Een specifieke juridische of IT achtergrond is niet vereist” — that a specific legal or IT background is not required. The original LinkedIn vacancy subsequently redirected. Part 1 therefore relies on the dated research record for this statement, rather than a fresh inspection of the original advertisement.
Location and entry requirements. Wordsmith (13) listed Edinburgh and London in the header while describing Edinburgh as the default office in the body. Ashby’s location (14) could not be confirmed from the available substantive text. Spellbook (18) described the role as remote in the US while also permitting candidates entitled to work in Canada; Microsoft 365/Word add-in experience was desirable rather than mandatory. These qualifications matter when comparing locations and requirements.
Intermediary advertisements. Jobgether (19) advertised for an unnamed client. It is identified as the intermediary, rather than treated as the hiring employer. The substantive description was available through indexing when the direct page was unavailable.
What the evidence can and cannot establish
Recruitment documents show how particular roles were advertised and what employers said they sought. They do not establish whether a vacancy was filled, how many people were hired, what work was subsequently performed or how competence was assessed in practice. Accounts of work provide the perspectives of their authors or organisations; they are not independent observations of those activities.
The collection supports examination of variation and comparison of particular examples. It does not support estimates of the prevalence of an activity or qualification across the employment market. Employer concentration, language coverage, platform access and source availability affect what is visible.
An entry requirement omitted from the available text is different from an express statement that the requirement is unnecessary. Neither omission nor an isolated advertisement establishes a general rule for the field.
The evidence does not settle whether these roles constitute one occupation, establish a shared competency framework or determine a certification threshold. Those remain questions for further research and consultation, including input from employers, people doing the work, professional bodies and regulators.