Underwriter Interview Questions (2026) and How to Answer

Behavioural questions (1–10)

How you've handled real situations. Answer each with one true story, in STAR order.

1. 1.Tell me about a file you declined that others thought should be approved.

   What they're really asking: Can you hold a risk decision under pressure from colleagues or sales?

   Answer outline (STAR)

   • SituationA deal that looked attractive on the surface but carried a risk others minimized.
   • TaskMake the right call, not just the popular one.
   • ActionDocumented the specific risk, compared it against guidelines, explained the decision in writing.
   • ResultWhat happened to the file afterward, and whether the decision was later validated.

   Full sample answer (fictional example)

   A broker brought me a commercial loan file with strong revenue numbers but a thin operating history, under fourteen months. The loan officer wanted to approve it based on the revenue trend alone. I documented the specific concern: no full seasonal cycle to verify whether the revenue was stable or a short-term spike. I declined, with a note that we'd reconsider after another two quarters of data. Six months later the business's revenue had dropped by about 30 percent in its off-season, which confirmed the concern. The loan officer later told me the decline had been the right call.

2. 2.Tell me about a time you approved a borderline file and it worked out well.

   What they're really asking: Can you take a calculated risk inside guidelines, not just decline anything unclear?

   Answer outline (STAR)

   • SituationA file outside the typical profile but with compensating factors.
   • TaskFind a way to approve it responsibly.
   • ActionIdentified the compensating factors, documented the exception rationale, added conditions.
   • ResultThe outcome of the file, and what it taught you about reading compensating factors.

   Full sample answer (fictional example)

   An applicant had a debt-to-income ratio slightly above our standard threshold, which usually meant a decline. But they had eighteen months of consistent on-time rent payments at a higher amount than the proposed payment, and a stable job history of over six years. I documented those as compensating factors, added a condition requiring proof of a small emergency reserve, and approved it. The file performed well, with no missed payments in the two years I tracked it afterward. It reinforced for me that strong payment history can offset a ratio that's only marginally outside range.

3. 3.Describe a time you had to deliver a decline to a broker or loan officer who disagreed strongly.

   What they're really asking: Can you hold a line while keeping a working relationship intact?

   Answer outline (STAR)

   • SituationA broker pushing hard for an exception on a file that didn't qualify.
   • TaskExplain the decision clearly without damaging the relationship.
   • ActionWalked through the specific guideline and the risk it addressed, offered alternatives where possible.
   • ResultHow the broker responded, and whether they continued sending you business.

   Full sample answer (fictional example)

   A broker had a file she'd worked on for weeks and was confident would close. The applicant's collateral valuation came in well below the loan amount requested, which violated our loan-to-value guideline by a meaningful margin. She pushed back hard, arguing the appraisal undervalued the property. I walked her through the specific guideline, showed her the appraisal's comparable sales, and explained I couldn't approve without a new appraisal or a reduced loan amount. She was frustrated but respected that I'd shown my reasoning clearly. She ordered a second appraisal, which came back close to the first, and the file was restructured at a lower amount.

4. 4.Tell me about catching a problem in a file that others had missed.

   What they're really asking: Do you look past the surface documents for inconsistencies?

   Answer outline (STAR)

   • SituationA file that looked clean until you checked something others skipped.
   • TaskCatch it before approval, not after funding.
   • ActionCross-checked income documents against bank statements, found a discrepancy, asked for clarification.
   • ResultWhat the discrepancy turned out to mean, and the check you added to your process.

   Full sample answer (fictional example)

   I was reviewing a self-employed applicant's income documents and noticed the bank statement deposits didn't match the income stated on the tax return, off by about 22 percent. The loan processor hadn't flagged it since both documents individually looked complete. I asked the applicant for an explanation and additional documentation. It turned out a portion of deposits were loan proceeds from a business line of credit, not actual income, which had been double-counted. We adjusted the qualifying income down accordingly. I added a step to my own checklist to always reconcile deposits against stated income line by line before approval.

