How to decide if a job is worth applying for

The hardest part of looking for work is not finding job ads. There are more than you can read. The hard part is deciding which ones deserve a real effort, because a proper application takes hours you cannot get back.

It is easy to decide on feel. An ad sounds exciting, so it goes on the list. Another one is vague about salary, so it quietly gets dropped. Neither of those is a decision based on evidence, and both of them cost you time.

Start with what you actually know

Before you judge a role, sort the ad into four buckets. It sounds fussy, and it takes about five minutes, but it changes what you do next.

• Facts. Things the ad actually states. The title, the location as written, the named team, the listed responsibilities, any salary range that is genuinely published.
• Evidence. Things you can verify outside the ad. The company’s size, what it sells, recent funding or restructures, who leads the function you would join.
• Assumptions. Things you are filling in yourself. That the role is really more senior than the title suggests. That the salary must be low. That they want someone younger, or cheaper, or already in the industry.
• Unknowns. Things nobody has told you and you have not verified. Much of a typical ad falls here, and that is normal.

Two examples of the difference. A missing salary is not a low salary: the ad simply does not tell you, and there are several possible reasons, such as unpublished pay bands or a wide range. A missing note about hybrid work is not five days onsite either. The policy may vary by team, or nobody may have written it down. You do not know until you ask.

Once you separate those buckets, you can see how much of your reaction to the ad came from the ad, and how much came from you.

Unknown isn’t the same as bad

This is one of the most useful habits to build, and one of the easiest to slip on.

Job ads are incomplete by nature. They are written quickly, approved by several people, and edited down for length. Salary, travel, reporting lines, budget, team size and the real reason the role exists are all commonly left out. When you treat every gap as a negative, you are not being cautious. You are inventing information and then believing it.

The cost of that is false certainty. You end up confident about a role you know almost nothing about, and that confidence closes off options. Some of the best roles people take were advertised badly. Some of the worst were advertised beautifully.

The discipline is simple. If you do not know something, write down that you do not know it, and keep it as an unknown. It stays neutral. It does not count for the role and it does not count against it. Its only job is to tell you what to find out.

The same rule cuts the other way. Enthusiasm is not evidence. Wanting a role badly tells you nothing about whether you can win it, and excitement is not a qualification. Treat your own keenness as a fact about you, not a fact about the role.

Use four questions before you apply

These are lenses, not a scoring system. Ask each one separately and resist the urge to let a strong answer on one carry the others.

• CAN — Can you credibly do the job as described? Look for evidence a stranger would accept that you can already do the core of the work. Gaps in tools, processes or domain detail that you could realistically learn in the role are normal; a gap in the central capability is not.
• WANT — Does the work match what you want next? Direction matters more than title. If the day to day work pushes you further from where you are heading, a pay rise will not fix that in eighteen months.
• WIN — How competitive are you likely to be? Against the realistic field for this role, at this employer, in this market. Capable and competitive are different questions.
• LIFE — Does it fit your life? Pay, location, commute, flexibility, travel, hours, notice period and everything else that decides whether you could actually accept it if offered.

The value is in the separation. A role can be a genuine yes on the work and a hard no on the practical realities, and you want to know that before you write a cover letter, not after a third interview.

Separate ability from competitiveness

This is a common source of wasted effort. It is tempting to check whether you could do the job, find that you could, and treat that as a green light.

Ability asks whether the work is within reach of your experience. Competitiveness asks how you compare to the people who will also apply. In JobHQ, CAN and WIN stay separate questions. You can be entirely capable and still be the tenth best applicant, usually because someone else has done exactly this role, in exactly this industry, at exactly this scale.

A blunt way to test it. If you had to explain in two sentences why you would be shortlisted ahead of someone who has already held the role, could you? If the honest answer is that you are a fast learner, that is ability talking, not competitiveness.

This is not a reason to only apply for safe roles. It is a reason to be clear about which applications are stretches, so you spend your best effort where you have a genuine edge and keep the stretches cheap.

Look for what would change the decision

You will never resolve every unknown, and you do not need to. Pick the one to three that would actually change your answer.

For one role that might be the salary band, because below a certain number you cannot accept it. For another it might be travel, or whether the role owns a budget, or whether the previous person was promoted or pushed out. Everything else can stay unknown without harming your decision. That is why JobHQ shows what it knows and what it does not.

Then go and find out, rather than guessing. Company news, annual reports, the leadership team page and recent employee reviews will answer more than people expect. What is left is a fair question to ask a recruiter early, and asking it is not rude. It is the same question they will eventually have to answer anyway.

A quick checklist before you apply

• I have sorted the ad into facts, evidence, assumptions and unknowns.
• CAN: I can point to evidence a stranger would accept for most of the core duties.
• WANT: the day-to-day work moves me toward where I want to be next.
• WIN: I can say in two sentences why I would be shortlisted ahead of the likely field.
• LIFE: nothing confirmed (pay floor, location, hours, travel) rules it out for me.
• I know the one to three unknowns that would change my answer, and how to check them.

A worked example (fictional)

Northstar Group, a fictional Melbourne company, advertises a Head of Customer Success. The ad lists an advertised sample range of $165k–$180k plus super, but says nothing about hybrid work or travel.

Sorted: the title, range and duties are facts. Company size and recent growth are evidence you can check. “It is probably five days in the office” is an assumption. Work setup and travel are unknowns. On the lenses, the candidate has led a similar team (strong CAN), the role matches their direction (good WANT), others will have more direct industry experience (moderate WIN), and LIFE is provisional because the work setup is not known.

The honest answer is Consider: worth pursuing, but the decisive unknown is the work setup. A short question to the recruiter may resolve it before much time goes into the application.

Decide before you spend hours applying

Finish with a decision, not a feeling. Three outcomes are enough.

• Apply. Strong on the work, plausibly competitive, no practical dealbreakers. This gets your real effort and a tailored application.
• Consider. Genuinely interesting but with a decisive unknown still open. Try to resolve it first. If the closing date is near and you cannot get an answer in time, weigh the hours a full application costs against the chance the answer rules it out, and keep the application lean if you go ahead.
• Skip. A confirmed dealbreaker, or an honest read that you would not be competitive enough to justify the hours. Passing on evidence is a good outcome, not a failure.

Write the reason next to the decision in one line. A month later, when the same company posts something similar, that line will be worth more than your memory of it. And if you find yourself passing on almost everything, or prioritising almost everything, the framework is telling you something useful about your search rather than about the ads.

None of this makes job hunting quick. It does mean the hours you spend go to the roles that could realistically be yours, and that your reasons are based on what you know rather than what you assumed at eleven at night.

Related guides go deeper on common sticking points: requirements you do not fully meet, ads with no salary and researching the company.