Prior Authorization Specialist Interview Questions & Answers

A Prior Authorization Specialist obtains payer approval before services, drugs, imaging or DME are delivered. You gather clinical documentation, submit through portals or forms, track approvals (auth number, CPTs, units, dates), work partial approvals and denials, and keep care schedules moving. Detail-heavy, deadline-driven, patient-impact real.

Snapshot$40,000โ€“$55,000 entry; $55,000โ€“$75,000 with 3+ years (US market)

Skills to talk about in the interview

  • PA submission: Availity, UHC iAOT, Cigna, Humana, BCBS portals; fax CFA forms; ePA platforms
  • Clinical documentation: office notes, imaging results, conservative treatment history
  • Auth mechanics: auth numbers, approved CPTs/units, valid dates, auth vs referral
  • Medication PA: J-codes, formulary tiers, step therapy, specialty pharmacies
  • Denials: CO-197 (no precert), CO-15, retro-auth windows, appeals with clinical support

Fresher (No Experience)

What they test: PA concept, workflow, urgency rules

Q1. What is prior authorization and why do payers require it?

The payer's advance approval that a service, drug or equipment is medically necessary before it's provided. Payers use it to manage cost on expensive or frequently overused categories โ€” MRIs, surgeries, specialty drugs, DME. No valid auth usually means a denied claim.

Q2. What goes into a complete PA request?

Patient demographics and insurance ID, provider NPI/TIN and taxonomy, requesting vs servicing facility, ICD-10 supporting medical necessity, CPT/HCPCS codes with units, place of service, and clinical documentation โ€” notes, test results, conservative treatment history.

Q3. Referral vs prior authorization โ€” what's the difference?

A referral is the PCP directing the patient to a specialist (HMO gatekeeping). A PA is the payer approving the actual service or drug. Some plans need both; many need only the PA. They're tracked separately and both can be required.

Q4. How long does a standard PA take, and what about urgent cases?

Standard is typically up to 14 days (Medicare Advantage standard), expedited is 72 hours with a physician attestation that waiting jeopardizes the patient's health. Commercial payers publish their own timelines in provider manuals.

Q5. Why is PA work detail-sensitive?

Because small misses cause big denials: wrong units, missing conservative-treatment documentation, expired auth dates, wrong facility NPI. The claim pays only if it matches the auth exactly โ€” so precision at request time decides everything downstream.

Q6. Would you be comfortable reading clinical notes as part of your job?

Yes โ€” and that's the honest answer interviewers want. PA work is half documentation-reading: understanding what the note supports, and asking the provider for what's missing rather than submitting weak requests.

TipFresher PA interviews: concept clarity (what PA is, why it exists) plus the 14-day/72-hour pair stated confidently. Willingness to read clinical notes matters more than medical vocabulary.

0โ€“6 Months Experience

What they test: Live submission workflow, tracking, pend management

Q1. Walk me through your PA workflow from order to auth number.

Confirm the CPT needs PA via the payer's lookup, gather clinical notes and the order, submit via portal with ICD-10/CPT/units, record the reference number, track status within the payer's SLA, and on approval record the auth number, approved CPTs, units and dates on the account and notify the scheduler. Pends get follow-ups; denials get reason analysis.

Q2. How do you track pending authorizations?

A PA tracker: payer, reference number, submitted date, status, next follow-up date, and who responded. I work pends oldest-first and by DOS risk, escalating anything past the payer's stated turnaround. Every status change goes on the account so scheduling sees it.

Q3. What do you do with a partial approval?

Record exactly what's approved (e.g., 12 of 20 PT sessions), notify the therapist of the limit, track units used against the approval, and calendar the re-auth before exhaustion. Partial approval is not full approval โ€” treating it as such creates denials.

Q4. The provider's note doesn't clearly support medical necessity. What do you do?

I don't submit a weak request. I go back to the provider with the payer's policy summary and request the specific missing elements โ€” conservative treatment duration, prior imaging, symptom timeline. Complete requests get approvals; weak ones train the payer to deny us.

Q5. What's the difference between an auth denial and a claim rejection for no-auth?

An auth denial happens at PA review (service not approved). The claim-side version (CO-197/CO-15) happens when a claim is billed without matching auth. For claims, I check whether an auth existed under a different provider/facility NPI, or whether retro-auth windows apply.

