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

A question bank for law firms interviewing senior associate candidates — file ownership, delegation and review, judgment and confidentiality, a practical exercise, and the questions to keep off your list.

The interview questions that matter for a senior associate hire are the ones that test what the level exists for: matters the hire runs day to day with little supervision — the calls they made, the work they delegated and reviewed, the clients they handled directly — plus how they handle confidentiality, deadlines and an unhappy client.

Below is the question bank: 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 you posted, not from a generic list.

If you have not settled the role itself — which matters may run without partner review, which clients the hire handles directly, whose work they review — start with our guide to how to hire a senior associate, then sharpen the questions once that is written down.

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

Weight the questions toward what the level is for.

You are hiring a lawyer to run files, not to learn on them, so the three things to test are file ownership (did they run the matter or watch it run), delegation and review (can they get work out of other people at a quality your firm can sign), and direct client handling.

Treat the partnership-track question as part of the interview too — a candidate moving at this level can weigh it before accepting, so have an honest answer ready.

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 fact pattern 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 — a draft of something you actually file, for example — may be an employee owed wages; a short exercise on a mock file 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 matter, not the parties.

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

And decide now how you will verify what the answers claim before you act on any of it — per the ABA, lawyers are licensed by a state agency in each state, and that agency can confirm whether a person has a law license and may practice there.

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

Which skills questions reveal real senior associate experience?

Walk me through a matter you personally ran day to day — the issue, the calls you made in it, and the work you delegated.

What to listen for: Strong answers name the kind of matter, the stage it reached, and separate what they decided from what the supervising partner decided: the strategy calls, the documents they drafted, the deadlines they owned.

They can go a level deeper on any step when you probe — a real file gets more specific under pressure.

A candidate who narrates the practice group instead of the file has not told you what they ran.

Which matters were you allowed to run without partner review, and which had to go up? Where was the line, and how did you know?

What to listen for: The line is the job.

Strong answers describe a concrete dividing line — dollar thresholds, client sensitivity, how novel the issue was — and one moment where the line was tested and they escalated, or should have.

A candidate who cannot describe the line at their last firm is asking you to let them invent one at yours.

How do you get work out of juniors and staff? Walk me through the last thing you handed off — the instructions you gave, and what you changed in the draft that came back.

What to listen for: Strong answers describe a system: a written scope, a deadline, a checkpoint before the work goes out, and feedback that teaches rather than only corrects.

They own the quality of what leaves under their review.

The weak answers are the two extremes: “it's faster to redo it myself” — no leverage, which is what the level exists to produce — or a war story about a junior's failure with no process anywhere in it.

Where are you admitted, and are you in good standing? And which parts of your practice could you carry into a new firm on day one?

What to listen for: Licensure standing is the job-related question for an attorney hire, and it is one you verify rather than take on faith: per the ABA, lawyers are licensed by a state agency in each state, and that agency can confirm whether a person has a law license and may practice there — run the check before any offer, not from the resume.

On portability, listen for an honest map of what carries straight over and what needs confirmation with the admitting authority where your firm practices — a candidate who says all of it transfers, everywhere, is telling you something.

Which clients do you deal with directly, and what do you handle without going back to the partner? Tell me about the last client request you settled on your own.

What to listen for: At this level the firm is buying direct client handling.

Strong answers name real relationships, the routine decisions they owned, and a recent example — plus the moment they looped the partner in, with a reason that makes sense: risk, relationship, scope.

The weak answers are either a senior title describing junior work (“the partner talks to all the clients”) or no example at all.

Which behavioral questions test judgment, confidentiality and deadlines?

Tell me about a time someone pushed you for details about a client's matter — at a gathering, online, in another firm's office. What did you say?

What to listen for: Strong answers decline without drama, confirm nothing, and 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 how they will treat yours.

Score discretion above storytelling.

Tell me about a time you disagreed with a supervising partner about how a matter should be run. What did you do?

