How to Decide Which Jobs Are Worth Applying To

When you're searching actively, there's always another posting. Applying to everything feels productive, but every application sent without a real fit takes time away from the ones where you'd stand out. A couple of minutes of triage per posting keeps your effort where it counts.

Start with the constraints you can't bend

Before you read about the tech stack, check the things that rule a job in or out regardless of fit:

• Location and work arrangement. Remote roles often hire only in certain countries or time zones, and hybrid roles vary widely in how many days you're on site.
• Work authorisation. Look for mentions of visa sponsorship, or a requirement to already be authorised to work in the country.
• Pay, where it's listed. If the range sits well below what you need, move on.
• Employment type. Contract, part-time, and full-time roles differ in pay, benefits, and stability.

If a posting fails one of these, no amount of skills overlap will fix it.

Separate must-haves from nice-to-haves

Requirement lists are often a mix of what the team truly needs and what would be a bonus. Look at how the posting is structured: sections labelled “required” versus “preferred” or “nice to have”, and the order of the items, which often puts the essentials first.

A reasonable rule of thumb: if you meet the core requirements and could credibly pick up the rest, apply. Don't rule yourself out because one tool on a long list is missing from your resume.

Read the seniority signals

Titles are inconsistent between companies, so read what the role actually owns.

• Scope words. “Own”, “lead”, “set direction”, and “mentor” point to senior work. “Support”, “assist”, and “learn” point to earlier-career roles.
• The size of the problem. A single feature, a whole service, or an entire platform.
• Years of experience are a rough guide at best. Scope and responsibilities tell you more.

Look at the work itself

• Is the stack one you use now, or one you want to use next? “Experience with” and “exposure to” are different bars.
• What would you build in your first six months? Postings that describe real projects make this easier to judge.
• Would this role move you toward the job you want after it?

Check that it's still live

An old or recycled posting can waste an afternoon. Check the posted date, open the application form to make sure it works, and prefer the employer's own careers page over copies on aggregators. Here's how to find roles on company career pages.

Score it in two minutes

Turning these checks into a quick score makes your decisions faster and more consistent. Rate each posting from 1 to 3 on:

1. Constraints: location, authorisation, pay, and employment type all work for you.
2. Fit: you meet the core requirements.
3. Interest: you'd genuinely want the job.

Apply first to postings that score well on all three, and give them your most carefully tailored resume. Skip anything scoring 1 on constraints. Strong fits you're lukewarm about can wait.

Keep your shortlist organised

Triage only helps if you remember the result. Save postings worth a closer look, and record each application when you send it, so you never apply twice or lose track of where you've been.

JobSorah helps at both ends. Match scores rank roles by how closely they line up with your resume, so you know what to read first, and application tracking keeps a list of what you saved and applied to. A score is a starting point, though. You'll still want to read each posting against the checks above.