What should you ask an intellectual property attorney in an interview? Questions and what good answers sound like
A question bank for law firms interviewing intellectual property attorney candidates — patent prosecution, patent litigation and trademark or copyright work — with answer guides, a practical exercise, and the questions to keep off your list.
The patent attorney interview questions worth asking are the ones that pin down which side of intellectual property a candidate has actually practiced — patent prosecution, patent litigation, or trademark and copyright — plus the work they personally did and how they handle confidentiality, deadlines and technical detail.
Below is that question bank for your firm: what each question reveals, what strong answers sound like, one 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, start with how to hire an intellectual property attorney, then sharpen the questions once the intellectual property attorney job description says what the hire will actually do.
Decide which lane you are hiring for before you pick the questions.
Patent prosecution, patent litigation and trademark or copyright practice are different jobs with different proof.
If a candidate presents all three evenly, treat that as your cue to probe until one lane shows verifiable work of their own.
The role's lane is also where credential questions belong: registration to practice before the USPTO requires passing the USPTO's registration exam — the patent bar — unless the exam is waived, and the USPTO qualifies applicants technically before they sit, through a degree in a listed technical subject, a technical coursework route, the Fundamentals of Engineering test plus a bachelor's degree, or a category limited to design patent practice.
A law degree is not what the USPTO requires to sit: passers who are not attorneys in good standing are registered as patent agents, not patent attorneys.
So if you would consider a patent agent for the seat, say so now; if the seat must be a licensed attorney, the license question stands on its own in the interview.
Decide two more 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.
Tell every candidate up front that they should not share client-confidential detail in the room: ask about the kind of work, not the parties or the invention.
Unpublished applications and clients' trade secrets are the ordinary material of IP work, so the instruction protects everyone — and how a candidate handles it is itself a data point.
Finally, 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 intellectual property attorney experience?
Which side of IP have you actually practiced — patent prosecution, patent litigation, or trademark and copyright — and what did you personally do in each?
What to listen for: Strong answers lead with one primary lane and put verifiable work inside it — applications drafted, office-action responses written, briefs argued, clearance opinions delivered — before touching the others.
Weak answers spread evenly across all three with nothing you could check.
Spend your follow-ups on the lane the seat actually is.
Walk me through one matter you owned end to end. What did you draft, file or argue, and what did the rest of the team do?
What to listen for: A strong answer separates the candidate's own work product — the claims drafted, the responses to an examiner's rejections, the arguments made — from what the team produced, and gets more specific when you probe one detail.
A weak answer stays at the level of the practice area: “patent work for tech clients,” with no document you could ask to see.
Are you registered to practice before the USPTO — and where are you admitted to practice law? Is anything pending or limiting that we should know about before we verify?
What to listen for: A strong answer is direct on both: the state or states of admission, the USPTO registration, and anything in motion, offered without prompting.
If they qualified for the registration exam, ask which route they used — a listed technical degree, the coursework route, the engineering-exam route, or the design-patent-only category.
Evasion about status or dates is its own finding.
Treat every credential answer as a claim to verify before you rely on any of it: the licensing agency in each state can confirm whether a person has a law license and may practice there.
What is the most technical invention you have had to learn quickly, and how did you get fluent enough to write or argue it?
What to listen for: Strong answers describe a method — reading the prior art, interviewing the inventor until they could restate the invention, checking their own understanding — and admit where the ramp was hard.
Weak answers claim instant fluency in everything.
Hold the answer against the technical fields your clients actually come from and decide day-one fit versus trainable on purpose.
How do you decide what belongs in a client report or opinion versus what stays in your working notes?
What to listen for: You are testing written judgment on matters where the document is the work product.
Strong answers talk about audience, certainty and what a reader could rely on, and keep speculation out of the deliverable.
Weak answers have never thought about the difference.
Ask for a redacted writing sample from the last year as the follow-up — the practical-exercise section below shows how.
Which behavioral questions test judgment, confidentiality and deadlines?
Tell me about a time someone pushed you to discuss a client's unpublished application or trade secret — at a conference, online, in a social setting. What did you say?
What to listen for: Strong answers decline without drama, confirm nothing, and keep the client and the technology out of the telling.
The dangerous answer is the entertaining one: a candidate who walks you through a former client's secret invention to impress you is showing you how they will treat yours.
Score discretion above storytelling every time.
Tell me about a time a client wanted to file or assert something you believed the invention or the evidence did not support. What did you do?
What to listen for: Strong answers lay out the options and consequences, put the recommendation in writing where it mattered, and let the client decide with a record.
Weak answers either went along quietly or argued without ever reducing the advice to writing.
You are listening for advice as a process, not confidence as a personality.
Walk me through a week when a filing deadline, an examiner's response window and another client's demands all collided. What moved, and who did you tell?
What to listen for: Strong answers triage by consequence, escalate to the supervising attorney early, use the docketing system rather than memory, and seek an extension in time rather than miss the date.
Weak answers amount to “I worked harder,” with no system and no one told.
Ask what changed in their process afterwards — the fix is the real answer.
Tell me about a filing or docketing mistake that happened on your watch. What did you do next?
What to listen for: Strong answers own it fast, fix it, tell whoever needed to know, and change the process so it cannot repeat.
Weak answers blame a paralegal, a vendor or the system — or insist it has never happened.
A candidate who can describe a well-handled mistake is safer than one with no mistakes at all.
You would join from your current firm, and a new matter lands close to work you did there. What happens next?
What to listen for: Strong answers flag it immediately and hand it to your conflicts process — they do not self-clear, and they do not start work while the question is open.
It is worth knowing your own machinery before you ask: the ABA's Model Rule 1.10(a)(2) provides that a lateral lawyer's former-client conflict from a prior firm is not imputed to the new firm if, among other conditions, the lawyer is timely screened and takes no part of that matter's fee and the affected former client is promptly given written notice.
State versions of Rule 1.10 differ, and our research did not verify which states accept non-consensual screening — confirm yours with your state bar's ethics counsel before you promise a screen.
What practical exercise or test should an intellectual property attorney complete?
Ask for a writing sample they personally drafted in the last year — an office-action response, a claim set, a brief or an opinion letter — 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, the claim scope, what was cut and why.
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.
Give a short, timed exercise on a disguised fact pattern: a mock inventor disclosure, with a written issue list and a claim outline due back.
What to listen for: Strong submissions spot the real scope and prior-art issues rather than the obvious ones, structure the answer before writing, hedge where the facts are thin, and land on a recommendation.
Weak submissions summarize what the inventor said without turning it into claims or issues.
Keep the exercise identical for every candidate so the comparisons mean something.
For a litigation lane: hand them a redacted brief or motion from one of your own filed matters and ask for a critique.
What to listen for: Strong candidates read the posture correctly, name the evidence gaps and the argument the drafter dodged, and say what they would have done differently.
Weak candidates compliment the writing without engaging the strategy.
One conversation over a real filing beats another round of questions.
Run a mock client or inventor call: a short scenario, you play the client, the candidate leads.
What to listen for: Strong candidates explain scope and options in plain English, give concrete next steps, answer cost and timeline questions honestly, and promise nothing about outcomes.
Weak candidates retreat into jargon, dodge the fees question, or start guaranteeing allowances.
For client-facing seats this exercise outweighs the rest of the interview.
Whatever you choose: keep it short, keep it on a mock file, and score it the same way for everyone.
What to listen for: The design rules are legal, not stylistic.
The EEOC's position is that a required test must be necessary and related to the job and may not exclude people of a protected group or people with disabilities — and an applicant with a disability who needs an accommodation to apply for the job — a sign language interpreter is the EEOC's example — must be given one unless it causes significant difficulty or expense.
Keep the work on a mock file rather than your real matters: under the FLSA's definition of employ, a candidate producing real, usable work for the firm may be an employee owed wages, and a short exercise on invented facts is the safer design.
Have employment counsel bless the format once, then reuse it.
What do strong vs weak answers sound like?
Ownership: “I drafted the claims and wrote the response that got the application allowed” — strong. “I worked on a lot of patent filings” — weak.
What to listen for: The strong version contains work you can verify — documents drafted, arguments made, deadlines owned, outcomes — and the candidate can go a level deeper on any piece of it when you probe.
The weak version describes a practice area, a firm or a team, with no personal doings anywhere in it.
Every follow-up you ask tests which version you are hearing.
Confidentiality: “I can describe the process, but that application is unpublished and the client's — what specifically do you want to know?” — strong. A guided tour of a well-known client's invention — weak, and disqualifying.
What to listen for: The strong answer protects the client and describes the behavior, not the story.
The weak answer is entertaining, which is exactly the problem: discretion scored lower than storytelling in your room will score lower than storytelling somewhere else, with your clients' technology as the material.
Technical honesty: “That was outside my field, so I interviewed the inventor until I could restate it and flagged what I had not checked” — strong. “I can learn any technology overnight” — weak.
What to listen for: The strong answer pairs a learning method with honest limits — which is what you want in someone whose written statements to an examiner or a court carry the client's case.
The weak answer offers effortless fluency; press gently on one technical detail and the difference tells you which one you are interviewing.
Deadlines: “I flagged the collision a week out, we moved the inventor interview and I told the partner” — strong. “I have never missed a deadline” — weak.
What to listen for: The strong answer shows a system — docketing, early warnings, escalation — plus one specific save.
The weak answer offers perfection, which a real docket makes hard to believe; press gently and the follow-up tells you which one it is.
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.
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 or religion are irrelevant to that decision.
Framing matters: federal law does not clearly forbid every pre-employment question touching those traits, but the answers can be used as evidence of intent to discriminate unless the question is justified by a business purpose — so treat them as risky questions rather than assuming a statute bans each one.
The EEOC publishes separate guidance on inquiries about race, height and weight, financial information, unemployed status, religious affiliation, citizenship, and marital status or number of children.
The flags below are the areas to stay off in an intellectual property attorney interview, with what to ask instead — and employment counsel should confirm the final list before your first interview.
- Salary history — “What did you make at your last firm?” California's Labor Code 432.3 bars all employers, any size, from seeking an applicant's salary history, including benefits, orally or in writing, personally or through an agent, and from relying on it in deciding whether to hire or what to pay. New York Labor Law 194-a bars relying on wage or salary history and requesting it as a condition of being interviewed, considered, hired or promoted, or getting it from a current or former employer — and New York permits confirming history only after an offer with compensation is made and the candidate responds by citing prior pay to support a higher number. Illinois 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 bars seeking a prospective employee's wage or salary history from the candidate or a current or former employer, confirmable only after voluntary disclosure or after an offer with compensation. Connecticut bars asking about wage and salary history unless the applicant volunteers it, Virginia bans seeking salary history, and Nevada bans it too. Those are the states our research verified, not the full map — many cities and other states have their own rules we did not read, so check yours. Ask “What are you looking for in pay for this role?” instead: California expressly allows the salary-expectation question, and California lets you consider salary history the candidate volunteers without prompting.
- Medical questions before an offer — health conditions, past injuries, medications. 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.
- Questions about who the candidate is rather than the work — age probes such as graduation years, where they are “really from,” religion, family plans, who watches their children. The EEOC's guidance calls questions about race, sex, national origin, age and religion irrelevant to whether a person is qualified, and without a business purpose the answers to inquiries touching those traits can become evidence of discriminatory intent. Ask about the schedule, the travel and the docket the seat involves instead.
- 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, with 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 its own map: California's Fair Chance Act bars employers with five or more employees from asking about conviction history until after a conditional offer, and if you then plan to deny the job over it, California requires an individualized assessment, written notice and at least five business days to respond first. 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 bars covered employers from asking until the applicant has been found qualified and notified they are selected for an interview — or, with no interview, until after a conditional offer. We did not research the full state and city map, so confirm your jurisdiction before the interview.
- Anything you could not connect to a duty in the job description — if a question survives the business-purpose 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 — matters, documents, state bar standing, USPTO registration — so the next round of diligence has something concrete to check.
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 — and some situations run longer, for instance for some federal contractors or once a charge is filed.
The questions an intellectual property attorney candidate asks you — and what they signal.
Leave real room at the end, because the questions are data too:
- “What does the mix of prosecution and litigation work look like for this seat?” — a candidate mapping the job to the lane they want to build in. Have the honest answer ready, including where the seat could drift.
- “What technical fields do your clients come from?” — technical-fit awareness, and a fair question. Know your client base before you interview anyone, because the wrong technical match wastes the hire and the year.
- “Who reviews my work, and how does the firm run conflicts?” — signals they have worked under supervision and through a lateral screening before. It is your cue to be honest about partner access and your conflicts process.
- “What is the pay range for this role?” — a reasonable question and, in places, one with a legal answer behind it: California requires an employer to give an applicant the position's pay scale on reasonable request regardless of firm size, and Nevada requires the wage or salary range once an applicant has completed an interview. Have the range 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 design, background-check process and pay-disclosure duties with employment counsel and your state fair-employment or labor agency before the first interview.
More hiring resources
Ready to interview intellectual property attorney candidates?
Post your opening where attorneys and legal staff look for law firm work.