5. 5.Tell me about a high-volume period where you had to maintain quality under pressure.

   What they're really asking: Can you keep decisions consistent when volume spikes?

   Answer outline (STAR)

   • SituationA surge in file volume with the same turnaround expectations.
   • TaskGet through the volume without lowering the bar on any file.
   • ActionPrioritized by deadline and risk level, used checklists to stay consistent, flagged anything rushed.
   • ResultThe volume cleared, and the error rate you maintained despite the pace.

6. 6.Tell me about a time you had to revise your own earlier decision.

   What they're really asking: Can you admit when new information should change your call?

   Answer outline (STAR)

   • SituationA file you'd approved or declined where later information changed the picture.
   • TaskCorrect the decision properly, not just quietly.
   • ActionReviewed the new information against the original reasoning, updated the file formally.
   • ResultThe outcome of the revised decision, and what you learned about your original process.

7. 7.Tell me about training or mentoring a newer underwriter.

   What they're really asking: Do you help raise the consistency of decisions across the team?

   Answer outline (STAR)

   • SituationA newer colleague making inconsistent calls on similar files.
   • TaskHelp them apply guidelines more consistently without just redoing their work.
   • ActionWalked through specific files together, explained the reasoning behind each guideline.
   • ResultThe change in their decisions afterward, and what you learned from explaining your own process.

8. 8.Tell me about a time you identified a pattern of risk across multiple files.

   What they're really asking: Can you see beyond individual files to a systemic issue?

   Answer outline (STAR)

   • SituationSeveral files from the same source showing a similar questionable pattern.
   • TaskDetermine if it was a real pattern worth escalating.
   • ActionPulled the files together, compared the common factor, brought it to a supervisor with evidence.
   • ResultWhat the investigation found, and the policy or process change that followed.

9. 9.Tell me about adapting to a major change in underwriting guidelines.

   What they're really asking: Can you adjust your judgment quickly when the rules shift?

   Answer outline (STAR)

   • SituationA significant guideline or regulatory change affecting how you evaluated files.
   • TaskApply the new standard correctly and quickly.
   • ActionStudied the new guideline in detail, reviewed recent files against it, asked questions on unclear points.
   • ResultHow quickly you adapted, and any files that needed re-review under the new rule.

10. 10.Tell me about a decision where you had to balance speed against thoroughness.

    What they're really asking: Can you judge when extra time is worth spending and when it isn't?

    Answer outline (STAR)

    • SituationA file under time pressure with an unresolved question of uncertain significance.
    • TaskDecide how much more diligence was actually warranted.
    • ActionWeighed the risk size against the delay cost, did the minimum additional check that would materially change the decision.
    • ResultThe decision made, and whether the extra check proved worth the time.

Technical and role-skill questions (11–22)

Can you do the work itself? Think out loud and name the trade-offs.

1. 11.Walk me through how you assess the risk on a new application file.

   What they're really asking: Can you describe a structured, repeatable risk process?

   Answer outline

   • Verify the documentation is complete and matches across sources.
   • Assess the key risk factors specific to the product, such as income stability, collateral or claims history.

   Full sample answer (fictional example)

   I start by confirming the documentation is complete and internally consistent, checking identity, income and asset documents against each other before looking at the bigger picture. Then I assess the specific risk factors that matter most for the product, such as income stability, debt load, collateral value or claims history depending on the file type. I compare the file against our written guidelines and note anywhere it falls outside standard parameters. If it's within guidelines, I document the straightforward approval reasoning; if it needs an exception, I document the specific compensating factors and get the appropriate sign-off before proceeding.

