Paralegal Interview Questions

"I started as a receptionist at a small litigation firm while I was finishing my degree. Within a few months the paralegals were asking me to help index files and pull records, and I found I really liked it, because a messy box of documents turned into something the attorney could actually use. I then did a paralegal certificate and moved into a junior role handling discovery and court filings. What I enjoy most is being the person who knows where everything is and what's due next. I want to stay in litigation and take on more research and drafting, which is why this role appealed to me."

"From your website and the recent cases I could find, most of your work is employment disputes for mid-sized companies, with a good share of it settling before trial. To me that means a lot of document-heavy discovery, witness interviews with current and former staff, and tight deadlines around mediation. I've spent two years on discovery and deposition prep, so that side is familiar. What draws me to employment work is that the facts are human. It's about what people said and did at work, and getting the timeline right really matters. I'd like to build real depth in one area instead of doing a bit of everything."

"My strongest area is organisation and deadlines. In my last role I kept the calendar for three attorneys and nothing slipped in over a year, partly because I always had a second person check new court dates. I'm also careful with documents; I proofread against the source, not from memory. Where I'm still building is legal research. I can find cases and statutes, but I'm slower than I'd like at judging which authority is strongest. So I've been doing short research tasks for one of the associates and asking her to mark up what I missed. I'd rather be honest about that than overpromise on day one."

"I sign up for the update notices from the courts we file in most, because local rule and filing changes are the ones that catch people out. I'm a member of a local paralegal association, and I go to their short sessions when the topic is relevant to my work, like e-filing changes or e-discovery. I also take any training the firm offers on its software. Recently a court we use changed its e-filing requirements for exhibits, and I updated our filing checklist and let the team know before anyone's filing got bounced. I set aside a little time each week for this, otherwise it never happens."

"It was the week before a trial started. I had exhibit binders and the witness list due to the court on Wednesday, a production due in another case on Thursday, and a partner asking for a medical records summary. On Monday morning I listed everything with its real deadline and who owned it. Court filings came first because those dates don't move. I told the partner straight away that the summary would be Friday, not Tuesday, and asked if that worked; it did. I got a colleague to do the second check on the production so I wasn't proofing my own work at midnight. Everything went out on time. What I learned was to raise a clash on Monday, not Thursday."

"When my last firm moved to a new document review platform, I was put on a review project in the first week, before the formal training had even been scheduled. I asked the vendor's support team for a short walkthrough, then practised on a test set so I wasn't learning on live documents. I made a one-page cheat sheet for coding documents, running searches and exporting, and checked it with the senior paralegal. By the second week I was coding at a normal pace, and I shared the cheat sheet with two contract reviewers who joined later. The main thing I learned was to test on dummy data before touching client files."

"I use the same structure on every matter, following whatever the firm's standard is, so pleadings, correspondence, discovery, evidence, research and billing each have their own place. I name files consistently, with the date first so they sort in order, then the document type and who it's from, and I mark final versions clearly so nobody works from an old draft. I keep a pleadings index and a key dates list at the top of the file, and I update them the day something comes in. The real test is whether someone covering for me can find the latest filed version of a motion in under a minute. If they'd need to call me, the file isn't set up properly."

"We were about to file a motion, and my last step is always to check every date, name and case number against the court's own docket rather than our file. The caption had the right parties, but the case number was from a related case the same client had in the same court. It had been carried over from an older template. I flagged it to the associate with a screenshot of the docket, we fixed it, and I checked the exhibits for the same error, where it had also crept in once. Afterwards I suggested we stop reusing old filings as templates and keep clean blank versions instead, and the team adopted that."

"I'd start by reading the complaint, the answer and any orders, so I know the parties, the claims and anything the court has already limited. I'd ask the attorney what they most want from this request, because a template covers everything and a good request is targeted. Then I'd check the court's rules and the judge's standing orders for things like page limits, formatting and caps on the number of requests. When I draft, I tailor every request to our facts, delete what doesn't fit, and fix definitions so they match our parties. I'd send it with notes in the margin on anything I wasn't sure of, so the attorney can review it quickly rather than hunting for problems."

