Guide
How to decide if a job is worth applying to
Read the posting for its must-haves, then go through the listed skills one by one and ask where you have used each of them. If you can point to real experience for most of the required skills, and the job moves you toward what you want next, apply. If you are missing several must-haves, or the job is a step you do not want to take, skip it and spend the time on a better match.
Why it pays to be choosy
A good application takes time. You read the posting carefully, adjust your résumé, and often write a cover letter or answer extra questions. Spread that effort over dozens of loose matches and each application gets thinner. Spend it on fewer jobs that really fit, and each one is stronger.
Being choosy is not the same as being timid. The aim is not to apply only when you tick every box, which almost nobody does. It is to apply where you have a real case to make, and to be able to make that case quickly.
Step 1: Find the must-haves
Most postings mix two kinds of requirement: things the employer truly needs, and things that would be nice to have. The wording usually tells you which is which.
- Usually firm: “required”, “must have”, “minimum”, “essential”, or anything listed first under a heading such as “What you’ll need”.
- Usually flexible: “preferred”, “a plus”, “bonus”, “nice to have”, “ideally”, or a separate list headed “It would be great if…”.
- Firm whatever the wording: a license or certification the role cannot be done without, where the job is based, travel, and working hours. If one of these does not work for you, no amount of skill will change it.
Check the firm requirements first. If one of them is a clear no, you have your answer and can move on without reading the rest.
Step 2: Check the listed skills against your experience
Now go through the skills the posting asks for, one at a time. For each, ask a simple question: can I name a specific time I did this? Not “I know about it”, but a project, a period in a job, or a result you could describe in an interview. Sort each skill into one of three groups.
- Strong. You have done it, recently, and could talk about it for a few minutes with real examples.
- Some. You have done it, but not often, not recently, or as part of someone else’s work.
- None. You have not done it. Be honest here; this list is only for you.
Strong: Managing a team of 8 to 10 (required). I led a team of 12 for three years.
Strong: Budget planning (required). I owned my department’s budget and yearly plan.
Some: Supplier contracts (required). I took part in two renewals but did not lead them.
Strong: Improving processes (preferred). I cut order errors by a third.
None: Experience in healthcare (preferred).
Verdict: Apply. Two strong and one partial on the required list, and the partial is easy to explain.
How much of a match is enough
There is no exact score, but a few rules of thumb hold up well. On the required list, you want strong or some experience in nearly all of them, with no more than one clear gap. On the preferred list, around half is fine. Postings are often written as a wish list, and many people are hired without every item on it.
Pay attention to which skills you are missing, not just how many. Missing a skill the job mentions once at the bottom is very different from missing the one the whole role is built around. If the posting talks about one thing again and again, treat it as the real requirement.
Step 3: Check the level
Job titles mean different things at different companies, so look past the title to the actual scope. Who would you report to? How many people would report to you? What would you own, and what decisions could you make on your own? Compare that with what you do today.
Treat years of experience as a rough guide rather than a rule. If the posting asks for eight years and you have six, but you have done the work it describes, you are a reasonable candidate. If you have far more experience than it asks for, think about whether the role would hold your interest, and be ready to explain why you want it.
Step 4: Check it against what you want
A job you could do is not the same as a job you want. Before you start searching, write a short list of what matters most to you and what you will not accept. Then hold each posting up against it.
- The kind of work you want more of, and the kind you want less of.
- Where the job is based, and how much of it can be done from home, if that matters to you.
- Hours, travel and on-call work.
- Pay, if the posting lists a range, compared with what you need.
- The size and type of organization you work best in.
If a posting fails one of your deal-breakers, let it go, however good the skills match looks. If it meets them all and the skills match is reasonable, that is a job worth your time.
When to apply even if you are not a perfect match
- Someone can refer you. A referral from a person inside the company often matters more than one missing skill.
- The gap is small and learnable. If the missing skill is something you could pick up in your first few months, say so plainly in your application.
- You have done the work under another name. Different companies use different words for the same thing. If your experience matches what the posting describes, the wording does not matter.
When to skip
- You are missing several of the required skills, or the main one the role is built around.
- A firm requirement, such as location or a license, does not work for you.
- The job is a step back you do not want, or a jump you are not ready for yet.
- It fails one of your deal-breakers.
Skipping a job is a decision, not a failure. Every posting you pass on leaves more time for one you can win. A few minutes of honest checking before you apply will save hours of work on applications that were never going to go anywhere.