2. 12.What compensating factors would make you approve a file outside normal guidelines?

   What they're really asking: Do you understand how exceptions work rather than treating guidelines as absolute?

   Answer outline

   • Strong factors in one area, such as a large down payment or long account history, can offset weakness elsewhere.
   • The combination matters more than any single factor; one strength rarely offsets a serious red flag alone.
   • Any exception still needs documented rationale that would hold up to an audit.

   Full sample answer (fictional example)

   I look for factors that specifically address the weakness the guideline exists to catch, not just general strength elsewhere. If the concern is thin credit history, a large down payment or substantial cash reserves can offset that, since they reduce the actual loss exposure. If the concern is income stability, a long tenure in the same role or industry can help. I'm cautious about stacking several moderate strengths to offset one serious red flag, since that often just means the real risk is being rationalized away. Any exception I approve gets documented with the specific factor and why it justified the deviation.

3. 13.How do you verify income or financial information when documents look inconsistent?

   What they're really asking: Can you spot and resolve inconsistency instead of accepting documents at face value?

   Answer outline

   • Cross-check the stated figures against supporting documents like bank statements or tax records.
   • Request clarification or additional documentation directly rather than guessing at the explanation.
   • Escalate or decline if the inconsistency can't be resolved satisfactorily.

   Full sample answer (fictional example)

   I start by laying the documents side by side, comparing stated income on an application against supporting evidence like pay stubs, tax returns or bank statements. If numbers don't reconcile, I don't guess at the explanation; I go back to the applicant or broker with a specific, targeted request, like asking about a particular deposit or discrepancy rather than a vague request for more documents. If the explanation holds up and is documented, I proceed. If it doesn't, or the applicant can't resolve it satisfactorily, I escalate or decline, since an unresolved inconsistency on income is one of the risks I'm specifically there to catch.

4. 14.How do you stay current with changing underwriting guidelines or regulations?

   What they're really asking: Will your decisions stay compliant as rules change?

   Answer outline

   • Regularly review updates from the relevant regulatory body or internal policy team.
   • Apply new guidelines consistently going forward, and flag files that may need review under the old rules.
   • Ask when a new rule is ambiguous rather than interpreting it alone.

5. 15.What's your process when a file is missing a required document?

   What they're really asking: Basic process discipline that prevents files from stalling or slipping through.

   Answer outline

   • Identify exactly what's missing and request it specifically, rather than a vague follow-up.
   • Set a clear timeline for the request and track it so the file doesn't stall silently.
   • Decide, based on guidelines, whether the file can proceed conditionally or must wait.

6. 16.How do you evaluate collateral or asset value as part of a decision?

   What they're really asking: Do you understand how asset-backed risk assessment works?

   Answer outline

   • Check the valuation against an independent source or appraisal, not just the submitted figure.
   • Consider how easily the asset could be sold and at what discount if things go wrong.
   • Factor the asset's condition and any liens or encumbrances into the final risk picture.

7. 17.How do you document your reasoning on a decision that might be questioned later?

   What they're really asking: Can you create a paper trail that protects the decision and the company?

   Answer outline

   • Write the specific guideline or risk factor the decision was based on, not just the outcome.
   • Note any exceptions made and the compensating factors that justified them.

8. 18.How do you weigh a thin credit or payment history against other strong factors?

   What they're really asking: Do you know how to assess risk with limited data on one dimension?

   Answer outline

   • Look for alternative evidence of reliability, such as rental or utility payment history.
   • Weight other strong factors more heavily, but don't treat them as a full substitute.

9. 19.What's the difference between a guideline exception and a policy violation?

   What they're really asking: Can you distinguish legitimate flexibility from a compliance problem?

   Answer outline

   • An exception is a deviation allowed under defined conditions, with documented justification.
   • A violation ignores a hard requirement that exists for legal or risk reasons and has no approved path around it.
   • Knowing which rules can flex and which can't is central to the role.

10. 20.How would you assess the risk on a file involving self-employed or variable income?

    What they're really asking: Can you underwrite income that doesn't arrive in a predictable paycheck?

    Answer outline

    • Look at an average over multiple periods rather than the most recent, possibly best, month.
    • Check for trend direction and seasonality, not just the average.