"An expert disclosure date had been moved by a court order, and the order came in while the docketing clerk was on leave. It went into the file but not the calendar. I caught it about four days out, only because I read every new order on my matters when it arrives, not just the ones flagged to me. I told the associate at once, and we got the expert report finished in time, but it was a scramble. The change I pushed for was simple: any new court order gets logged in the calendar the same day by whoever opens it, and a second person confirms the entry. We haven't had a gap like that since."

"I'd go back to the source first: the document that started the clock, the rule that sets the period, any court order that changes it, and the counting rules, like whether weekends count or extra days apply for how it was served. If I still get a different date, I'd treat the earlier of the two as the real deadline until a lawyer confirms. Then I'd send the attorney a short, clear note they can read at a break: two dates, why they differ, and what I recommend. If I can't reach them, I'd go to another attorney on the case or the supervising partner. Once it's decided, I'd fix the calendar and add a note explaining the calculation."

"First I identify the triggering event, like service of a complaint or entry of an order, and the date it happened. Then I find the rule that sets the period, and check whether a court order, local rule or the judge's own procedures change it. Next I count using that court's method. Most rules leave out the trigger day, but they differ on whether short periods skip weekends, what happens when the last day lands on a weekend or holiday, and whether extra days are added for how the document was served. If I'm counting backwards from a hearing, a weekend usually moves the deadline earlier, not later. I enter the deadline in the docketing system with reminders well ahead, and I note the rule and trigger with it. Then someone else checks my calculation independently. If rules-based calendaring software is used, I still sanity-check what it produces."

"We had a client in a personal injury case who had been through two firms already and was angry about being asked the same questions again. I started by saying I'd read the notes from the previous firm, so I'd only ask about the gaps, and that I'm a paralegal working with the attorney, not the attorney. That seemed to calm things down. I let her tell the story her way first, then went back for dates, names and documents. At the end I read the key points back to her, and she corrected two dates, which mattered for the timeline. I wrote it up the same day and flagged the corrections for the attorney."

"In the room I'd keep the same tone I had before, because a reaction can make a witness start guessing what I want to hear. I'd ask the normal follow-ups: when it happened, who else was there, whether there are emails or notes about it. I'd write down their words as close to exactly as I can. I would never suggest they might be remembering it wrong or that it would help to put it another way; that's shaping evidence. Afterwards I'd tell the attorney that day, before anything else, and put it clearly in the summary, not buried on page six. Bad facts found early are far easier for the attorney to deal with."

"One partner needed a filing assembled for a same-day court deadline, and an associate needed exhibits for a client meeting at three. Both said urgent. I checked the actual deadlines: the filing had to be in by the court's cut-off, which couldn't move, and the meeting exhibits were needed, but the associate could live with a draft set. I told the associate right away what I could do and when, and I asked another paralegal to pull the exhibits while I finished the filing. Both got what they needed. Now, when I support several attorneys, I keep one shared list of what's due for each of them, so priorities are visible and nobody's surprised."

"Early on I gave an associate a summary of a long deposition, and she told me it was basically a shorter transcript. She needed to know which answers helped us, which hurt us, and where the witness contradicted earlier documents. I asked if she had an example of a summary she liked, and she sent me one. I rewrote mine with sections by topic, page and line references for every point, and a short list of inconsistencies at the top. She used that version in her motion. Since then I always ask one question before I start a summary: what will you use this for? It saves a lot of rewriting."

"For me it works best when they can hand something over and stop thinking about it, because they trust it'll come back right and on time, or I'll warn them early if it won't. What I need in return is fairly simple: what the task is, when it's actually due, and what they'll use it for, because that last part changes how I do it. I like to confirm an instruction back in one line if it's complicated. I also try not to interrupt with every small question. I save them up unless something's urgent. Over time I learn each attorney's preferences, like how one wants summaries and another wants full detail."