Q6. Which PA portals have you submitted through?

Specifics: 'Availity (multiple payers), UHC One Healthcare ID with iAOT, [others you truly used].' Add: 'I also know the fax CFA fallback when portals fail, with confirmation-number discipline.'

TipShow the tracker habit and partial-approval discipline. 'I never submit weak documentation' is the strongest 6-month PA signal.

1 Year Experience

What they test: Payer policies, drug PAs, denial prevention

Q1. How do medication PAs differ from procedure PAs?

Drugs route through the pharmacy benefit (or medical benefit for in-office J-codes): formulary tier, step-therapy requirements, quantity limits, specialty pharmacy network. Requests need diagnosis, prior therapies tried, and often specialty pharmacy details. Biologics and oncology drugs have payer-specific criteria I verify in their medical policy first.

Q2. How do you handle imaging PAs (MRI/CT/PET)?

Imaging runs on strict clinical criteria (eviCore, Carelon/AIM for many payers). I confirm the conservative-treatment history matches the criteria (e.g., 6 weeks PT for low back pain), map ICD-10s to the covered indications, and choose the correct CPT with/without contrast. Indication-to-code accuracy drives first-pass approval.

Q3. A claim denied CO-197 with no PA ever requested. How do you try to save it?

Check retro-auth windows first (some payers allow 3โ€“14 days post-service with clinical documentation), then evaluate a medical-necessity appeal if the clinical record strongly supports the service. If neither path exists, it's a documented write-off with a process fix so it can't repeat.

Q4. What's your first-pass approval rate and how do you improve it?

State your real number (e.g., 85โ€“90%). Improvement levers: read the payer's medical policy before submitting, match ICD-10s to covered indications, complete documentation the first time, and maintain a denial log that teaches providers what payers expect.

Q5. How do you handle PA for DME?

HCPCS item codes, rental vs purchase determination, face-to-face documentation, prescription details, supplier network status, and for Medicare the DMEPOS PA list. Rental approvals are month-based โ€” I track rental months because purchase timing follows them.

Q6. How do you manage auth expiry across an active treatment plan?

Validity tracking (from/through dates), weekly unit reconciliation for recurring services (PT, ABA, infusions), re-auth started 2โ€“3 weeks before expiry, and utilization reports so no session is delivered on an exhausted auth. Expiry management is a calendar discipline.

TipOwn one specialty deeply (drugs, imaging, DME) and quote your first-pass rate. The CO-197 salvage playbook (retro window โ†’ appeal โ†’ write-off with fix) is the one-year signature.

1โ€“2 Years Experience

What they test: Specialty depth, provider communication, unit tracking

Q1. How do you handle step-therapy denials for specialty drugs?

Verify the step requirement in policy, document contraindication or failure of required steps with clinical evidence, submit the exception/peer-to-peer with the provider, and if still denied file the formal appeal citing the policy's own exception criteria. Meanwhile the practice knows the drug's status so patient conversations happen.

Q2. The surgeon adds a second procedure to tomorrow's authorized surgery. What do you do?

Check whether the added CPT needs separate auth and whether it's incidental/bundled. If needed, amend the request before DOS through the payer's add-a-procedure process (deadlines often 24โ€“48h). Never assume the original auth covers additions.

Q3. How do you run peer-to-peer requests with providers?

Prepare the packet: denial reason, payer's policy language, the clinical evidence supporting the service, and the specific points the physician should address. Schedule the call promptly (peer-to-peer windows are short), debrief the outcome, and document everything on the account.

Q4. How do you reconcile units for recurring authorized services?

Weekly report: approved units vs delivered units per patient, flag any delivery without remaining auth, notify the therapy/service team immediately, and re-auth before exhaustion. Unit leakage is the most common silent loss in recurring auths.

Q5. How do you communicate PA status to anxious patients?

Honestly and within my lane: where the request stands, realistic timelines, and that the clinical team is engaged. I don't promise approvals โ€” I promise process transparency and timely updates. Patients forgive delays; they don't forgive silence.

Q6. What PA metrics do you watch weekly?

