What should you ask a legal assistant in an interview? Questions and what good answers sound like

A question bank for law firms interviewing legal assistant candidates — real experience, judgment and confidentiality, a practical exercise, and the questions to keep off your list.

The questions to ask when hiring a legal assistant are the ones that surface the work a candidate personally ran — the documents they produced, the deadlines they tracked, the clients they calmed — plus how they handle confidentiality and the days when everything collides.

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

Build the questions from the job description, not from a generic list.

If the role itself is not settled yet — the mix of calendaring, correspondence, filings and client contact, who the hire supports, and how work gets reviewed — start with our guide to how to hire a legal assistant, then sharpen the questions once the legal assistant job description says what the hire will actually do.

The interview's job is to test the claims that posting makes.

Decide which mix your firm is hiring for and weight the questions toward it.

A legal assistant whose week is mostly filings, e-filing and deadline management is a different hire from one whose week is client correspondence and scheduling, and a strong calendaring answer and a strong client-care answer are not the same skill.

Pick the two or three duties that matter most in your office and probe those hardest.

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 the same 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.

If you require applicants to take a test, the EEOC's position is that it 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.

Design the exercise around a mock, disguised file rather than a live matter.

The FLSA defines "employ" to include "to suffer or permit to work" (29 U.S.C.

203(g)), so a candidate doing real, usable work for the firm — producing a document you actually send, for example — may be an employee owed wages; a short exercise on a mock file is the safer design.

Tell every candidate up front not to bring client-identifying detail from their current job into the room: ask about the kind of work, not the parties.

How a candidate handles that instruction is itself a data point.

Decide before the loop starts what you will verify after it: the work samples, the software claims, and which references you will actually call, so the reference checks can confirm the specifics the candidate named today.

Write your list against the risky-questions section below, and have employment counsel confirm the final version — these rules vary by state and they move.

Which skills questions reveal real legal assistant experience?

Walk me through one piece of work you personally ran end to end — a filing, a discovery set, a closing binder, a client intake. What did you do at each step?

What to listen for: Strong answers name the documents and the steps — what was prepared, what was filed and where, who reviewed it, what came back — and they separate the work they owned from the team's.

Pick one step and probe; real work gets more specific under pressure, while an inflated role gets vaguer.

What did you actually do inside the case-management and document systems at your last firm — not which ones you have used, what you did in them?

What to listen for: Strong candidates describe the workflow: entering calendar entries the day a date arrives, versioning drafts, keeping client records current, pulling what an attorney needs in minutes.

A list of software names with no tasks inside them is the finding — the tools are learnable, the habits are the hire.

Which documents have you prepared yourself, and what happened to them before they went out?

What to listen for: Strong answers name a range — correspondence, pleadings, discovery responses, bills, engagement letters — and describe the review step plainly: an attorney checked it, made changes, and signed or sent it.

A candidate who describes substantive work going out with no attorney review is telling you how they will work in your firm.

You want the instinct that preparation is theirs and the sign-off is not.

How did you keep court deadlines and internal dates straight? Walk me through the actual system.

What to listen for: An adjectives-only answer is the one to press hardest here.

Strong answers name the mechanics: a master calendar, the same-day entry of every new date, a reminder ahead of the deadline, a second check before anything is treated as filed.

Weak answers are adjectives — organized, detail-oriented — with no system anywhere in them.

What client contact did you handle — calls, updates, scheduling — and what did you do with a question you could not answer?

What to listen for: Strong answers show warmth plus an escalation reflex: take the question, take the message, get it to the attorney, close the loop with the client.

The dangerous answer is the helpful one — a candidate who improvised answers to legal questions at their last firm will do it at yours.

You are hiring the person who knows which questions are not theirs to answer.

Which behavioral questions test judgment, confidentiality and deadlines?

Tell me about a time someone outside the firm asked you about a client's matter — at a party, at another job, online. What did you say?

What to listen for: Strong answers decline without drama and confirm nothing, and they keep client identifiers out of the telling even now.

The dangerous answer is the entertaining one: a candidate who walks you through a former client's most sensitive details is showing you exactly how they will treat yours.

Score discretion above storytelling.

Two attorneys need you at the same moment — one has a filing due today, the other wants something now. What did you do the last time that happened?

What to listen for: Strong answers triage by consequence, tell both attorneys what is happening, and escalate the collision instead of silently picking.

Weak answers amount to "I just worked faster," with no system and nobody informed.

Ask what they changed about their calendar or their check-ins afterwards — the fix is the real answer.

Tell me about a time you realized a deadline was about to slip. What did you do next?

What to listen for: Strong answers flag it early, tell the attorney in time to do something about it, and change the process so it cannot repeat.

Weak answers insist it has never happened, or that they stayed late and saved it alone with nobody told.