"I'd tell them it's a really important decision and I want them to have the attorney's advice on it, because giving legal advice isn't something I'm allowed to do as a paralegal. Then I'd make sure I have what the attorney needs: what their questions or worries are, whether the offer has a deadline, and the best time and number to reach them. If the offer expires soon, I'd contact the attorney straight away, even if they're in court, by whatever route the firm uses for urgent messages. And I'd tell the client when they can expect a call, then check it actually happened. What I wouldn't do is give even a hint of my own opinion."

"First, I'd tell the supervising attorney straight away, in person or by phone, not by a quiet email. I'd give them the exact document, who got it and the time it went. If our email system allows a recall I'd try it, but I wouldn't assume it worked. It's then the attorney's call how to contact opposing counsel and ask for the document to be returned or destroyed, and whether a clawback clause in a protective order or the court's rules applies. Speed matters, because acting promptly is often part of what decides whether the privilege survives. I'd write down the timeline while it's fresh. Afterwards I'd turn off address autocomplete for opposing counsel and double-check recipients on anything sensitive."

"I'd say it respectfully but clearly: I'm not comfortable putting a date on the letter that isn't true, because if anyone relies on that date it could be misleading, and it could come back on the attorney and the firm. Then I'd offer a way through. We date it today, and the letter itself can say that it confirms what was agreed on the phone last week, if that's what happened. Most of the time that solves the real problem. If the attorney still insisted, I'd raise it with the supervising partner or whoever handles ethics questions at the firm, and I'd keep a short note of the conversation. I'd rather have an awkward talk than put my name to a false record."

"I'd keep it light but firm: 'Sorry, I can't talk about anything to do with work cases, even the ones in the news.' I wouldn't confirm whether I'm working on it, or share small details like how the team feels or what the client is like, because small details add up and they travel. If they're curious, I'd say whatever's in the news is public, and that's all I can add. Then I'd move the conversation on. Confidentiality covers far more than the legal strategy; it covers pretty much everything I learn about a client through my work, and it doesn't switch off when I leave the office."

"A paralegal does real legal work under an attorney's supervision: research, first drafts of documents for review, managing files and deadlines, discovery, and interviewing clients and witnesses to gather facts. What I can't do is practise law. That means I don't give legal advice, agree to take on a client, set fees, sign court papers or represent a client in court. The exact line depends on where you work, since some places let trained paralegals do more on their own, so I follow the local rules and the firm's policy. Day to day the line is simple: I can gather facts and pass on information, like a hearing date or what a form asks for, but deciding what the client should do is always the attorney's call. I also make sure people know I'm not a lawyer, and I flag anything I'm unsure of, because the attorney is responsible for my work."

"A conflict check makes sure the firm can take on a new matter without a clash with another client, current or former, for example acting against someone we already represent. To run it properly I need the full names of the prospective client and any related entities, like parent companies and subsidiaries, all the adverse parties and their related companies, and often other key people such as co-defendants or insurers. I'd include former names and trading names, because a search is only as good as the names you put in. I run them through the firm's conflicts database and pass any hits to the attorney or conflicts team to decide. It should happen before we take detailed confidential information or do any work."

"Attorney-client privilege protects confidential communications between the client and their lawyer made to get or give legal advice. It lets us refuse to hand those over, but it can be lost, for example if the client shares the advice with an outsider. Work product protection covers material prepared because litigation was expected, like an attorney's notes or my witness summaries done at their direction. It's usually a qualified protection: the other side can sometimes get factual material if they show real need, while the attorney's opinions and strategy get the strongest protection. The duty of confidentiality is the broadest of the three. It's an ethical duty not to reveal information about the client's matter, including things that aren't privileged at all, and in many places even things that are already public. It's about what I say, not what we can withhold in discovery. The exact names and scope change between countries, so I'd check the local rules."

