Questions to Ask in a Medical Coding Interview
For medical coders and billers, newly certified or with years of charts behind them, at the point in an interview when the hiring manager turns the questions over to you. These questions to ask in a medical coding interview follow the order the decision tends to take: what you would be coding, the productivity and accuracy standards, how audits work, the software and the remote setup, training and credentials, then pay and next steps. If you hold a credential and have no paid experience yet, begin with the Training group, where the question about hiring new coders sits.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
The work
Which specialties would I be coding for?
Why ask it
Specialty decides the code ranges you live in and how hard the documentation is to read: a day of family medicine visits is a different job from a day of orthopedic operative reports. If they name several, ask how the split usually falls in a week, and say which of them you have coded before.
What types of charts are in the queue: office visits, procedures, emergency department, inpatient stays?
Why ask it
Each chart type has its own pace, and the productivity figure you hear later only means something once you know what is being counted. If the list includes a type you have not coded, say so here and ask how other coders picked it up on the job.
What does a typical day look like for a coder on this team?
Why ask it
The useful version is an ordinary Tuesday from login to logoff: how charts reach the coder, whether a huddle or a team chat runs through the day, how many charts are on hold for a query by afternoon, and what closes the day's count. If the description is all coding and no interruptions, ask what interrupts.
Is this coding only, or would I also enter charges, post payments or take patient billing calls?
Why ask it
Titles blur in this field: a 'coder' in a three-doctor office may also chase unpaid claims and answer the billing line, while a hospital coder may never see a claim. Get a rough share of the week for each duty. If billing is part of it, the productivity figure should allow for that, so raise it again when you reach the standards.
Would I be coding the professional side, the facility side, or both?
Why ask it
One encounter can be coded twice, once for the clinician's bill and once for the hospital's, and the code sets and rules can differ between the two. A coder who has only done one side can usually learn the other, but it takes training time, so ask whether that is built in. A small practice may not use these terms at all, and there the question is simply whose services you would be coding.
Would I assign codes from the documentation myself, or check codes a provider or the software has already chosen?
Why ask it
Coding from the note and validating someone else's picks call for different kinds of attention, and the second is usually expected to go faster. Where providers choose their own codes, find out how often coders change them and how the provider is told. That shows how much weight a coder's judgment carries in the place.
How do coders query a provider when the documentation is unclear or incomplete?
Why ask it
You want the route and the wait: a message in the record, a form, a documentation specialist in between, and how many days an answer usually takes. The chart has to sit somewhere in the meantime, so find out where, and who chases a provider who does not reply. Where there is no process at all, the question becomes what coders are expected to do with a note that does not support a code.
When a claim I coded is denied, does it come back to me?
Why ask it
In some departments coders never hear about a denial, and in others they work the coding-related ones and write the appeal. Seeing your own denials is fast feedback, though it takes time out of the day's count. Which payers send the most back, and for what, is a preview of the rules the team codes around.
How many coders are on the team, and how is the work divided among them?
Why ask it
On a team of two you cover everything when the other is out. A team of forty usually means a narrow lane, a lead to ask and someone to pick up your queue during vacation. Find out whether charts are assigned by specialty, by client or by whatever is oldest.
How much contact would I have with the providers, and is educating them part of the job?
Why ask it
Some coders never speak to a clinician, and some are expected to sit down with a physician and explain why a level of service was not supported. If teaching is part of it, ask who backs the coder when a provider pushes back. It is skilled work, and worth mentioning again when pay comes up.
Is there a backlog right now, and how old is the oldest chart in it?
Why ask it
A backlog explains a lot: why they are hiring, why overtime is on offer, why training might be hurried. Managers tend to know this figure closely because uncoded charts are revenue waiting. If it is large, ask what the plan is beyond this one hire.
Is this a new seat, or did a coder leave it?
Why ask it
Growth, a new client or a new service line means the workflow may still be taking shape, and your first months will help settle it. If someone left, ask how long they held the job and what they moved on to. Several departures in a year from one small coding team is a reason to look harder at the standard.
Standards
What is the productivity standard for this role, and what unit is it counted in?
Why ask it
Get the number and the unit together: charts an hour, encounters a day, lines, or a points system that weights harder charts. A single figure applied to every chart type penalizes whoever draws the complex ones, so ask whether it varies. Then set it beside what you have actually done. A coder with no count of their own yet can ask what a first-year coder on the team averages.
What accuracy rate do coders have to hold, and how is it calculated?
Why ask it
The percentage matters less than what counts as an error. Some places score by chart, so one wrong modifier fails the whole encounter, and some score by code. A missed code, a wrong sequence and a wrong level of service may or may not weigh the same, and that is the detail to get.
How long does a new hire have before the full standard applies?
Why ask it
A stepped ramp, with a lower target for the first month and a rising one after, shows the department has brought coders up to speed before. 'We expect you to pick it up quickly' is not a plan. Ask where the last hire stood at thirty, sixty and ninety days.
How is time spent on queries, meetings and system downtime treated in the productivity count?
Why ask it
Every coding day has minutes that produce no finished chart. Departments differ on whether that time is logged and taken out of the calculation or simply comes off your total. If it is logged, ask how, because a clumsy time-tracking step is its own drag on the count.
What share of the team is meeting the standard at the moment?
Why ask it
If nearly everyone meets it, the number is realistic. If half the team is under, either the standard is off or the charts have changed, and you would be joining the half that is struggling. A manager who knows the figure without looking it up is watching the right thing.
What happens when a coder falls below the productivity or accuracy standard?
Why ask it
Listen for the order of events: a conversation, extra review, a written plan, and how long each stage lasts. A department that starts with education treats a dip as a training problem. One bad month setting it off is a harsher policy than a trend over a quarter, so get the trigger.
Is there a turnaround time for charts, such as a set number of days after the visit or discharge?
Why ask it
A deadline changes the job from steady volume to clearing whatever arrived, and it decides how far a provider's late note becomes your problem. Ask what coders do on the days the queue runs dry and on the days it doubles.
When speed and accuracy pull against each other, which does the department want protected?
Why ask it
Nearly every manager will say accuracy. The follow-up tests it: has anyone been praised for slowing down to get a difficult chart right, or only spoken to about their count? What gets rewarded is the real standard.
Audits
How often is each coder's work audited, and how many charts are pulled?
Why ask it
Monthly, quarterly and yearly reviews make for very different jobs. A handful of charts once a year lets a single unlucky sample define you, while a regular pull spreads the risk and catches habits early. It also matters whether the sample is random or aimed at certain chart types.
Who performs the audits: a lead on the team, a compliance department or an outside firm?
Why ask it
An auditor who codes your specialty will catch the fine points and can explain them. An outside firm brings a fresh eye and may know less about the payers you deal with. Either way, find out whether the auditor is someone you could message with a question.
How does audit feedback reach the coder?
Why ask it
A score in an inbox teaches little. What helps is the chart, the code you chose, the code the auditor chose and the guideline behind the difference, with a chance to talk it through. If they have a blank copy of the audit report, ask to see it.
Can a coder dispute an audit finding, and who settles it?
Why ask it
Coding has gray areas, and auditors are sometimes wrong. A rebuttal process with a named decider means disagreement is expected and handled. If findings are final, your accuracy score rests on one person's reading, so ask who reviews the auditor.
Are a new hire's charts all reviewed at first, and when does that step down?
Why ask it
Full review at the start protects you: errors are caught before they reach a claim and before they count against you. The detail to get is what releases you from it, a number of weeks or a run of clean charts, and whether your charts are held from billing until they are checked.
What were the most common errors in the last round of audits?
Why ask it
The answer names what the team finds hard, which is often a documentation problem upstream as much as a coding one. It also hands you something exact to study before your first day. A manager who cannot say may not be reading the audits.
If I believe the documentation does not support a code I am asked to use, who do I take that to?
Why ask it
Coders are sometimes pressed, by a provider or by a revenue target, toward a code the note does not back up. You want a named route, such as a lead, a compliance officer or a reporting line, and some sign that using it has not cost anyone their standing. Ask it plainly and notice whether the interviewer is at ease with the question.
Do payers or outside reviewers audit this organization's coding, and what did the last review find?
Why ask it
External reviews show how the department's work holds up to someone with no stake in it. A finding followed by a described fix is a reasonable answer. Not every interviewer will be free to share this, so accept a general reply without pressing.
Software and remote
Which EHR would I be working in, and which encoder do coders use?
Why ask it
Name the systems you know as soon as you hear theirs. If yours differ, ask how long people coming from another system took to get comfortable, and whether training happens on a practice copy or on live charts. Find out too whether you get a full encoder with references built in or only the code lookup inside the record.
Does computer-assisted coding or an AI tool suggest the codes, and what is left for the coder to do?
Why ask it
Where software proposes the codes, the coder's job shifts toward accepting, correcting and adding to them, and the productivity target is usually set with that in mind. Ask how often the suggestions are wrong for this specialty, and whether an error the tool introduced and you missed is scored as yours.
Which references does the department pay for: code books, a coding guidance subscription, payer policy access?
Why ask it
Buying your own books every year is a real cost, and having no guidance beyond the encoder slows down every hard chart. If the answer is that everything is in the encoder, ask whether that includes the payer policies for the plans you would bill most.
Is the job remote, hybrid or on site, and will that be written into the offer?
Why ask it
A remote arrangement that exists only in conversation is easy to withdraw later. In some departments remote status depends on holding your productivity and accuracy, so find out whether it does here, and how often you would be expected on site for training or meetings.
Are there states or countries where you cannot hire remote coders, and what happens if I move?
Why ask it
Employers are often set up to hire only in certain states or countries, for payroll and legal reasons that have nothing to do with your work. Settle it before an offer if you live somewhere other than where the employer is based, and raise it again if a move is on the horizon.
Does the organization supply the computer, monitors and phone, and does it contribute to internet costs?
Why ask it
Practice ranges from a full kit shipped to your door to a login for your own machine. Coding on one small screen is slow, so ask specifically about a second monitor. If you would be on your own equipment, ask what software goes on it and who fixes it when it fails.
What does my home workspace need to meet your privacy and security rules?
Why ask it
You would be reading patient records at home, and employers set their own conditions: a private room, a screen nobody else can see, a wired connection, no printing. Get the list before you accept, since a shared apartment or a kitchen table may not qualify. Some employers also want a photo of the room or a signed statement.
Are the hours fixed, or can I choose when I work as long as the charts are done?
Why ask it
Remote coding jobs divide into those with a set shift and those with a daily or weekly quota worked whenever you like. If it is flexible, ask about the limits: core hours for meetings, a cutoff for the day's charts, whether weekends count. Hourly staff should also ask how their time is recorded.
How is a remote coder's day monitored?
Why ask it
By output alone, by time logged in the system, or by software that tracks activity on the screen. You should know which before you start, and what a flagged idle period leads to. The answer also says something about how far the department trusts its own productivity numbers.
When the system goes down or I am locked out, who do I call and how is that time treated?
Why ask it
At home there is no colleague at the next desk and no IT person down the hall. Get the support hours, especially if you would work early or late, and whether an outage is taken out of your productivity for the day. How that time is paid for hourly coders depends on the employer and on the rules where you live, so ask how it works there.
Training
What does training look like in the first weeks, and who runs it?
Why ask it
Look for a named trainer, a set of practice or lower-risk charts, and a date when you start working the live queue alone. For a remote job, ask whether it is live on video or a folder of recordings. Being trained by whichever coder has a spare minute tends to mean being trained by nobody.
Do you hire newly certified coders, and what is different about how they start?
Why ask it
With a credential and no experience, this is the question that matters most, so ask it early. A department that takes new coders regularly will describe simpler chart types first, longer review and a gentler ramp. If your credential carries an apprentice designation, ask whether the work here would count toward removing it, and confirm the rule with your credentialing body.
When I am stuck on a chart, who do I ask, and how quickly do they usually answer?
Why ask it
It might be a lead, a team chat, an auditor with office hours or nobody in particular, and a remote coder feels the difference every day. A good sign is that settled answers get written into a shared guideline, so two coders do not code the same scenario two ways. New coders can also ask how many questions a day is considered normal in the first month.
Which credentials do you require, and is there a deadline to earn one after hire?
Why ask it
Employers differ on which certifying bodies and which credentials they accept, and some want a specialty or inpatient credential for particular queues. If a deadline applies, ask what support comes with it and what happens when the exam is not passed on the first attempt.
Does the employer pay for membership dues, continuing education units and exam fees?
Why ask it
Keeping a coding credential generally means paying dues and earning continuing education on your credentialing body's schedule, so this is a recurring cost of the career. Ask for the yearly amount, what it can be spent on and whether it is paid up front or reimbursed. A promise without a figure is hard to hold anyone to.
Is continuing education done on paid time, and does the team run sessions of its own?
Why ask it
In-house sessions on the specialties you actually code tend to be more useful than a general webinar, and some carry CEUs. If education happens on your own time, count those hours when you compare this job with another. Ask what the last session covered.
How does the team learn about code set updates and payer policy changes?
Why ask it
Codes and payer rules are revised regularly, and a coder working from last year's habits makes errors without knowing it. Good answers are specific: an update session each year, a lead who circulates changes, time set aside to read them. If it is left to each coder, add that reading to your picture of the week.
Could I cross-train into another specialty or chart type once I am meeting the standard here?
Why ask it
A second specialty gives you somewhere to go when one queue runs dry, and breadth is what auditing and lead roles tend to draw on. The practical details are who would train you, whether your target is lowered while you learn, and whether errors in the new area count toward your accuracy from the first chart. If nobody on the team has done it, treat the answer as a hope and not yet a path.
Where have coders on this team gone next: auditing, documentation improvement, a lead role, education?
Why ask it
The routes out of production coding are well known, but only some departments have them in house. A name is the proof: someone who made the move, and what it took, including any added credential. Whether pay rises when a coder earns another credential or takes on more complex charts belongs in the same answer.
Pay and next steps
What is the pay range, and is it hourly, salaried or paid per chart?
Why ask it
The structure matters as much as the figure. Per-chart pay rewards speed and leaves you carrying the cost of empty queues and difficult documentation, so ask what you earn on a day with little work. With hourly pay, ask what places a coder within the range: years, credentials or specialty.
Is there a bonus for productivity or quality, and how many coders earned it last period?
Why ask it
A bonus almost nobody reaches is decoration. Ask whether it requires meeting accuracy as well as volume, since an incentive on volume alone pushes toward the kind of coding an audit later marks down.
Would I be employed directly by this organization, or work as a contractor or through a staffing company?
Why ask it
Coding work is often placed through staffing firms and outsourcing companies, and the name on the posting may not be the name on the paycheck. Status affects benefits, taxes and how easily the arrangement can end, and the rules depend on where you live. Ask how it is set up for this role and read the agreement before you sign.
Is overtime offered or expected, and when does the workload peak?
Why ask it
Month-end, year-end and the weeks after a system change are common crunch points, though each department has its own. Find out whether extra hours are voluntary, how they are approved and whether the productivity standard still applies during them.
Is there a coding assessment before an offer, and what does it cover?
Why ask it
Testing candidates on sample charts is common in coding hires. Ask which specialties it draws on, whether it is timed, and whether you may use your code books or an encoder, then practice under those conditions. The passing score is worth knowing too, and so is whether you will see your results.
Is there anything about my experience, such as the specialties I have coded, that leaves you unsure?
Why ask it
A manager's hesitation about your coding background is easier to meet across the table than in a rejection email. If it is a specialty you lack, describe the nearest thing you have coded and how you learned it. If it is that you are newly certified, point to your exam, any practicum charts and what you would do in your first ninety days.
What is left in the process after today, and when would I hear?
Why ask it
Write the date down. Coding hires can involve an assessment, a second conversation with a lead, and background and credential checks, so ask which of those remain. For a remote job, ask how long equipment and system access usually take after an offer, because that sets a realistic start date.
How to use these questions in a medical coding interview
Practical guidance for the conversation itself
Getting ready as a coder
Write down your own numbers first
Before the interview, put on one page what you have coded: the specialties, the chart types, the systems, roughly how many charts you finished in a day and your most recent audit result if you have one. Every standard the manager quotes is easier to judge against that page. If you are newly certified, list your exam date, the specialties you practiced on and any practicum or externship charts instead.
Mine the posting for what it leaves out
Postings for coders usually name the setting and a credential and stop there. Mark what is missing, often the productivity figure, the audit schedule and whether equipment is supplied, and build your questions from those gaps. Asking what the posting already states spends one of your turns and suggests you skimmed it.
Send each question to the person who knows
A coding supervisor or manager can speak to standards, audits and the queue. A recruiter or HR contact usually knows the pay range, the equipment policy and where remote staff can live. In a small practice the office manager may run the interview without ever having coded, so keep the technical questions short there and ask to speak with whoever codes now.
Choose six, one from each group
There is rarely time for more than five or six. Take one from each group and put first the one that would end your interest if the answer were wrong, which for many coders is the productivity standard or whether the job is really remote. Keep the others on your page for a second interview or the offer call.
Asking about standards and audits
A number needs its unit
Twenty a day means nothing until you know twenty of what. Whenever you hear a figure for productivity or accuracy, ask what is counted, over what period and who does the counting. Two departments can quote the same percentage and mean quite different things by it.
Ask for the most recent case
Policies describe what is meant to happen. The last audit, the last coder who fell behind and the last new hire's first three months describe what does. Build the question around the latest example and the answer is usually plainer.
Say you intend to meet the standard
Questions about what happens when a coder falls short can sound like planning to. Open with the reason: you want to know the target well enough to hit it, and you have seen targets set without regard to chart type. Put that way, a manager hears care about the work.
Listen to how compliance is talked about
The question about unsupported codes says more about the department than any other on the page. A manager who answers quickly, names the person you would go to and seems glad you asked is probably running a team where coders can say no. Hesitation, or a joke about keeping providers happy, deserves a second thought before you accept.
Fitting the list to your situation
Newly certified coders
Lead with the question about hiring new coders, because the answer decides whether the others apply. Then spend your turns on training, review of your charts and the ramp to full productivity. Bonuses and career paths can wait: what a first coding job needs to give you is supervised volume and honest feedback.
Remote applicants
Go through the whole remote group, either in the interview or on the offer call: written status, where you can live, equipment, workspace rules, hours, monitoring and support. None of these is awkward to raise, and any one of them can undo an offer after you have given notice elsewhere. Ask for the remote work policy as a document before you sign.
Billers and coder-billers
If the role is mostly billing, translate as you go. Specialties become payers and claim types, the productivity figure becomes claims or accounts worked in a day, and audits become reviews of posted payments, adjustments and follow-up notes. The questions on software, training, remote work and pay apply as written.
When a coding test is part of the process
Get the conditions before you practice: which specialty the sample charts come from, whether there is a clock, and whether code books or an encoder are allowed. Then work a few charts under exactly those conditions. Afterwards, ask for your results whether or not you get the job, since they amount to a free audit.
What trips coders up at this stage
Agreeing to a standard you cannot picture
A candidate who nods at a productivity figure without knowing the chart type has agreed to something unknown. If you cannot work out what the number would mean for your day, say so and ask the manager to walk you through an ordinary hour in the queue.
Letting remote decide everything
Working from home is a strong draw, and it can crowd out the questions about the standard, the audits and the training, which shape the job far more. A remote seat with an unreachable target is still an unreachable target.
Using real patients as examples
When you describe a difficult chart you coded, tell it as a coding problem: the procedure, what the note left out, the guideline you applied. Keep out the patient's name, the date of service, the facility and any detail a listener could trace back to one person. An interviewer who codes for a living will notice the care, and will notice its absence.
Overstating what you have coded
It is tempting to claim a specialty you have only touched. Audits show the truth within weeks, and being hired as a coder who needs training in cardiology beats being found out as one who said otherwise. Say what you know, what is adjacent and how fast you learned the last new thing.