A well-handled near-miss with a process fix is the strongest answer this question produces.

Walk me through the last time an upset client reached you directly and the attorney was unavailable. What did you say?

What to listen for: Strong answers stay calm, take the concern seriously, promise nothing about the case, get the message to the attorney, and follow up with the client so nobody feels dropped.

The two weak answers are the extremes: false reassurance the client will act on, or a coldness that loses the client.

The legal assistant may be the first person at the firm an upset client reaches — treat the answer as a front-desk audition.

Tell me about a mistake of yours that reached an attorney — or nearly did. What happened next?

What to listen for: Strong answers own it fast, fix it, say who they told, and name what changed in their process afterwards.

Weak answers blame a software export, a courier or the court — or cannot produce a single example.

A candidate with no mistakes to describe is describing a short memory, not a clean record; press gently and the follow-up tells you which.

What practical exercise or test should a legal assistant complete?

Proofread test: hand the candidate a short client letter with planted errors — a wrong date, a misspelled client name, a figure that does not match the enclosed document — and ask them to mark everything they would fix before it goes out.

What to listen for: Strong candidates catch the substantive errors — names, dates, numbers — and can say why each one matters, not just that it looked wrong.

Weak showings circle the typos and miss the client's name being wrong — the planted error with a real person's name attached to it.

Keep the same letter for every candidate so the comparisons mean something.

Calendar test: give the candidate a mock attorney note containing several dates — a filing deadline, a client call, an internal draft date — and ask them to enter each one in a blank calendar and describe how they would double-check themselves.

What to listen for: Strong candidates enter every date, set the reminder ahead of the deadline, confirm back what they recorded, and ask which dates are court-certain and which can move.

Weak candidates enter some of the dates and stop there, with no second check anywhere.

Watch how they handle the date that is ambiguous — asking is the strong move.

Writing test: from a short mock status note, have the candidate draft the client update email they would send.

What to listen for: Strong samples are short and plain, give the client a concrete next step, and promise nothing about how the case will come out.

Weak samples hedge in every sentence, drift into legal conclusions, or read like a form letter.

A legal assistant writes to clients all day in the firm's voice — this exercise shows you whose voice your firm is getting.

Organization test: hand the candidate a shuffled mock file — correspondence, a draft document, receipts, notes — and ask how they would organize it and what they would flag.

What to listen for: Strong candidates produce a usable order quickly, separate what is final from what is draft, and flag what seems missing rather than filing around it.

Weak candidates narrate the pile.

This is the closest a short exercise gets to the first week of the actual job.

What do strong vs weak answers sound like?

Deadlines: “The order came in Tuesday afternoon; I entered the response date the same day, set a reminder a week out, and emailed the attorney what I'd recorded” — strong. “I'm very organized and I've never missed a deadline” — weak.

What to listen for: The strong version has a system in it — same-day entry, a reminder, written confirmation — and specifics you can probe.

The weak version offers adjectives and perfection, which is hard to believe in a role built around dates; press once and the follow-up tells you which one you are hearing.

Confidentiality: “I told them I couldn't talk about anything at the firm, and changed the subject” — strong. A detailed story about a famous client's file, told with relish — 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: discretion is the core of the job for support staff, and a candidate who performs a former client's private file in your interview has told you how your files get performed somewhere else.

Client calls: “I told her I'd get the message to Mr. Lee that afternoon and made sure he called her before five” — strong. “I told her not to worry, these things always work out” — weak.

What to listen for: The strong answer does the three things a support role can do — receive, relay, close the loop — and promises nothing about the outcome.

The weak answer is the expensive one: the client hangs up reassured about something nobody at the firm actually said, and acts on it.

Listen for candidates who know reassurance is not in their job description.

Ownership: “I prepared the exhibit binder, but the associate caught two documents I'd put in the wrong order and fixed my checklist” — strong. “I handled discovery at my old firm” — weak.

What to listen for: The strong version contains personal doings you can verify with a reference call — documents prepared, entries made, corrections taken well — and honest edges where someone else's work began.

The weak version names a firm and a practice area with nothing checkable anywhere in it.

Every follow-up you ask tests which version you are hearing.

Which questions are illegal or risky to ask?

Interviews are part of the hiring process the anti-discrimination laws reach: protections enforced by the EEOC extend to job applicants and former employees, not just current staff.

Title VII, the ADA and GINA cover private employers with 15 or more employees who worked at least 20 calendar weeks in the current or prior year, and the ADEA's age protections cover private employers with 20 or more employees who worked at least 20 calendar weeks in the current or prior year.

State and local laws can reach smaller employers — that coverage was outside our research, so confirm what applies to your firm.