"I'd tell the attorney the same hour, with a rough size and what it means for tomorrow. Then I'd get the files loaded and processed quickly, run deduplication against what's already been reviewed, and apply our search terms to get a sense of how much is actually relevant and how much might be privileged. That gives the attorney real numbers to decide on: produce the original set on time and supplement the new batch shortly after, or ask the other side for a short extension. What I wouldn't do is rush the new documents out without a privilege check just to meet the date. I'd also ask the client whether anything else is still out there."

"A litigation hold is a written instruction telling people and systems to keep information that might be relevant to a dispute, and to stop anything that would normally delete it, like email auto-deletion or recycling old laptops. The duty to preserve usually starts when litigation is reasonably anticipated, which can be well before anything is filed, for example when a demand letter arrives. My part is practical: helping the attorney list the custodians and data sources, sending the notice, tracking who has acknowledged it, chasing those who haven't, and working with IT so automatic deletion is paused. I'd send reminders, add new custodians as the case develops, and keep a record of all of it, because we may need to show later what we did."

"I'd describe it as a pipeline. First you identify where relevant information lives, like email, shared drives, phones and chat tools, and you preserve it so nothing gets deleted. Then you collect it in a way that keeps the metadata intact, so nobody can say it was altered. Processing turns that raw data into something reviewable: it pulls out text and metadata, removes duplicates and often threads emails together. Review is where people, sometimes helped by technology-assisted review, mark each document as relevant, privileged, confidential and so on. Then the team analyses what the documents show, produces the non-privileged responsive ones in the format agreed with the other side, and finally uses them in depositions, motions or at trial."

"A privilege log lists each document we're withholding or redacting on privilege grounds, so the other side and the court can assess the claim. Typically that's the date, the author, all recipients, the type of document, a description of the subject matter, and which protection we're claiming, like attorney-client privilege or work product. The hard part is the description. Something like 'email from in-house counsel to the finance director requesting legal advice on contract termination' works; 'legal advice' on its own doesn't. Vague entries invite a challenge, and a court may order the documents shown to the judge or even produced. I also mark which recipients are lawyers, and check that everything withheld from the production appears in the log, and nothing extra."

"I'd start from the review: only documents coded responsive and cleared for privilege go in the set. I'd check the format agreed with the other side, for example native files for spreadsheets and images for the rest, plus the load files and metadata fields. Each page, or each native file, gets a unique Bates number with our prefix, running in sequence from where the last production stopped, and documents covered by a protective order get the right confidentiality label. Before it goes out I run checks: no privileged documents slipped in, redactions are actually burned in rather than just drawn on top, no gaps or duplicates in the numbers, and a spot check of the output. Then I log the Bates range and date, and draft the cover letter for the attorney."

"First I'd make sure I understand the exact question and which jurisdiction and court we're in, because that decides which authorities are binding. If I'm new to the area, I'd start with secondary sources, like a practice guide or treatise, to understand the basics and pick up the key statutes and leading cases. Then I'd go to the primary law itself: the statute or regulation, and the cases interpreting it, starting with courts whose decisions bind ours. I'd check each authority is still good law. I'd write it up briefly: the question, the short answer, the key authorities with citations, and anything that cuts the other way or that I wasn't sure about. And I'd keep a note of my search path so it can be retraced."

"I run every case through a citator in whichever research service the firm uses. That shows me the case's later history, like whether it was reversed on appeal, and how later courts have treated it, whether they've followed it, distinguished it or overruled it. A warning flag isn't the end of the story, so I read the later case to see whether it affects the exact point we're relying on. For statutes and regulations, I check we're quoting the current version, and whether the version in force at the time of our facts was different. Finally I check every quotation and page reference against the original, because a wrong pin cite is an easy way to lose a judge's trust."