How to Source the AI Roles Reshaping the In-House Legal Org Chart
By Matt DenOuden
August 17, 2026
Matt DenOuden is Vice President, GTM Strategy and Legal Ops Transformation at Onit. He has worked with more than half of the Fortune 500 and serves as executive sponsor to many of Onit’s largest customers. His 25 years of expertise spans legal process, AI innovation, workflow automation, and customer strategy.
Walk into almost any legal department today and you’ll notice the org chart looks a little different than it did two years ago. Alongside the classic in-house legal team, contract managers and compliance leads, you might now find a legal engineer, an AI trainer, a prompt engineer, or even someone with “Chief AI Officer” on their badge. This isn’t a passing trend. It’s a genuine restructuring of how legal departments think about talent, and it’s happening fast. The question is what AI roles should your department be looking for?
The numbers tell the story. Generative AI adoption in corporate legal departments has nearly doubled year over year, with 87% of general counsel now reporting some use of AI on their teams, up from 44% just a year earlier, according to FTI Consulting’s General Counsel Report. But adoption and maturity are two different things. Most of that FTI survey and a similar one from Axiom Law finds that while two-thirds of departments are still stuck in pilot mode, only a small fraction have actually scaled AI into daily workflows. The gap between “we bought the tool” and “we know how to run it well” is exactly where these new roles are stepping in. Leading companies have chosen to procure not just the AI tech but also the talent to wrap it around their workflows.
Who is actually filling these seats
Whether insourced or outsourced, it starts with the builders. The legal engineer is probably the most visible of the new titles, and also the most misunderstood. These aren’t junior lawyers moonlighting as coders. Legal engineers typically don’t actively practice law at all. They come from legal ops, product management, or technology backgrounds, and their job is to build and maintain the connective tissue between legal work and the tools that support it: workflow automation, contract data pipelines, no-code platforms, API integrations. Think of them as translators who happen to be fluent in both “redline” and “Python.”
A close cousin, borrowed from the broader software world, is the forward-deployed engineer: someone embedded directly with a legal team to configure an AI tool around that team’s actual workflows rather than shipping a generic product and hoping it fits. More and more law departments are concluding that they need legal-specific AI and that the enterprise tools fall short.
Next, are the people who make the AI itself trustworthy. An AI trainer, sometimes called an AI training specialist or legal AI analyst, annotates legal data, refines how a model interprets contract language, and makes key catches when it gets off track. Adjacent to that is the prompt engineer, whose job is narrower but no less important: designing and testing the actual instructions that get fed to a model so its output is consistent, accurate, and context-backed rather than confidently wrong.
Legal tech commentators have also started using the term legal quant for a related but distinct profile: a technically fluent lawyer, not a professional engineer, who builds their own AI-assisted workflows, chaining prompts together to extract contract terms, benchmark them, and craft a way to mine data without waiting on IT. It’s less a job title you’ll see posted than a skill set increasingly expected of senior associates and operational leads. All of this work increasingly happens in-house rather than being outsourced, because nobody understands the nuance of your company’s data, contracts and risk tolerance better than your own team.
Then there’s the risk side. AI compliance and governance roles have exploded in demand, arguably faster than any other category. Most organizations say they need more AI governance professionals than they currently employ, and LinkedIn’s Skills on the Rise report clocked 150% year-over-year growth in demand for these roles. What’s notable is what skills employers are actually seeking. Most aren’t hunting for deep technical experts. They want people who can translate between attorneys, IT, risk, and the C-suite, drawing on backgrounds in privacy, eDiscovery, or compliance rather than computer science. A related but distinct role is what some departments are calling the AI legal advisor: not someone administering the tools, but a lawyer whose day-to-day docket is specifically the company’s own AI use, from vendor contracts and IP exposure to the fast-moving patchwork of AI regulation. Where the compliance expert builds the governance program, the AI legal advisor is the one advising the business on it deal by deal.
At the top of the org chart, the Chief AI Officer (CAIO) conversation is a bit more nuanced than the title suggests. Dedicated CAIO roles inside legal departments specifically are still rare. What’s happening instead, is that general counsel and chief legal officers are simply absorbing AI governance into their existing mandate. Many CLOs now oversee three or more functions beyond traditional legal work, including privacy, ethics, and government affairs. AI oversight is becoming one more item on that already crowded plate, whether or not anyone updates their job title. And running underneath nearly all of it is legal operations, which has quietly become the connective tissue holding these new roles together. Legal ops is often the function actually vetting AI vendors, managing rollout, and measuring whether any of this is working.
Hire, upskill, or borrow a friend from IT?
So how should legal departments actually build out this capability? The honest answer is: some combination of all three, and the mix depends on the role.
Highly specialized, scarce skills, like true AI governance expertise, are worth hiring for, even though the market is tight. Compliance-focused hiring managers report average time-to-fill of four to six months for these roles, which is unusually long for anything tech-adjacent. If you wait until you desperately need this person, you’re already behind.
Upskilling makes more sense for roles closer to existing legal functions, like paralegals moving into contract automation or legal ops staff picking up prompt design. Robert Half’s research on legal hiring found that 79% of legal leaders report AI-related skills gaps on their teams, but also that firms investing in training see real returns; two-thirds of respondents cited investment in legal technology as key to attracting and keeping talent, alongside genuine professional development opportunities.
AI governance doesn’t live neatly inside legal, IT, or compliance. It lives in the seams between them. The departments getting this right aren’t necessarily the ones with the flashiest new title on the org chart. They’re the ones that figured out how to get legal, privacy, security, and the business talking to each other regularly, with someone whose actual job is to make sure that conversation happens.
None of this replaces the core value a lawyer brings: judgment, risk assessment, and advocacy. But it does mean the modern in-house legal team looks less like a group of lawyers with a shared associate pool, and more like a genuinely multidisciplinary unit. That shift is exciting for many, uncomfortable for some departments and overdue for others. No matter what, it’s not reversing. The current environment calls for and rewards action. Here are some first steps:
- Assess your current capabilities. Identify who already owns AI-related work, whether that’s legal ops, IT, privacy, or compliance.
- Map your highest-value AI use cases. Prioritize workflows where AI can deliver measurable efficiency, such as contract review, legal research, intake, or matter management.
- Identify skill gaps before creating new positions. Determine whether existing employees can be trained before opening new requisitions.
- Establish AI governance early. Create clear policies around approved tools, acceptable use, human review requirements, confidentiality, and data security.
- Build a cross-functional AI working group. Include representatives from legal, IT, information security, privacy, compliance, and procurement to guide adoption.
- Measure success. Define metrics such as time saved, cycle time reduction, user adoption, accuracy, or outside counsel spend before expanding AI initiatives.
- Embrace continuous learning. A vast array of resources can be found in the Onit OnPoint Community.
We are in a unique place in the adoption and innovation curve where AI is so exciting and transformational that it is bringing people together. Bring your veterans, bring the new hires, bring IT, and bring legal operations to host the party. You’ll be amazed at the rapid business impact a well-coordinated team can make.
Must read intelligence for general counsel
Subscribe to the Daily Updates newsletter to be at the forefront of best practices and the latest legal news.
Daily Updates
Sign up for our free daily newsletter for the latest news and business legal developments.