Solutions
Customer Support
Resources

Key takeaways:
Most legal teams meet product work as an interruption. An engineer asks whether a new feature can use customer data to train a model, and the answer is slow to come back because there's no specialist to advise.
By the time a company is shipping weekly, that pattern has a cost. Launches slip while legal catches up, or they go ahead without legal seeing them, which creates risk.
A product counsel exists to move the legal question upstream, into the design conversation rather than the launch checklist. This page covers what the role owns, how it differs from adjacent in-house roles, the background people come from, and what the available pay data tells us. If the pressure you're feeling is contract volume rather than product risk, our guide to the commercial counsel role describes a different hire that might be more appropriate.
Let's dive in.
A product counsel is an in-house lawyer who advises product and engineering teams on the legal risk in what the company builds, from feature design through launch.
The role concentrates on technology, fintech, consumer platforms and increasingly in life sciences. It blends work that used to sit across several specialisms: intellectual property, consumer protection, privacy, regulatory compliance and the terms that end users accept.
Writing in the ACC Docket, practitioners describe the role as spanning the full product management process, from feature request through release, so that legal input is consistent rather than arriving at the end. That end-to-end involvement is the part that distinguishes it from a generalist who reviews launches on request.
The shortage is in a particular skill combination rather than in lawyers generally. Major, Lindsey & Africa's 2026 legal hiring report found employers across the US struggling to fill roles requiring AI, cybersecurity, data privacy and compliance experience, and identified product counsel among the specialisms in demand.
What changed is that shipping a feature now carries regulatory questions that didn't exist a few product cycles ago. A generative AI feature raises training data provenance, output liability, disclosure and territorial availability in a single ticket. Those questions arrive at design time and can't wait for a launch review.
Six activities account for most of the week:
Getting into the design conversation. The work is issue-spotting at the specification stage: what data the feature touches, which markets it can launch in, what has to be disclosed to users. A product counsel who first sees a feature at launch is functioning as an approver rather than an advisor, which is the failure mode the hire is meant to prevent.
Answering the questions nobody owned before. Whether a model can be trained on customer data, what a vendor's terms permit, what the output is warranted to do, and what users are told. Gusto's 2026 product counsel advert asks for seven or more years of experience including AI product counseling or AI governance, which is a useful marker of where the bar sits in 2026-7.
Writing what customers actually agree to. Terms of service, acceptable use policies, end-user licence agreements and in-product disclosures. These change with the product, so they're a maintenance commitment rather than a drafting project.
Checking what the company owns and what it borrowed. Open source license compatibility, trademark clearance on feature names, and whether a competitor's patent affects something the team is building.
Making sure marketing can support what it says. Product counsel commonly review external communications about a product, which is where consumer protection risk concentrates. A performance claim in a launch blog is a representation.
Working out where a feature can go live. The same product often launches on different dates in different territories because the regulatory position differs. Somebody has to own that map and keep it current.
These three roles overlap enough that companies can easily hire the wrong one. The distinction that holds up is which team the lawyer sits with, and at what point in the development cycle their work happens.
In a small team, one person covers all three, usually badly, because the working rhythms conflict. Contract review can be batched, whereas a product question at design stage can't. Our guides to commercial counsel and privacy counsel cover two comparative hires in full.
There is no standard route, and the people doing the job arrived from several directions. Practitioners who have moved into it commonly advise entering a technology company through a commercial, transactional or litigation role first, then moving across internally, because getting the product team to trust and value you is half the battle.
Qualification is assumed: a practicing licence in at least one jurisdiction. Adverts in 2026 commonly ask for five to eight years of experience, with in-house technology experience weighted more heavily than firm pedigree.
The threshold is about the shape of the risk rather than the size of the company. A business whose product touches personal data, money, health information, minors or generative AI reaches it much earlier than one selling software to other businesses.
Below that threshold, most companies use a generalist plus outside counsel for the hard calls. The cost of getting it wrong is asymmetric, though: a feature built on a bad assumption is expensive to unwind after launch.
This role sits outside the main salary guides. Robert Half, BarkerGilmore and Barclay Simpson don't cover it, and the US Bureau of Labor Statistics has no category for it. There's self-reported data, but it's patchy.
The gap between the top and bottom rows is a result of four different organizations measuring different groups of people and labeling the result the same way. The Levels.fyi and Glassdoor figures include equity, which is where most of the value sits at a large technology employer, and both draw on populations who self-select into reporting.
If we had to be specific: at a US technology company, total compensation in the mid $200,000s upward is consistent with the reported data, with base salary well below that. Treat the Salary.com figure as measuring something else. For the method behind pricing any in-house role properly, see our guide to in-house lawyer salary benchmarks.
Sources: Levels.fyi and Glassdoor.
Product counsel generate contract artifacts continuously. Every change to the terms of service, every new data processing agreement triggered by a feature, every partner integration agreement starts as a product decision and ends as a document somebody has to version, approve and find again.
In Juro, those documents are built as structured data, so a change to a liability clause in the standard terms is versioned and attributable rather than living in a file named final_v4. When a customer asks which version of the terms they accepted and when, you can simply ask in Operator or Claude:
The wider case for keeping agreements queryable rather than filed is in contract data, and contract approval workflows covers routing changes for sign-off.
A product counsel buys judgment at design time, which is the cheapest point to apply it. It does not solve the contract volume that arrives afterward, and most teams underestimate how much of that a shipping product generates. Related reading: legal operations, how to review a contract, the automated lawyer, and the legal engineer for the most technical role on the spectrum.
In everyday use the terms are interchangeable, though product counsel is the title that appears on job adverts. Note that product lawyer also gets used for product liability work, which is a different practice entirely and mostly litigation.
Partly, and at many companies one person holds both. The overlap is real, since privacy by design means reviewing features before they are built. The gap is everything in a product review that is not about personal data: IP, open source, consumer claims and market availability.
Rarely as a first legal hire. Most startups need commercial coverage first, because contracts arrive before regulatory scrutiny does. The exception is a company whose product is regulated from day one, where product risk precedes revenue.
The common route is joining a technology company in a commercial, transactional or litigation role and moving across internally once you understand the product. Practitioners describe lateral movement inside big technology companies as the usual path rather than hiring directly into the role.





