Legal AI Engineering is an emerging specialization. Employers are beginning to hire for these skills, but practical, integrated engineering training remains relatively uncommon. This is that training: the person who can actually build AI for legal work — and prove it holds up. Two hands-on days — three if you add the Deep Dive. Ingest messy legal data, make it searchable, add retrieval that cites its sources, keep it private on a local model and prove nothing left the machine, then measure a document review well enough to defend the numbers. You finish with a working repository, not notes.
An Elephant Scale course · Intermediate to Advanced · Live online, 9:00–16:00 US Central · 2-day Core,
plus a 1-day Deep Dive scheduled separately
taught by Mark Kerzner, the engineer who builds FreeEed
No payment, no commitment. You are telling us you want the dates and which format suits you.
Legal work is being handed AI faster than anyone is being trained to build it. Training exists for the pieces — legal technology, eDiscovery, AI engineering, “AI for legal” generally. What is uncommon is the integration: one build path from messy data to something you can be cross-examined on. That is what this course is.
Two claims run through every module, because they are the two a legal engineer actually has to make:
Nine postings, six employers, read on 11 November 2026 — a snapshot, not a market study. At four of those six employers, the job titled Legal AI Engineer is a J.D.-gated role: they want a lawyer who already practises, and no course can get you one.
The roles that want what this course teaches — build the pipeline, prove the privacy, measure the review — exist at the same employers, pay comparably or better, and are titled something else: forward-deployed engineer, AI automation engineer, AI solutions engineer. Knowing which half of the market to apply to is the first hour of the course, and it is worth more than another lab.
Nobody is born a legal engineer. People arrive from one of two directions, and the course is built to take either one.
You already have the half that takes years to acquire: you know what the work actually is, what a privilege call costs, and why a production has to be right the first time. What this adds is the building — so that the next time a tool cannot do what the matter needs, you are the person who makes one.
And the straight version, because you should have it before you register rather than after: the labs are hands-on Python. You will write code. You will write it with an AI assistant beside you — that is a prerequisite of the course, not a crutch, and it is how this job is genuinely done now. But the course as it runs today is pitched intermediate-to-advanced. If you have never written a line, say so on the form. If enough of you do, we will run a paced cohort that starts further back. We would far rather build that than have you spend day one lost.
You have the stack. What you are missing is the domain — and in legal work the constraints that decide whether a system is usable are mostly not the technical ones. No legal background required — privilege, defensibility, production and the rest are taught in context, as the problems they actually are. You will finish able to talk to lawyers about the thing you built without either side translating.
Also squarely in scope: engineers already at legal-tech companies who have the platform but keep hitting the legal-domain depth they were never taught.
The Core — two days, the full build path:
Every design decision in these labs was made once already, under load, in a product that ships — which is why the course can tell you why a thing is built that way and not just that it is. That product is FreeEed: Apache-2.0, on-prem eDiscovery — extraction across 1,400+ file types, OCR, imaging, PST/OST, Solr/Lucene search, review and export. It is the reference architecture the course points at, and you can download it and run it today.
Nothing in the course requires it. The labs are self-contained Python over synthetic corpora, there is no vendor account and no licence, and FreeEed is Apache-2.0 — there is nothing here to buy. It is in the course because it is a real system you can open up, not because it is ours.
Tell us how to reach you and what fits. Dates go to this list first.
We will email you about dates for this course and nothing else. No list, no partners.
© 2026 FreeEed. All Rights Reserved.