What “Preferred” Actually Means in a Job Posting

I wrote the same sentence three times last month, in three different job postings.

Different clients. Different disciplines. A Plant Manager, a Manager of Design and Drafting in Calgary, a Senior Accountant working remotely.

Each time, some version of the same line: this credential is not required.

I didn’t write it three times for style. I wrote it because I keep watching qualified people read a preference as a wall.

Three Postings, Three Versions of the Same Sentence

Close to word for word, this is what went out.

• Plant Manager. Your current title doesn’t necessarily have to be Plant Manager.
• Manager, Design and Drafting. An engineering background and P.Eng. would be an asset, but significant hands-on design and drafting experience is equally important.
• Senior Accountant. CPA or designation is preferred, but it’s not a deal breaker.

Three clients who have never met. Three disciplines with almost nothing in common.

One shared problem, which is that the person best suited to each role was likely to read the posting and decide it wasn’t for them.

I only noticed the pattern because the three searches ran in the same four weeks. Written a month apart, I would have called each one a coincidence.

Why I Now Write “This Isn’t Required” Out Loud

The word preferred used to do this job on its own. It doesn’t anymore.

Candidates have been trained out of believing it. They have applied to enough postings that listed ten preferences and quietly meant all ten. They have been screened out for a “nice to have” often enough to stop treating the label as real.

So the word has been drained of meaning, and the only repair I have found is to be blunt in the posting itself. The line that works reads closer to this: we will hire someone without this, and here is what matters more.

The change in the applicant pool was immediate. Fewer applications overall in some cases, and a noticeably better middle of the pack.

The people who had been self-selecting out started arriving.

A posting communicates far more than its requirements list, which is a subject on its own. What your job posting is actually saying covers the tone and the signal. This post is about the list.

What Genuinely Can’t Be Flexed

I want to be careful here, because there’s a version of this argument that collapses into “requirements don’t matter,” and that version is wrong.

Some things are walls, and they should be.

Legal and contractual. A P.Eng with stamping authority is required to seal drawings. That one comes from the regulator, and no amount of hands-on experience substitutes for it. Same with work authorization, and with the safety-critical tickets a client’s own insurer or prime contractor mandates on site.

Capability that has to already exist. Some roles need someone who has already held commercial responsibility under pressure, or has already run a plant floor through a bad quarter. You cannot coach that in during the first year, because the first year is when it gets tested.

The question I ask a client to separate the two is short. Can this person learn it inside a year, and can the team carry the gap while they do?

If both answers are yes, it’s a preference. If either is no, it’s a requirement, and it belongs in a different part of the posting.

That distinction shows up whenever a strong candidate comes from an unexpected direction, which I’ve written about in when the right hire isn’t where you’d expect.

The Candidates Who Never Applied

This is the part nobody sees, and it’s the reason I keep writing that sentence.

The cost never arrives as a bad hire. It arrives as an absence. The applications you never received, from people you would have wanted, who read one line and closed the tab.

On the Plant Manager search, the strongest operational leaders in the pool weren’t carrying the title. They were Operations Managers and Production Managers running the same scope under a different label.

Several of them told me, once I called, that they had seen the posting and skipped it.

The design manager was the same shape of problem. Fifteen years of hands-on drafting leadership, deep in the tooling, credible with the shop floor, no P.Eng.

Exactly the person the client described wanting. He saw four letters in the qualifications section and moved on.

When I call these people directly, the sentence I hear is always some version of the same one: “Oh, I didn’t think I qualified.”

They weren’t being modest. They were reading the posting the way it was written.

How a Preference Becomes a Requirement Without Anyone Deciding

Nobody sits down and chooses to cut half the pool. It happens through accumulation.

A job description gets built by committee. The hiring manager writes the core. HR adds the education line, and someone in the department suggests the software they’d like the person to know. A director adds an industry preference because the last hire struggled without it.

Every contribution is reasonable on its own.

Nothing gets removed, because removing something means arguing that it doesn’t matter, and nobody wants that meeting. The list grows in one direction only.

Then the posting gets reused. It goes into the folder, comes back out for the next opening, and by the third use the preference has hardened into a requirement that nobody in the room can trace the origin of.

Ask why the CPA is on there and you’ll often get a pause.

A JD is a document that accumulates and never gets edited down. That accumulation is one of several reasons a search stalls for reasons that have nothing to do with the market, which I’ve gone through in you’re probably solving the wrong hiring problem.

How to Write a Posting That Means What It Says

Four things, and the first one does most of the work.

• Rank instead of listing. Pick the three things a person genuinely cannot do this job without and put them in their own short section at the top. Everything else goes below, under a heading that says plainly it’s a wish list. A flat list of twelve items reads as twelve requirements no matter what you title it.
• Say the quiet part in the posting. If you’d hire an Operations Manager into a Plant Manager role, write that down. Naming the adjacent titles you’ll consider is the single highest-return line you can add, and it takes ten seconds.
• Name what you’ll teach. Almost every employer will train someone on their ERP, their drawing standards, their internal systems. Almost none of them say so, so the software line reads as a hard filter. One sentence about what you’ll bring someone up to speed on changes who is willing to apply.
• Test it on someone outside the function. Hand the posting to a colleague who doesn’t do this work and ask them who they think is qualified. If their answer is narrower than what you meant, the posting is narrower than you meant.

The reverse problem, a posting so vague it produces two hundred unusable applications, has its own fixes in too many applicants, your job posting is broken. The two problems have the same root, which is a posting that hasn’t decided what it’s asking for.

If You’re Reading a Posting and You’re Not Sure

The working rule I give candidates is simple. If you meet the genuine core of the job and you’re short a preference or two, apply and let them decide.

You are guessing at how a company weighs its own criteria, from the outside, based on a document written by four people over three weeks. You will guess wrong, and the application costs you twenty minutes.

Address the gap rather than hoping it goes unnoticed. One line in the cover note or the opening of the email does it: I don’t hold a P.Eng. I’ve led drafting teams for twelve years and set the standards three of them still run on.

That sentence does more than a perfectly matched resume with a hole nobody explains. The same instinct applies to any break in a work history, which I’ve covered in resume gaps and getting past the automated rejection.

Then there are the walls that really are walls. Believe these ones:

• Professional licensure and stamping authority. P.Eng registration where sealed drawings are involved.
• Safety certifications a site requires. These come from the client or the insurer, and the employer can’t waive them.
• Legal right to work. No flexibility exists here regardless of how strong the fit is.

If the requirement has a regulator or an insurer behind it, put your energy into the roles where it doesn’t apply. Everything else is worth a conversation.

Ask Before You Assume

If you’re hiring and a search isn’t producing the applicants you expected, the posting is the cheapest thing to check. It’s usually faster to fix than the strategy around it, and it’s the only part of the process the whole market can see.

If you’re on the other side and you’re not sure whether you qualify, ask. I’d rather have that conversation and tell you honestly than watch a good fit disappear because of a word in a bullet point.

Get in touch, and I’ll give you a straight answer.

“Preferred” Actually Means FAQs