What to listen for: Strong answers made the disagreement concrete and on the record — a written recommendation, a risk flagged early, an escalation that still respected the final call — and can describe what would have taken it further.

The weak answers are the two extremes: a bitter war story about a partner who never listened, or a claim they have never once disagreed.

At this level you are hiring the judgment to push and the judgment to lose gracefully.

Walk me through a week when several deadlines collided across matters you were running. What moved, and who did you tell?

What to listen for: Strong answers triage by consequence, warn the supervising partner early, and seek more time in time rather than miss in silence.

Weak answers amount to “I worked harder,” with no system and nobody told.

Ask what changed in their calendar process afterwards — the fix is the real answer.

Tell me about a time you caught a significant mistake in someone else's work — a junior's draft, a client's facts, the other side's papers. What did you do?

What to listen for: Strong answers fixed it, told whoever needed to know, and changed the process so it could not repeat — without hiding the error or grandstanding about it.

Blaming the junior and moving on is the weak answer; how their review worked is part of the story you are listening for.

Tell me about a client who was unhappy with you or the firm. What did you do, and what happened to the relationship?

What to listen for: Strong answers are honest about what went wrong, concrete about the fix, and promise nothing about outcomes — while staying human.

The weak answers are the extremes: blame shifted to the partner or the client, or a version so polished the relationship apparently never had a problem.

A senior associate who can hold an unhappy client is doing the job the level exists for.

What practical exercise or test should a senior associate complete?

Ask for a writing sample they personally drafted in the last year — a brief, a memo, a major agreement — with client details redacted before it reaches you.

What to listen for: A strong candidate produces one quickly and can walk through every choice in it: the issue framing, what was cut and why, the caveats, who the reader was.

Press on whether a partner rewrote it and what changed.

A weak showing is an old sample, a document someone else largely wrote, or one the candidate cannot discuss in detail.

Redaction is part of the exercise, not an excuse to skip it.

Run a delegation session: hand them a mock fact pattern and have them scope it into an assignment for a second-year associate — tasks, deadlines, checkpoints — then brief you as if you were the partner.

What to listen for: This is the senior-specific test.

Strong candidates split the work sensibly, name what they would keep themselves, put review points where mistakes are still cheap, and flag the questions only the partner should decide.

Weak candidates either hand off the whole thing or keep everything.

Keep the fact pattern disguised and mock — see the note above.

Run a mock first client meeting on a disguised fact pattern — you play the prospective client, the candidate leads.

What to listen for: Strong candidates ask the questions that sort the problem, lay out the realistic options and their risks in plain English, name what they would need to confirm before committing to an answer, and handle the fee question honestly — promising nothing about outcomes.

Weak candidates retreat into jargon, dodge the money question, or start guaranteeing results.

Give them a closed packet of mixed materials on a mock matter — some on point, some not — and ask for a one-page answer with a recommendation and what they would delegate from it.

What to listen for: Strong answers sort what actually applies from what merely looks applicable, state a recommendation with an honest edge (“this changes if…”), and mark which parts go to a junior.

It is judgment and delegation in one pass, and it is the closest proxy on this list for the daily work.

Keep it short and mock so it stays a sample of judgment rather than free work product.

Ask how they would run their first month: a mock docket of matters at different stages, handed over mid-stream from a departing associate.

What to listen for: Strong candidates triage by deadline and consequence, name what they would read first, which clients and files they would confirm early, and what they would escalate to the partner in week one.

Weak candidates narrate the list.

This is the file-running test, and it maps directly onto the desk you are hiring them to carry.

What do strong vs weak answers sound like?

File ownership: “I ran discovery in that case — I set the schedule, I took the depositions, and the partner saw my strategy memos before the client did” — strong. “I worked on complex litigation at a large firm” — weak.

What to listen for: The strong version contains work you can verify — schedules set, drafts written, people managed — and the candidate can go a level deeper on any of it when you probe.

The weak version describes a firm and a practice area, with no personal doings anywhere in it.

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

