You spent a decade learning to ask uncomfortable questions. Then a hiring process is nice to you for three weeks and the skill quietly steps aside.
The questions that feel slightly rude. Why the seat is open, what happened to the person who had it, what a bad week looks like, and how many people have left in the last two years. None of them are about money, because money is the one thing everyone is braced to discuss.
I sat on the hiring side of these interviews for twenty years, and the pattern almost never changed.
In nearly every physician's job search there's a question the physician wants to ask and doesn't. Usually it's a good one, which is exactly the problem. The good questions feel a little rude, so they never get asked.
You're a guest, everyone's being nice, and pressing feels like you don't trust what's happening. So the question that would have told you the most stays in your head, and the politeness that stopped you costs you for years.
Why it matters: Those unasked questions are the most valuable thing you carry into that room, and most physicians give them away for free.
Why is this job open?
It sounds too basic to bother with, which is part of why nobody asks it. But the answer, and even more the way it gets delivered, tells you a lot.
Growth has a good sound. It's specific and a little proud: a service line expanding, a partner retiring after thirty good years.
Trouble sounds different, because it gets abstract. "We're always looking for great people." "It was time for a change on both sides."
When a straight question gets a soft, careful answer, you haven't hit a dead end. You've found the thing they were hoping you'd be too polite to push on.
What happened to the person who had this job before you?
Almost nobody asks, because it feels invasive. You're not prying, you're reading the history. A role that has launched three physicians into good careers tells one story. A role that has burned through three physicians in four years tells a very different one, and the difference is the next several years of your life.
Dr. Jeff Williams, who spent twenty years hiring physicians, has two questions he thinks every candidate should ask out loud:
"When was the last person you hired? How many have left in the last year, and why?"
His read on a group that won't answer is blunt. "That's immediately a trust bond you're never forming."
The tell isn't a high turnover number. It's the refusal to give you one.
My favorite, because it's hard to dodge: what does a hard week look like here?
Anybody can describe a good week. The good week is the brochure. Ask about the bad one and watch what happens.
A healthy place will tell you honestly, because they've thought about it and they have answers, and that honesty is the reassurance. A struggling place gets vague, or a little defensive. Either way you've just gotten your inspection report for free.
Money is the one thing everyone is braced to negotiate, which makes it the safest and least revealing thing on the table.
The questions that actually predict whether you'll be happy are about fit, and fit lives in the answers people would rather not give: the call, the coverage, the culture, the reason the seat is empty.
Those questions have an edge to them. The edge is why they work.
The strange part is that you've spent a decade being trained to ask uncomfortable questions in order to get things right.
You ask patients about symptoms they're embarrassed by. You push a colleague on a diagnosis that doesn't sit well. You are, professionally, one of the harder people in any room to satisfy.
Then a hiring process is nice to you for three weeks, and all of that useful skepticism quietly steps aside.
Don't let it. Be as warm as you like, because warmth costs nothing and smooths the whole thing along. But ask the question you were about to swallow because it felt impolite.
Politeness is a lovely quality in a dinner guest and an expensive one in the biggest negotiation of your career. You're the only person at that table who's going to pay for it.
No, and it's the most normal diligence question there is. Every employer expects it, most answer it easily, and the ones who don't have told you something more useful than the answer would have. If asking feels rude, that's a signal about the room's temperature, not about the question.
Take that as the answer. There are legitimate limits on what an employer can say about a former employee, but "someone relocated" or "it was a mutual decision" costs nothing to say. Vagueness where a plain sentence would do is information, and you can follow up by asking how many people have left the group in two years, which is not personnel-specific.
Ask them warmly, early, and as routine rather than as a challenge. Framing helps: "I want to make sure I'd actually be good here, so can I ask a few blunt things?" Employers worth joining read that as diligence. The ones who read it as an attitude problem are showing you how disagreement will go later.
Yes. It's the single biggest determinant of what the job feels like, and leaving it to the end signals that you'll accept whatever it turns out to be. Ask for the actual twelve-month calendar rather than the described policy.
Both, and compare the answers. A recruiter can tell you the structure, the process and the numbers. Only the physicians currently doing the job can tell you what a Tuesday is like. When the two accounts differ, the difference is the most useful thing you learned all week.