Read this section with the EEOC's own framing: federal law does not clearly forbid every pre-employment question touching race, sex, national origin, religion or age, but such questions can be used as evidence of intent to discriminate unless justified by a business purpose — treat them as risky, not as technicalities.

Have employment counsel confirm your final question list before the first interview.

  • Salary history — “What did you make at your last firm?” California bars all employers from seeking an applicant's salary history, including benefits, orally or in writing, and from relying on it in hiring or pay decisions; New York bars relying on it and requesting it as a condition of being interviewed, considered, hired or promoted, and permits confirming it only when an offer with compensation is on the table and the candidate responds by citing prior pay to support a higher number; Illinois makes it unlawful to screen applicants by salary history or request it as a condition of an interview or offer; Massachusetts bars seeking it from the candidate or a current or former employer; Connecticut bars asking about it unless the candidate volunteers it first; Virginia and Nevada bar seeking salary history as well. Those are the jurisdictions our research verified, not the full map — other states and cities have rules we did not read, so check yours. Ask “What are you looking for in pay for this role?” instead — California's statute expressly permits asking about salary expectations — and keep the posting's range consistent with the answer.
  • The candidate's life off the job — “Where are you really from?”, how many kids they have, who watches them when the office runs late, their church, their maiden name, what year they graduated high school. The EEOC's position is that pre-employment questions should be limited to what is essential to decide whether a person is qualified, and that questions about race, sex, national origin, age and religion are irrelevant to that decision; the EEOC also maintains separate guidance on pre-employment inquiries about marital status and number of children, religious affiliation and citizenship, among other topics. The friendly “fit” questions are the ones that drift here — swap each one for the job question you actually meant.
  • Medical questions before an offer — health conditions, past injuries, how many sick days they took last year. The FTC and EEOC's joint background-check guidance says employers should not ask medical questions before a conditional job offer; before an offer, keep questions on how the candidate would handle the job's actual demands — the filing volume, the deadlines, the occasional late evening.
  • Criminal history, asked casually. The same FTC and EEOC guidance says 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 it warns that a criminal-record exclusion that significantly disadvantages a protected group and does not predict job performance can be unlawful disparate impact. Where and when you may ask is also regulated: California bars employers with five or more employees from asking about conviction history until after a conditional offer, and an employer there that plans to deny the job over conviction history must make an individualized assessment, notify the applicant in writing, and give at least five business days to respond; New York City makes it unlawful for most employers to ask about or consider applicants' criminal history before a conditional offer; Illinois bars covered employers from asking until the applicant has been found qualified and selected for an interview — or, when there is no interview, until after a conditional offer. Those are the jurisdictions our research verified — state and city rules vary, so confirm yours before asking. For a support-staff hire, the job-related substitutes are the duties themselves: the reference checks and the work samples tell you about trustworthiness; the interrogation does not.
  • Tests and exercises without a job anchor. If you require a test, the EEOC's position is that it must be necessary and related to the job, and must not exclude people of a protected group or people with disabilities — and an applicant who needs an accommodation to apply for the job, such as a sign language interpreter, must be provided it unless it causes significant difficulty or expense. Every exercise on this page is anchored to a duty in the posting; keep yours that way too.
  • Anything you could not connect to a duty in the job description — age probes dressed as culture fit, questions about plans for children, religion, or where a candidate was born. If a question survives that test awkwardly, replace it with the job question you actually meant; the work itself gives you more than enough to ask about.

After the interview

Score every interview on the same sheet while the details are fresh: the skills answers, the behavioral answers, the exercise, and anything the candidate volunteered that you did not ask about.

Compare candidates against the rubric and the job description rather than against each other's polish, and write down the specifics you intend to verify — the documents they named, the software claims, the systems they described — so the reference checks have something concrete to confirm before you make an offer.

Keep what you wrote down.

The FTC and EEOC's joint 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.

The questions a legal assistant candidate asks you — and what they signal.

Leave real room at the end, because the questions are data too:

  • “How many attorneys would I support, and how is the work divided when everything lands at once?” — a candidate who knows the job's real shape. Have an honest answer about the actual workload, not the posting's version of it.
  • “Who reviews my work before it goes out?” — they know the review structure is the job. Your cue to be honest about how available the reviewing attorneys really are.
  • “What case-management and document systems do you run?” — practical thinking; they want to be usable fast. Name the actual stack, including whatever is clunky about it.
  • “What does the busiest month of the year look like here?” — they are weighing the job's real demands against their experience, the way you are. Answer it the same way.
  • “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 rules come from federal and state laws that change and vary by jurisdiction — confirm your question list, exercise, background-check process and pay-disclosure duties with employment counsel and the EEOC or your state fair-employment agency before the first interview.

More hiring resources

Ready to interview legal assistant candidates?

Post your opening where attorneys and legal staff look for law firm work.