What should you ask a litigation support specialist in an interview? Questions and what good answers sound like
An employer-side question bank for interviewing a litigation support specialist at a law firm: skills and behavioral questions with answer guides, a practical exercise on a mock data set, and the questions to keep out of the room.
The questions to ask when hiring a litigation support specialist are the ones that surface systems a candidate has actually run — the productions built, the document databases administered, the hearings supported — plus how they handle confidential material, colliding deadlines and attorneys in a panic, and where their judgment ends and counsel's begins.
Below is that question bank for law firms: what each question reveals, what strong answers sound like, a practical exercise, and the questions to keep off your list.
Before the interview
Write the questions from the job description, not from a generic list.
If you have not settled the seat itself — the systems, the matters, who the hire supports and how much of the technology they own — start with our guide to how to hire a litigation support specialist, then sharpen the questions once the litigation support specialist job description says what the hire will actually do.
The interview's job is to test the claims that posting makes.
This page treats litigation support as several jobs that share a title: running the document databases and the eDiscovery workflow behind reviews and productions, supporting hearings and trials in the courtroom, and coordinating the vendors and processing providers who do work the firm does not.
Decide which mix you are hiring for and weight the questions toward it; a strong database-and-productions hire and a strong trial-support hire are not the same experience.
Decide two things before the first candidate sits down: the practical exercise you will use, and the scoring sheet you will fill in right after each interview.
Keep both identical for every candidate, and score while the specifics are fresh — comparisons made from memory weeks later are comparisons made from charm.
Two legal rails belong under the exercise.
Under EEOC guidance, a required test must be necessary and related to the job and must not exclude people of a particular protected group or people with disabilities.
And an employer must provide an accommodation a disabled applicant needs to apply for the job — a sign language interpreter, for example — unless it causes significant difficulty or expense.
Keep the exercise hypothetical.
The FLSA is the reason: "employ" includes "to suffer or permit to work" (29 U.S.C.
203(g)), so a candidate producing real, usable work for the firm — running processing on a live matter, for example — can be an employee owed wages.
A short exercise on a mock, disguised data set is the safer design.
Tell every candidate up front that they should not share client-identifying detail in the room: ask about the kind of work, not the parties.
How a candidate handles the instruction is itself a data point.
And set the pay range before the loop starts — if you are hiring in California, Labor Code 432.3 requires giving an applicant the position's pay scale on reasonable request, whatever the firm's size.
Which skills questions reveal real litigation support specialist experience?
Walk me through the last production you supported from start to finish — the data arriving, the work in between, the files going out — and be precise about which parts were yours.
What to listen for: Strong answers separate their own work from the team's and the vendor's, and name the stages in order: the data processed and culled, the review the firm's attorneys ran, the format the receiving party specified, the quality checks before anything left the building.
Pick one stage and probe; a real production gets more specific under pressure.
A theme with no matter under it — I ran eDiscovery — is the weak version of this answer.
Which systems have you personally operated for a litigation team — review platforms, document databases, processing tools — and what did you actually do inside each one?
What to listen for: Strong candidates name specific tools and specific tasks: builds and imports they ran, searches they wrote for attorneys, user access they administered, reports they produced.
The distinction matters because a seat that operates the systems and a seat that schedules around them are different jobs — decide which one you are filling.
Follow up with what broke once — a candidate who has only watched the software has no failures to describe.
Tell me about working with an eDiscovery vendor or processing provider. What did you hand off, what came back, and what did you check?
What to listen for: Strong answers describe managing the handoff in both directions: a spec sent in writing, deliverables tested against it rather than trusted, problems sent back with specifics, and escalations that reached counsel early.
Weak answers describe emailing files and hoping.
If your firm outsources processing, this answer is the difference between a manager and a messenger.
A hearing is three weeks out and the attorneys want exhibits presentable in the courtroom. What do you do between now and then?
What to listen for: Strong candidates work backward from the hearing date: the exhibit list confirmed, the presentation built and tested on the equipment that will actually be in the room, a rehearsal with the attorneys, and a failure plan for the day.
Weak answers start with the software.
Whatever your trial workload is, this answer tells you whether the hire can carry a courtroom or only a conference room.
A new matter just came in. What do you set up before the first document lands?
What to listen for: Strong answers describe building the workspace before the pressure arrives: the database or repository structured to the team's conventions, naming and access decided and written down, confidentiality rules applied from the first upload.
Weak answers wait for the documents and improvise.
Ask what their conventions cover — a candidate who cannot name a single one has been working inside someone else's system, not running one.
Which behavioral questions test judgment, confidentiality and deadlines?
Tell me about a time someone outside the case team — another client of the firm, a colleague, a stranger online — asked you about material you worked on. What did you say?
What to listen for: Strong answers decline without drama, confirm nothing, and keep client identifiers out of the telling.
The dangerous answer is the entertaining one: a candidate who walks you through a former client's most sensitive documents is showing you how they will treat yours.
The seat runs on confidential material, so score discretion above storytelling.
Walk me through a week when two attorneys needed productions at the same time and one of the deadlines moved. What moved, and who did you tell?
What to listen for: Strong answers triage by consequence, escalate to the attorneys early, and treat nobody told me as the failure to avoid.
Weak answers amount to I worked harder, with no system in them and nobody told.
Ask what changed in their tracking afterwards — the fix is the real answer.
Tell me about a production mistake that reached the other side — wrong files, wrong format, wrong anything. What happened next?
What to listen for: Strong answers own it fast, tell the attorneys immediately, help correct the production, and change the check that would have caught it.
Weak answers blame the vendor, the software or the clock — or insist it has never happened.
In this seat the cover-up is the career risk; a candidate who can describe a well-handled mistake is safer than one with no mistakes at all.
Describe a time you found privileged or confidential material somewhere it should not have been — in a data set, a folder, a production draft. What did you do?
What to listen for: Strong answers stopped and flagged it: sealed or quarantined the material, told the attorneys before anyone else looked, and left the trail clean.
Weak answers read it, forwarded it, or resolved it themselves.
Press on who they told first — the strong answer is counsel, and quickly.
Tell me about a time you pushed back on an attorney or a vendor — a shortcut, a scope change, a step someone wanted to skip. How did it end?
What to listen for: Strong answers held the line without theater: the risk named plainly, the decision routed to the person entitled to make it, the protocol followed until counsel changed it.
Weak answers are either I just do what I'm told — which is how protocol violations happen — or a story about winning an argument rather than protecting a production.
You are listening for judgment about whose call it is.
What practical exercise or test should a litigation support specialist complete?
Hand them a small mock data set — a folder of mixed files: email exports, spreadsheets, images, a few odd formats — and ask how they would get it ready for attorney review.
What to listen for: Strong candidates ask questions before they touch anything: what the matter is about, what the production deadline is, what the receiving party's spec says.
Then they describe the order of operations — identify what is there, remove the duplicates and system files, load what remains, and document what they did.
Weak candidates start clicking.
The questions are the experience.
Give them a one-page mock production request and ask what they would do first — and what they would confirm with counsel before starting.
What to listen for: Strong candidates read the spec closely and flag its ambiguities out loud: the format, the date range, the fields, what confidential material gets withheld and who decides.
Weak candidates summarize it back as if it were all clear.
The habit you are testing — confirm before you build — is the one that prevents the expensive errors.
Run a deadline scenario: the data arrives late, the production date does not move, and they own the week. Ask them to lay out the week.
What to listen for: Strong candidates work backward from the date, name the checkpoint where they would escalate to the attorneys, and build in testing time before anything goes out.
Weak candidates start with hope.
The answer shows you the calendar discipline before you have to trust it with a real one.
Ask for a production set, database report or trial presentation they personally built in the last year, redacted before it reaches you.
What to listen for: A strong candidate produces one quickly and can walk through every choice in it: how it was structured, what was checked, what went back for another pass and why.
A weak showing is an old sample, work someone else largely assembled, or a document the candidate cannot discuss in detail.
Redaction is part of the exercise, not an excuse to skip it.
If the seat carries courtroom work, have them talk through setting up an exhibit presentation from a mock exhibit list — or walk you through the last one they ran.
What to listen for: Strong candidates describe the full run: the equipment tested in advance, the exhibits built and ordered, a rehearsal with the attorneys, and a backup plan for the morning something fails.
Weak candidates describe the software's features.
If you cannot tell the difference in the room, ask what their backup plan has actually been used for.
What do strong vs weak answers sound like?
Ownership: I processed the data, built the review workspace and ran the checks before anything went out — strong. I did eDiscovery at a large firm — weak.
What to listen for: The strong version contains work you could verify — stages, systems, checks — and the candidate can go a level deeper on any of it when you probe.
The weak version describes an employer and a software category, with no personal doings anywhere in it.
Every follow-up you ask tests which version you are hearing.
Confidentiality: I flagged the privileged documents, sealed them and told the attorneys the same day — strong. A detailed story about the most sensitive material they have ever processed — weak.
What to listen for: The strong answer protects the client and describes the behavior, not the story.
The weak answer is entertaining — and disqualifying: a candidate who talks through a former client's most sensitive production in your interview will talk about yours somewhere else.
Score charm lower than discretion.
Deadlines: The data came in late, so I flagged the risk the same day and we re-sequenced the week — strong. I have never missed a production deadline — weak.
What to listen for: The strong answer shows a system — early warnings, escalation, a re-planned week — plus one specific save.
The weak answer offers perfection, which real production deadlines make hard to believe; press gently and the follow-up tells you which one it is.
Judgment: I held the export until counsel confirmed the format, and it cost us a day — strong. I just build whatever the attorney asks for, however they ask for it — weak.
What to listen for: The strong answer shows a working line between serviceable and safe: a day lost to a confirmed spec beats a production recalled.
The weak answer sounds flexible and is the expensive one — it is how privileged material ends up in the wrong production.
It is the cheapest disqualifying answer on the page.
Which questions are illegal or risky to ask?
Treat this as risk management, not a list of magic words.
Under EEOC guidance, federal law does not clearly forbid every interview question that touches race, sex, national origin, religion or age — but such questions can be used as evidence of an intent to discriminate unless they are justified by a business purpose, and the guidance's working rule is that pre-employment questions should be limited to what is essential to deciding whether a person is qualified.
A litigation support hire sits close to several of these questions — the whole interview is about whether this person can be trusted with sensitive material — which is exactly why the script needs a clean list.
The flags below are what to keep out of it, and what to do instead.
Have employment counsel confirm the final version before your first interview.
- Protected traits dressed as small talk. When did you graduate, are you planning children, what church do you attend, who watches your children — the EEOC publishes separate guidance on pre-employment inquiries about race, height and weight, financial information, unemployed status, religious affiliation, citizenship, and marital status or number of children. If a question would matter to you only because of a protected trait, it is not essential to the hiring decision.
- Medical questions before an offer. FTC and EEOC guidance is blunt: employers should not ask medical questions before a conditional job offer. Ask about the job's demands — heavy production weeks, courtroom days, after-hours support — and keep health conditions and disabilities out of the question script.
- Salary history, asked directly. What were you making at your last firm? is barred or restricted in California, New York, Illinois, Massachusetts, Connecticut, Virginia and Nevada: California Labor Code 432.3 bars all employers, of any size, from seeking an applicant's salary history — compensation and benefits included — orally or in writing, personally or through an agent, and from relying on it in hiring and pay decisions. New York Labor Law 194-a bars employers from relying on an applicant's wage or salary history, from requesting or requiring it as a condition of being interviewed, considered, hired or promoted, or from seeking it from a current or former employer. Illinois (820 ILCS 112/10(b-5) and (b-10)) makes it unlawful to screen applicants by salary history, to request it as a condition of an interview or offer, or to seek it from a current or former employer. Massachusetts (G.L. c.149 s.105A(c)(2)) bars seeking it from the candidate or a current or former employer. Connecticut bars asking about wage and salary history unless the applicant volunteers it. Virginia (Virginia Code 40.1-28.7:12) and Nevada (NRS 613.133) also ban seeking salary history.
- Salary history — what you can do instead. Ask expectations, not history: California Labor Code 432.3 expressly allows asking an applicant about their salary expectation for the position, and an employer may consider salary history the candidate volunteers without prompting. New York allows confirming history only at the offer stage — when you have made an offer with compensation and the candidate responds by citing prior pay to support a higher number. Massachusetts allows confirmation only after voluntary disclosure or after an offer with compensation has been made.
- Criminal history, asked too early. It is generally not illegal for an employer to ask about an applicant's background or require a background check, apart from restrictions around certain medical and genetic information — but when and how you ask is regulated, and the FTC and EEOC guidance warns that a criminal-record exclusion that significantly disadvantages a protected group and does not predict job performance can be unlawful disparate impact. California's Fair Chance Act (Gov. Code 12952) bars employers with five or more employees from including conviction-history questions on an application, or otherwise inquiring into or considering conviction history, until after a conditional offer. New York City's Fair Chance Act, part of the NYC Human Rights Law since October 27, 2015, makes it unlawful for most employers to ask about or consider criminal history before a conditional offer. Illinois' Job Opportunities for Qualified Applicants Act (820 ILCS 75/15) bars covered employers from asking until the applicant has been found qualified and notified they are selected for an interview — or, when there is no interview, until after a conditional offer.
- A practical exercise built on the firm's real work. The FLSA defines employ as including to suffer or permit to work (29 U.S.C. 203(g)), so a candidate producing real, usable work for the firm can be an employee owed wages. An exercise run on a live matter also hands the candidate client material before they are hired. Keep the exercise on a mock, disguised data set.
- The step after a conviction question becomes lawful. In California, an employer that plans to deny a job over conviction history must make an individualized assessment, notify the applicant in writing, and give at least five business days to respond before a final decision.
- Assuming size exempts you. Federal anti-discrimination law covers private employers with 15 or more employees for Title VII, the ADA and GINA, and 20 or more for the age discrimination law (ADEA) — in each case counting employees who worked at least 20 calendar weeks in the current or prior year — and the protections reach applicants and former employees as well as current staff. The federal numbers are not the whole test: California's Fair Chance Act reaches employers with five or more employees, and this page's research did not confirm a size threshold for every state and city statute named above. Confirm coverage with employment counsel.
- Treating this page as the whole map. This page names only the jurisdictions its research covered; it is not a count of the states and cities with salary-history or fair-chance rules, and many cities and other states have their own. Before you finalize your script, have employment counsel check the rules where your firm and each candidate sit.
After the interview
Score the same day, on the same axes.
Verified systems experience, judgment, discretion, deadline discipline — the four things these questions were built to test.
Grade each interview alone before the panel compares notes, so the loudest voice in the room does not set the scale.
What strong answers sound like.
Specificity you could check: matters and stages named, the candidate's own work separated from the team's and the vendor's, problems volunteered as readily as successes, and at least one thing they would do differently.
In the exercise, strong candidates say they do not know and then reason to a next step — knowing the edge of what you know is a skill, not a gap.
Verify before the offer.
Write down the specifics you intend to check — the employers, the systems, the matters as the candidate described them — and call the references who actually watched the work, the supervising attorney first.
Keep what you wrote down: FTC and EEOC guidance says private employers must keep personnel and hiring records, including applications from people who were not hired, for at least one year from the date the record was made or the personnel action taken, whichever is later.
Know your market before the pay conversation.
Our research found no BLS occupation code for litigation support specialists, so the closest proxy occupations in the legal services industry are Legal Support Workers, All Other (SOC 23-2099), with a median annual wage of $63,100, and Computer Occupations, All Other (SOC 15-1299), with a median annual wage of $105,500 — both BLS OEWS May 2025.
Employers may report this seat under more than one code, and our research cannot tell you which code a given employer actually uses, so read the two medians as brackets, not one number.
The questions a litigation support specialist candidate asks you — and what they signal.
Leave real room at the end, because the questions are data too:
- "What does your review and production workflow look like today, and who owns it?" — a candidate thinking about the operation they are joining, not just the title. Answer honestly, including the parts that are messy; the person you hire will inherit them, and a strong candidate is pricing that in.
- "Which systems would I work in, and who decides when they change?" — signals someone who has lived through a platform change and wants to know who is accountable. Name your stack and the gaps you expect the hire to help close.
- "How many matters would I support at once, and who do I take direction from?" — a workload-and-supervision question, and a fair one. Answer from your current docket, not an aspiration — and note that a candidate who asks nothing about the work is telling you something too.
- "What does trial support look like here — travel, courtroom days, after-hours calls?" — signals a candidate who has lived through trial technology failures. Whatever your answer is, make it honest about the expectations.
- "What is the pay range for this role?" — a reasonable question and, in places, one with a legal answer behind it: California requires employers to give an applicant the position's pay scale on reasonable request, and Nevada requires the wage or salary range for an applicant who has completed an interview. Have the number ready and consistent with the posting.
- No questions at all — explore it rather than reading it as disinterest; asking what they are still weighing tells you more than moving on.
This page is employer information, not legal advice. Interview-question rules come from EEOC guidance and from state and city statutes that differ and change; have employment counsel review your question script and exercise before you use them.
More hiring resources
Hiring a litigation support specialist?
Post the opening where litigation support specialists look for law firm jobs — the systems, the matters and the pay range up front.