What NPs and PAs Want That Most Job Postings Don't Mention

If you're a practice administrator or physician leader trying to recruit an NP or PA right now, here's something worth sitting with: the job posting you wrote probably isn't answering the questions that actually drive an advanced practice provider's decision.

You listed the specialty. You listed the schedule. You listed the compensation range and the benefits package. You may have even included a line about being a "collaborative, patient-centered team." And your posting looks more or less like every other APP posting in your market.

That's the problem.

The NPs and PAs I work with every day are not making their decisions based on the surface-level details that most job descriptions cover. They're making decisions based on a set of factors that rarely get named explicitly — and when a practice actually names them, the recruiting process moves faster, the candidates are better matched, and the hires stick.

Here's what they're actually trying to figure out.

Autonomy: The Question Behind the Question

When an APP asks about "autonomy," they're not always asking whether they can practice independently. They're asking something more specific: Will I be trusted to do my job?

That means: Will my clinical judgment be respected, or will every decision get second-guessed? Will I have input into how I manage my caseload? Will I be treated as a clinical partner or a physician extender who executes someone else's orders?

The distinction between full practice authority states and restricted states matters legally, but the day-to-day experience of autonomy is a culture question, not a regulatory one. An NP practicing in a restricted state with a collaborative physician who genuinely trusts her clinical judgment will feel more autonomous than an NP in a full practice authority state working in a system that runs everything through a top-down approval chain.

When I'm working with an APP who's evaluating a new role, autonomy is almost always in the top three factors — and they almost never get a straight answer about it from a job posting. The ones that do get a straight answer stand out immediately.

If you want to recruit faster, tell candidates specifically what autonomous practice looks like in your setting. Not "we support APP autonomy." Something real: APPs manage their own panel independently, consult with physicians as clinical partners when needed, and have full prescriptive authority within scope. That's a sentence that answers the question.

Scope Clarity: Know Before You Go

One of the most common frustrations I hear from NPs and PAs after they've started a new job — and one of the most common reasons they're calling me six months later — is that the scope of practice wasn't what they expected.

Sometimes it's narrower: they were hired as a "provider" but the role is really heavily protocol-driven, with little room for independent clinical judgment. Sometimes it's uncomfortably wide: they were hired for a specific specialty but are being pulled into areas where they don't feel adequately trained or supported.

Both situations are avoidable. And both stem from job descriptions that describe a title and a setting without describing the actual scope.

What APPs want to know up front:

What does a typical patient encounter actually look like? Complexity, acuity, time per patient.

What procedures are within scope, and are there any restrictions? This is especially important in surgical, procedural, or urgent care settings where scope varies significantly by practice.

Is this a new APP role or a backfill? A backfill tells me something about the role's stability and clarity. A new role tells me I might be building the position as I go — which some APPs find exciting and others find destabilizing.

What are the hard boundaries? If there are things the practice doesn't allow APPs to manage independently, say so. Candidates would rather know before they accept than discover it three weeks in.

Scope clarity isn't a liability. It's a selling point. Practices that describe scope honestly attract candidates who are genuinely a fit and repel the ones who aren't — which is exactly how good hiring is supposed to work.

Physician Collaboration Style: The Factor Nobody Writes Down

This one is the most overlooked, and in my experience, it drives more early exits than almost anything else.

NPs and PAs are not looking to practice in a vacuum. They want a relationship with their collaborating or supervising physicians — but the nature of that relationship matters enormously. And it varies more than most people outside the practice environment realize.

Some APPs want a tight collaborative relationship: regular touchpoints, shared case reviews, a physician who's genuinely engaged and accessible. They thrive on that dynamic. Others want a more hands-off arrangement: a physician available for consult when needed, but day-to-day independence as the default. Put the first type into the second kind of practice and they'll feel abandoned. Put the second type into the first and they'll feel micromanaged.

What I almost never see in a job posting: any honest description of what collaboration actually looks like in this practice.

How often do the APPs and physicians interact clinically? Is the physician in the building? On-call by phone? Are there structured case review meetings or is it ad hoc? Is the culture one where APPs are expected to run things up the chain frequently, or are they expected to manage their panels independently and escalate only when truly necessary?

These are not difficult questions to answer. They're just questions that most practices have never thought to address in a job posting — because they assume the candidate will figure it out during an interview.

Some do. Many don't, not until they're already ninety days in.

Career Trajectory: Where Does This Role Go?

This one is generational in part, but it's showing up across age groups more than it used to.

APPs — especially those in the five to fifteen years of experience range — are increasingly asking: If I come here and do good work, what happens next?

That's not entitlement. That's a reasonable question from a clinician who has options and is trying to make a decision that serves their long-term career, not just their next paycheck.

In many practices, the honest answer is: "This is a clinical role and it will remain a clinical role. There's no defined leadership track." That's a legitimate answer. Some APPs want exactly that — depth in clinical practice without the headaches of administration. Own it. Say it clearly.

But if there is trajectory — a path toward a lead APP role, directorship, clinical education responsibilities, expansion into a new service line — say that too. Spell it out. NPs and PAs who are thinking long-term will gravitate toward opportunities where someone has thought long-term about them.

What I rarely see: any mention of growth in an APP job posting. Not because growth doesn't exist, but because nobody thought to include it. The candidates who care most about trajectory are often the highest performers — and they're the ones quietly filtering you out when the posting doesn't speak to it.

Why the Practices That Name These Things Recruit Faster

I've placed enough APPs to see the pattern clearly. When a practice takes the time to address autonomy, scope, collaboration style, and trajectory in their job description — or even in the first conversation with a candidate — two things happen consistently.

First, candidate engagement goes up. An APP who's been burned by a mismatch before responds differently to a practice that seems to understand what actually matters to them. It signals that this practice has thought carefully about what they're building and what they're asking of the people who join them. That alone is differentiating.

Second, the wrong candidates self-select out earlier. A clear description of a highly collaborative, physician-integrated model will appeal to some APPs and turn off others — and that's a feature, not a bug. The last thing either party needs is a hire built on mutual misunderstanding.

The goal isn't to write a perfect job posting. The goal is to write an honest one — specific enough that the right candidate reads it and thinks, that sounds like where I want to be.

That's how you stop filling the same role every eighteen months.