11. 21.How do you factor in external economic conditions when assessing risk?

    What they're really asking: Do you account for the environment the file will be repaid or claimed in, not just the file itself?

    Answer outline

    • Consider how sensitive the applicant's income or asset value is to a downturn.
    • Adjust for current conditions like rate changes, local market softness or industry stress.
    • Avoid both ignoring macro risk and letting it override individual file evidence.

12. 22.What tools or systems do you rely on to flag fraud risk in a file?

    What they're really asking: Basic fraud awareness expected of any underwriter.

    Answer outline

    • Automated flags for document tampering, mismatched identifiers or unusual patterns.
    • Cross-checks against third-party verification services for identity and income.
    • Manual judgment on anything that looks inconsistent even if no automated flag triggers.

Take-home or live exercise: tips

Underwriter interviews often include a case file review where you walk through a decision, or a written exercise summarizing your reasoning on a borderline application.

• State the specific guideline or risk factor behind every decision, not just the outcome.
• When discussing an exception, name the compensating factor explicitly and why it offsets the specific concern.
• Practice explaining a decline in plain language, as you would to the broker or applicant, not just internally.
• Show your documentation habit, since a decision that isn't written down clearly is a risk in itself.

Situational questions (23–30)

Scenarios that test judgement: say what you'd do first, and why.

1. 23.A loan officer pressures you to approve a file that doesn't meet guidelines. What do you do?

   What they're really asking: Can you resist pressure from someone whose incentives differ from yours?

   Answer outline

   • Explain specifically which guideline isn't met and why it matters.
   • Hold the decision unless a genuine compensating factor changes the picture.
   • Escalate to a supervisor if the pressure continues, rather than quietly bending.

   Full sample answer (fictional example)

   I explain specifically which guideline the file doesn't meet and why that guideline exists, since most pushback softens once the reasoning is clear rather than it just being a rule. If the loan officer has a genuine compensating factor I hadn't considered, I'll review it on its merits. But if the pressure is really about closing the deal rather than new information, I hold the decision. I've found it helps to put the reasoning in writing early, so the conversation is about the specific risk factor rather than becoming personal. If pressure continues past that point, I escalate to my supervisor rather than making an exception quietly.

2. 24.You find a red flag the day before a deal is set to close. What do you do?

   What they're really asking: Will you raise a late problem even when it's inconvenient for everyone?

   Answer outline

   • Verify the red flag is real before raising it, to avoid a false alarm.
   • Notify the relevant parties immediately rather than waiting to see if it resolves itself.
   • Explain what additional information or time would be needed to resolve it.

   Full sample answer (fictional example)

   I verify the red flag is real first, since a false alarm the day before closing creates unnecessary disruption. Once confirmed, I notify the relevant parties immediately rather than waiting to see if it resolves on its own, even knowing it will be an unwelcome message that close to closing. I explain specifically what the issue is and what would be needed to resolve it, whether that's additional documentation, a short delay, or in some cases a decline. Closing deadlines create pressure to look past problems, but a red flag found late is exactly the kind of thing underwriting exists to catch before funding, not after.

3. 25.Two similar files get different outcomes from two different underwriters. How should that be handled?

   What they're really asking: Do you care about consistency across the team, not just your own files?

   Answer outline

   • Review both files against the same guidelines to see where judgment diverged.
   • Discuss the difference openly with the other underwriter rather than assuming either was wrong.
   • Use the gap to clarify or update team guidance so it doesn't recur.

4. 26.A file passes every guideline but still feels wrong to you. What do you do?

   What they're really asking: Do you trust pattern recognition enough to dig deeper, even when nothing's technically flagged?

   Answer outline

   • Identify specifically what feels off rather than declining on a vague hunch.
   • Dig into that specific area with extra verification before deciding.

   Full sample answer (fictional example)

   I try to pin down specifically what's bothering me rather than act on a vague feeling alone, since a hunch isn't documentable on its own. On one file, every number cleared, but the stated employer didn't show up in any standard verification search. I dug into that specific point, called the employer's listed number directly, and found it led to a disconnected line. That led to uncovering a fabricated employment reference. I document these extra checks even when a file ultimately clears normally, since it keeps the habit sharp and gives a record of due diligence either way.

