Underwriter interview questions and how to answer them
An underwriting interview is really a test of how you think about a file you've never seen. Expect questions about declines, referrals and missing information, and expect at least one moment where they hand you a submission and watch you read it. Your credentials matter less here than showing you can say no clearly and write down why.
What happens in each round
- 1
Recruiter screen
What happens
Whether you know which kind of underwriting the role is (commercial, personal lines, life, or mortgage), whether your background lines up with it, and whether you can explain why you want a desk job built around reading and deciding.
- 2
Hiring manager interview
What happens
Your judgment on real situations: a broker pushing for a quote, a file that looks fine on paper but doesn't sit right, a decision you had to defend. They're listening for how you weigh risk, not for textbook definitions.
- 3
File review or case exercise
What happens
They give you a sample submission, a set of loss runs, or a borrower file and ask what you'd approve, decline, or ask for. They care about what you notice, what questions you raise, and whether you know what's missing before you price anything.
- 4
Panel with senior underwriters
What happens
Whether the people who'd review your referrals trust your notes and would enjoy working next to you. Expect questions on how you handle a heavy queue, how you take pushback, and how you learn guidelines.
Questions you're likely to get
1.Walk me through how you'd review a new commercial submission.
Why they ask
They want to see whether you have an order of operations or just react to whatever's on top of the file.
How to answer
- Start by checking appetite: is this class of business something the company writes at all
- Confirm the file is complete: application, loss runs, schedule of locations, financials if the account needs them
- Read the loss history for patterns, then the operations and any inspection report
- Decide whether it's inside your authority before you spend time pricing it
- Price it, set conditions, and write a note that says why
2.How do you read a set of loss runs, and what makes you stop?
Why they ask
Loss runs are the core document on the insurance side, and they want to know you can read them for a story rather than a total.
How to answer
- Separate frequency from severity: lots of small claims says something different from one big one
- Look for open claims and how much is still reserved on them
- Check whether the loss type ties back to the operations described in the application
- Ask what changed since the bad stretch: new safety program, new management, a location closed
3.A broker you've worked with for a long time wants a quote by end of day, and the loss runs are missing. What do you do?
Why they ask
This tests whether you'll bend guidelines for a relationship and how you handle pressure without burning the person on the other end.
How to answer
- Tell the broker plainly what's missing and why you need it
- Offer what you can do, such as an indication subject to loss runs, if your guidelines allow that
- Don't bind or issue a firm quote on a file you can't support
- Follow up in writing so the conversation is on the record
4.Tell me about a time you declined a risk or a loan that someone wanted approved.
Why they ask
Every underwriter has to say no to people who earn money on a yes. They want proof you've done it and handled the fallout.
How to answer
- Describe the file briefly and who wanted it approved
- Name the specific reason: the guideline, the red flag, the missing piece
- Explain how you told them and what, if anything, would have changed your answer
- Say what happened after, including whether the relationship held
5.The automated system approved a file, but something in it bothers you. What do you do?
Why they ask
On the mortgage side, Desktop Underwriter and Loan Product Advisor findings clear a lot of files, and personal lines have their own rules engines. They want someone who reads the file anyway.
How to answer
- Say the system's output depends on the data that went in, and bad data gets clean findings
- Give an example of what might bother you: income that doesn't match bank deposits, an address that doesn't match the inspection
- Condition the file or ask for documentation to settle the doubt
- Document what you saw and what you asked for
6.How do you decide when a file goes outside your authority and needs to be referred?
Why they ask
Working inside a letter of authority is a big part of the job. Referring too much slows the team down, and referring too little is a compliance problem.
How to answer
- Say you know your limits by limit, class and territory before you open a file
- Refer anything outside those lines, even if you'd approve it
- Send the referral with your recommendation already written, not just the file
- Treat the answer you get back as training for the next similar file
7.How do you write a file note that someone else can understand later?
Why they ask
Auditors, reinsurers, investors and your own manager read your notes long after you've moved on. A decision with no reasoning looks careless.
How to answer
- Lead with the decision and the terms
- State the main reasons in plain sentences, tied to specific documents
- Note any exception to guidelines and who approved it
- Keep it short enough that someone actually reads it
8.Your queue is backed up and the turn-time target is about to slip. How do you handle it?
Why they ask
Most underwriting desks run on volume targets. They want to know you'll triage instead of cutting corners across the board.
How to answer
- Sort by what's closest to a deadline or a closing date
- Clear the simple files quickly so the hard ones get real attention
- Tell your manager early if the math doesn't work, rather than on the day
- Keep the quality of your notes the same even on a rushed day
9.Which worries you more on a given account: frequency or severity?
Why they ask
It's a quick way to test whether you think about losses in shapes, and whether you tie your answer to the kind of business in front of you.
How to answer
- Say it depends on the line and the class, then commit to an example
- Frequency often points to a management or safety problem that can be fixed
- Severity can be one bad day, or a sign of exposure the pricing missed
- Explain what you'd ask the insured or broker in each case
10.Tell me about a mistake you made on a file.
Why they ask
Everyone misses something eventually. They want to see if you own it and changed your process.
How to answer
- Pick a real miss, not a disguised strength
- Say how it was caught and what it cost
- Describe the habit you built so it doesn't happen again
11.How do you keep up with guideline changes?
Why they ask
Guidelines, rating rules and investor requirements change often, and an underwriter working off an old version creates real problems.
How to answer
- Name how you actually get updates: bulletins, team meetings, the guideline portal
- Describe how you check the current version before a borderline decision
- Mention any study toward the CPCU or AU if you're working on one
12.Why underwriting instead of sales or claims?
Why they ask
They want to know you understand what the desk is like and actually want it, not just a job at an insurer or lender.
How to answer
- Say what draws you: deciding, reading the full picture, owning a call
- Show you know the trade-off, like less customer contact and a lot of reading
- Connect it to something you've done that felt the same way
Mistakes that sink good candidates
Talking about approvals as the goal, as if volume matters more than how the book performs
Complaining about brokers or loan officers you've worked with
Saying you'd trust the automated findings without reading the file
Giving a vague decline story with no specific reason behind it
Need more Underwriter interviews to prep for?
HeroApply applies to Underwriter jobs that match you, every day. 1,022 jobs are open today.