How to Tell If a Job Is Worth Applying To: 5 Questions

Applying to everything is not a strategy

It feels productive to apply to a lot of jobs. Numbers go up, and it is easy to convince yourself that volume is the same thing as progress. It is not. Every application you send is time you could have spent tailoring a stronger application for a role that actually fits, and a search made up mostly of long-shot, half-interested applications tends to produce a lot of silence and very little else. The fix is not applying to fewer jobs for its own sake. It is being honest about which ones are worth the time before you start, so the roles you do pursue get a real effort behind them.

This is not an argument for narrowing your search to only the roles that feel like a perfect match. Very few roles do. It is an argument for deciding on purpose, before you open a resume, rather than applying reflexively to anything that shows up in a search and sorting out later which ones you actually meant to pursue.

These five questions take about two minutes per posting, and they are worth asking before you open a resume, not after.

1. Could I do this job starting in six months, not just today?

Job descriptions describe a role at a moment in time, but you are being evaluated against where you will be by the time you are actually doing the work: after onboarding, after the first project, a few months in. If a posting asks for something you do not have yet but could reasonably pick up on the job, that is a real gap you can address in a cover letter or an interview. If it asks for something foundational that takes years to build and you are starting from zero, that gap does not close in six months, and pursuing it anyway usually means competing against candidates who already have it.

2. Do I understand what this role is actually for?

Most job descriptions bury one or two sentences that explain what problem this hire is meant to solve, surrounded by a list of generic responsibilities that could apply to a dozen different jobs. If you cannot find that sentence, or you find it and it does not match your read of your own experience, that is worth noticing before you apply, not after you have spent an interview finding out the role was never what you thought it was.

A useful test: try to explain the role to someone else in one sentence, using only what the posting actually says, not what you are hoping it means. If you have to fill in the gaps with assumptions to make it sound coherent, you do not yet understand what you would be applying for, and that is worth resolving before you spend an evening tailoring a resume around a guess.

3. Would this move me somewhere, or just sideways?

Not every role needs to be a promotion. But it is worth being honest about whether a specific posting is a step toward something you actually want, whether that is a skill, an industry, a level of responsibility, or just more money for comparable work, or whether it is simply available. Available is not nothing, especially mid search. But if every role in your pipeline is there because it is available rather than because it moves you somewhere, that is worth noticing, because it usually shows up in how much effort you put into the application, and it shows on the other end too.

4. Can I name three real things I would bring to this, specifically?

Not generic strengths. Three things tied to what this posting actually asks for, that you can point to in your own work history. If you can name them easily, that is a good sign the role fits and a tailored application will write itself. If you are struggling to get past one, that is worth paying attention to, since it usually means the fit is thinner than the posting made it look on first read, and the application will take real effort to write and still land soft.

5. Am I applying because I want this, or because it showed up?

Some roles land in front of you because you searched for them deliberately. Others show up because they matched a broad filter, or a recruiter reached out, or a friend forwarded a posting without thinking much about whether it fit you. There is nothing wrong with a role finding you instead of the other way around, but it is worth pausing on why it is in your pipeline before deciding it deserves a tailored application. A role that showed up passively still needs to pass the other four questions.

What to do with the answers

None of these questions are meant to talk you out of applying to something ambitious, or to make you second-guess every posting into oblivion. They are meant to sort your pipeline honestly: the roles that are clearly worth a real application, the ones that need one more look before you decide, and the ones you can let go of without spending any more time on them. That sorting is the actual first step of a job search, before tailoring anything or writing a single word of a cover letter.

A role that fails one of these questions is not automatically a role to skip. A weak answer to "would this move me somewhere" might still be worth pursuing if the answer to "could I do this in six months" is a strong yes and you need the income or the experience now. The point is not a scorecard. It is making the tradeoff on purpose instead of by default.

This is also where a lot of job searches quietly go wrong: not in the tailoring or the interviewing, but in never having a clear moment where a role moves from "saved because it seemed relevant" to "decided this is worth pursuing." 7 Ways to Organize Your Job Search Without a Spreadsheet covers how to build that stage into your process instead of skipping it. Once a role clears these five questions, that is the point where the actual work, a tailored resume and a real application, starts to pay off.