5. 27.A colleague asks you to quietly approve an exception for a friend's file. What do you do?

   What they're really asking: Will you hold ethical and process lines even under social pressure?

   Answer outline

   • Decline to bypass the normal process, regardless of the relationship involved.
   • Explain that any exception has to go through the documented approval path.
   • Report the request if it continues or feels like a pattern.

6. 28.Your manager asks you to approve more files to hit a volume target. How do you respond?

   What they're really asking: Can you push back on a target that conflicts with sound risk judgment?

   Answer outline

   • Clarify whether the request means more efficient review or lower standards.
   • State plainly if hitting the target would mean approving files you wouldn't otherwise.
   • Propose where real efficiency gains exist instead of lowering the bar.

7. 29.A file you declined is resubmitted with minor cosmetic changes. What do you do?

   What they're really asking: Can you spot when a resubmission doesn't actually fix the underlying risk?

   Answer outline

   • Compare the resubmission carefully against the original decline reason.
   • Approve only if the substantive risk factor has genuinely changed, not just the paperwork.
   • Document why a resubmission was or wasn't treated differently.

8. 30.An applicant claims your decline was discriminatory. How do you respond?

   What they're really asking: Can you show the decision was based on documented, applicable criteria?

   Answer outline

   • Review the file and your documentation to confirm the decision was guideline-based.
   • Explain the specific factors behind the decision clearly and factually.

Red flags to avoid in your answers

Each one is quick to fix before the day.

1. Approving files to avoid conflict with sales or brokers.

   Describe a specific time you held a decline under direct pressure.

2. Treating every guideline as rigid with no concept of a documented exception.

   Explain how compensating factors and exception documentation actually work.

3. Vague reasoning that wouldn't survive an audit.

   Practice stating the exact guideline or risk factor behind each decision.

4. Missing cross-checks between documents in a file.

   Walk through your specific process for reconciling income, identity and asset documents.

How to prepare for an underwriter interview in 7 days

An hour or two a day is enough; the order matters more than the length.

1. 1

   Day 1: Guideline refresh

   Reread the specific product guidelines for this role and note three areas where exceptions are commonly requested.

2. 2

   Day 2: Borderline file drill

   Write out how you'd evaluate three fictional borderline files, naming the compensating factors for each.

3. 3

   Day 3: Decline scripting

   Practice explaining a decline decision in plain language, as you would to a broker or applicant directly.

4. 4

   Day 4: Documentation review

   Draft a sample decision write-up that would hold up if reviewed in an audit months later.

5. 5

   Day 5: Pressure scenarios

   Rehearse out loud how you'd respond to a loan officer or broker pushing for an exception.

6. 6

   Day 6: Fraud and inconsistency check

   List the specific cross-checks you run between income, identity and asset documents on a file.

7. 7

   Day 7: File breakdown

   Prepare a five-minute walkthrough of one real decision: the risk, the guideline, the reasoning and the outcome.

Questions to ask the interviewer

Pick two or three; the answers tell you whether you want the job.

1. What guidelines or policy manual does the underwriting team work from, and how often do they change?
2. How much discretion do underwriters here have to approve exceptions?
3. What does the escalation path look like when sales or brokers disagree with a decision?
4. What's the typical file volume and turnaround expectation per underwriter?
5. What's an example of a guideline that's been refined recently based on team experience?

Preparation tips

• Review the specific product guidelines for the role, whether mortgage, commercial, or insurance underwriting.
• Prepare examples where you held a decision under pressure and examples where you approved a reasonable exception.
• Practice explaining a decline in plain terms, as if to the broker or applicant, not just internally.
• Be ready to discuss how you document decisions so they'd survive an audit or dispute.

Prepare the general questions too: tell me about yourself, why do you want to work here? and why are you leaving? Afterwards, send a thank-you email; when the offer comes, negotiate the salary.