First-pass approval rate, pends aging vs payer SLA, DOS-critical approvals completed before service, approval-to-claim match rate, and units exhausted vs delivered. The last two catch revenue leaks; the first two measure quality and speed.

TipProvider-communication fluency (amendments, peer-to-peer, patient updates) plus unit-reconciliation discipline are the 1โ€“2 year PA signatures.

2โ€“3 Years Experience

What they test: Team management, escalations, metrics ownership

Q1. How do you manage a PA team's daily production?

Distribute by payer competence and service type, track submissions/pends/approvals daily, manage the two clocks (payer SLA and DOS), run a daily stand-up on aging pends and DOS-critical cases, and personally QA every expedited request โ€” those carry the highest patient risk.

Q2. Tell me about a stalled authorization you escalated.

Structure it: what stalled, the payer's breached SLA, patient impact (cancelled appointments), how you escalated (expedited line citing breach + harm risk), the outcome (same-day supervisor review, approved in 24h), and what you institutionalized (documented escalation lane for the team).

Q3. What PA metrics matter and why?

First-pass approval (documentation quality), turnaround vs payer SLA, DOS-critical approved-before-service (patient access), approval-to-claim match (claims left valid), units exhausted vs delivered (leakage). Each metric has an owner and a target โ€” metrics without ownership are wallpaper.

Q4. How do you reduce duplicate or unnecessary PA work?

Quarterly audit of the PA-required list against payer policies (requirements change without notice), remove dead codes, standardize first-time documentation requests so requests don't bounce, and use payer lookup tools as the source of truth instead of tribal memory.

Q5. How do you onboard a new payer volume spike?

Learn the payer's PA rules and portal fast, build a payer-specific checklist, distribute volume to the strongest portal users first, run 100% QA for the first two weeks, and report ramp metrics daily to leadership until stable.

Q6. How do you handle a provider who operates without waiting for approvals?

Data, not opinions: show their CO-197 denial dollars and the write-off trend, propose a firm workflow (no service on schedule without auth number or documented exception), and get the policy signed by practice leadership so the financial-risk owner is explicit.

TipTeam production management, one strong escalation story, and metric fluency with ownership. The provider-compliance answer shows backbone with professionalism.

3+ Years Experience

What they test: Process design, policy monitoring, compliance

Q1. How do you keep a PA team current with changing payer policies?

Structured watch: payer medical-policy bulletins on a monthly list, a shared policy-change log, quarterly re-verification of PA-required code lists, and same-week micro-trainings for affected specialties. Denial patterns are my early-warning system โ€” new reasons mean new rules.

Q2. What compliance boundaries exist in PA work?

Requests must reflect the true record โ€” never alter or embellish clinical information to force approval; expedited criteria applied consistently (no gaming urgency); PHI protected in portals/faxes; payer contracts honored; all communications documented. Our job is accurate representation, not persuasion at any cost.

Q3. How would you design a PA process for a new service line?

Read the payers' medical policies for the line, build documentation templates with providers, define per-payer SLAs, set up the tracker with service-line tagging, run month one at 100% QA, and define patient financial-responsibility communication for at-risk services.

Q4. When do you choose peer-to-peer vs formal appeal?

Peer-to-peer when a physician peer can influence a clinical judgment call โ€” denial explicitly invites it or the reason is 'insufficient medical necessity' with real clinical evidence available. Formal appeal for administrative errors, policy misapplication, or after peer-to-peer fails. Urgency rules matter: expedited appeal windows for urgent cases.

Q5. How do you analyze and act on PA denial patterns?

Group denials by reason/criteria/provider/code, test whether our documentation or the payer's application is the problem, fix documentation against policy language, request peer-to-peers for clinical cases, and take systematic misapplication to the payer's medical director channel. Appeal win rate tells you who's actually wrong.

Q6. How do you balance PA quality with speed under volume pressure?

Tiered workflow: high-dollar/urgent cases get senior review with full packets; routine cases run a standard complete-packet checklist. I never trade documentation completeness for speed โ€” weak requests create more downstream work than they save.

TipPolicy-to-practice translation, compliance boundaries, denial pattern analysis, tiered quality design. Know when peer-to-peer beats an appeal letter.

4+ Years Experience

What they test: Supervision, automation, cross-functional ops

Q1. Where have you used automation or ePA tools?