Confidentiality: “I can describe the kind of issue without the client” — strong. A war story with the client's industry, names and numbers attached — 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 file in your interview will talk about yours somewhere else.

Score charm lower than discretion.

Delegation: “I rewrote her summary judgment argument, then walked her through why, and her next draft needed only line edits” — strong. “Honestly, it's faster to just do it myself” — weak.

What to listen for: The strong answer shows leverage and teaching — the two things the level exists to produce.

The weak answer describes a busy senior lawyer with no bench behind them: your firm gains one pair of hands and loses the reason the level exists.

Judgment under pressure: “Two deadlines collided, so I flagged it to the partner a week out, we moved the deposition, and both filings went in on time” — strong. “I've never missed a deadline and never will” — weak.

What to listen for: The strong answer shows a system — early warnings, escalation to the supervising partner, a re-sequenced week — plus one specific save.

The weak answer offers perfection; press gently and the follow-up tells you which one it is.

The same test applies to “I've never disagreed with a partner.”

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.

A senior associate interview adds one trap of its own: graduation years can slip easily into conversation at this level, and a class year turns into an age with quick arithmetic — keep your questions on the files, not the years.

Have employment counsel confirm the final version before your 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 states 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 answer consistent with the range in your posting.
  • Protected-trait probes — “Where are you really from?”, comments on an accent, graduation or class years as an age proxy, religion, family plans, who watches their children. 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 pages on pre-employment inquiries about race, height and weight, financial information, unemployed status, religious affiliation, citizenship, and marital status or number of children. The job-related ground sits right next to the trap: admission and good standing, and the files a candidate has personally run, are legitimate to ask about and to verify — keep your questions there.
  • Medical questions before an offer — health conditions, past injuries, treatment. 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 — file loads, trial or deal calendars, travel.
  • 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, where 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. The job-related question for an attorney candidate is admission and standing, and the check you run with the state licensing agency beats the interrogation.
  • 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.
  • Anything you could not connect to a duty in the job description — if a question survives that test awkwardly, replace it with the job question you actually meant; the files themselves give 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 role you wrote down rather than against each other's polish, and write down the specifics you intend to verify — the matters named, the documents, the admission and standing.

Admission and standing are confirmed with the state licensing agency, not from the resume, and the matters named early in the process feed the conflicts run you want finished before an offer.

If the hire is a lateral, the conflicts run matters twice over — the candidate can arrive with prior-firm clients in tow.

ABA Model Rule 1.10(a) imputes a conflict under Rules 1.7 or 1.9 of any one lawyer in a firm to all the firm's lawyers, unless an exception applies; the exception that fits a lateral is Model Rule 1.10(a)(2): a former-client conflict from a prior firm is not imputed where the lawyer is timely screened from the matter and is apportioned no part of the fee.

States differ on whether they accept this kind of non-consensual screening — check your state's version of Rule 1.10 with your state bar's ethics counsel before you rely on it.

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 one year from the date the record was made or the personnel action taken, whichever is later — the guidance notes longer periods in some cases, for some federal contractors and where a charge is filed.

One more answer to have ready before the loop starts is the partnership track: what the path is, the criteria, who decides, and on what timeline.

A senior candidate's acceptance decision can turn on it, and a track described in the interview is a stronger promise than one added after it.

What a senior associate candidate asks you — and what it signals.

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

  • “Which matters would I run, and how much partner review is on them?” — a candidate testing whether the level you are selling is the level you mean. Have honest answers about which files run without review and which do not.
  • “Who would I be supervising, and how does review work here?” — signals they have run other people's work before, good or bad. It is your cue to describe the structure, not just the title.
  • “What is the path to partnership, and who decides?” — the question behind a senior-level move. Describe the criteria and the decision-maker plainly; vagueness reads as a no.
  • “How do you handle conflicts when a new matter sits close to a lateral's prior-firm work?” — conflicts awareness, and a fair question where the hire is a lateral. Know your process before the loop starts.
  • “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 senior associate candidates?

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