Moved high-volume imaging and drug PAs to electronic channels (payer ePA platforms, pharmacy ePA networks), built auto-flagging rules for PA-required CPTs at scheduling, and dashboards for pend aging. The human team then works exceptions and pends. I measure turnaround deltas and catch rates monthly โ€” automation drifts when payers change.

Q2. How do you handle a payer that generically denies as 'not medically necessary' at high volume?

Pattern analysis first: which criteria, providers, codes. Fix documentation against their actual policy language, peer-to-peer for clinical cases, escalate systematic misapplication via provider relations/medical director channels, and track appeal recovery โ€” a high win rate proves our process and indicts their application.

Q3. How do you structure PA department staffing?

By complexity and touch: dedicated pods for high-touch categories (oncology drugs, surgery), a general pod for routine imaging/PT, an expedited/urgent desk, and float capacity for surges. Cross-train on two payers minimum; QA at 10%+ with coaching loops; SLA reporting by pod.

Q4. Build-vs-buy framework for PA tooling?

Buy where payer-data currency is the differentiator (ePA networks, portal aggregators) โ€” keeping payer rules current is their full-time job. Build where our workflow logic is the value (auto-flag rules, documentation templates, dashboards). Integration risk and maintenance load decide the boundary.

Q5. How do you manage concurrent PA crises (payer outage + volume spike)?

Command structure: one person owns prioritization (DOS-critical first), alternate channels activated (fax/phone with reference discipline), leadership briefed hourly with burn-down numbers, and post-crisis, a salvage plan for anything that slipped plus a documented root-cause fix.

Q6. What does a good PA QA program look like?

Sample 10%+ of submissions scored against a checklist (policy checked, ICD mapping, documentation completeness, units, facility details), plus outcome tracing (denials on approved-auth claims). Findings feed training and checklist updates โ€” QA exists to improve the system, not to collect scalps.

TipOps-leadership interviews: automation with drift monitoring, staffing pods, crisis command, QA design. Quantify turnaround improvements and appeal recovery rates.

5+ Years Experience

What they test: Strategy, payer relations, ePA evolution, revenue impact

Q1. How has PA strategy evolved, and where is it going?

From fax-and-call to portals to electronic PA (CMS interoperability rules, FHIR APIs, 278 modernization), while payers expand PA into more high-cost categories โ€” specialty drugs, genomics, advanced imaging. The winning strategy: automate routine volume via ePA/APIs and invest clinical-review skill in complex cases. Staying manual on high-volume categories is unsustainable.

Q2. How do you build payer relationships that improve PA outcomes?

Data-driven quarterly reviews with key payers: our first-pass rates, turnaround performance, systemic denial patterns. That makes us a data partner instead of a complainer, opens named-contact escalation lanes, and resolves in days what took weeks. I formalize the lanes in an escalation matrix the whole team uses.

Q3. What revenue impact have PA operations had under your leadership?

Cut CO-197/CO-15 denial dollars through auth-to-claim matching controls, reduced cancellations via earlier DOS-critical approvals, and shortened A/R lag on high-dollar services. Authorization done right is one of the biggest A/R levers on expensive care โ€” I present it to leadership in exactly those terms.

Q4. How do you balance patient access speed against approval quality?

Tiered SLAs: urgent/expedited to senior staff with daily follow-up; routine flows through the standard queue with complete-packet standards. I measure both first-pass quality AND approved-before-service rate so neither gets silently traded away.

Q5. What would you do in your first 90 days leading our PA function?

Audit: current pipeline, first-pass rates by payer, pend aging, auth-to-claim match rate. Quick wins: DOS-critical triage and the escalation matrix. Structural: documentation templates by payer, QA program, and an automation/ePA assessment. Deliver a baseline dashboard by week two so improvements are measured, not claimed.

Q6. How do you future-proof a PA team?

Train toward the exception economy: automation absorbs routine volume, so the team's value moves to clinical documentation quality, denial strategy and payer relationships. I build data literacy (reading their own metrics), rotation across high-touch categories, and ePA/interoperability awareness so nobody is blindsided by the shift.

TipExecutive level: ePA/FHIR trajectory, data-driven payer partnerships, revenue framing, 90-day plans. Close every answer with a measured outcome.