← Back to blog
Hiring Posts Are Not Open Jobs: A Ten-Minute Check Before You Apply

Ricky Chan • Oct 9, 2026 • 8 min read

Hiring Posts Are Not Open Jobs: A Ten-Minute Check Before You Apply

You see a post that says a company is hiring, you spend forty minutes tailoring your résumé, and nothing ever comes back. After a few rounds you start wondering what is wrong with your résumé. Usually the culprit is the post. Treating every announcement of hiring as an open job is the mistake I see most often, and it feels reasonable because the company said it out loud, in public, with a link. Why would anyone bother to post something that wasn't true?

They bother for plenty of reasons. Some roles are filled by the time you read the post, some are pipeline-building for a role that may open later, and some are reposted for months because nobody took them down. The post isn't a lie, exactly. It just doesn't tell you what you need to know, which is whether a human being is waiting for your application this week. Below are four mistakes, the early sign of each, and what to do instead.

Mistake one: believing the post is the job

The early warning sign is a post with no date, no team, and no name, or identical text on three sites with different "posted" labels. Another is that you can't tell who the role reports to. If you can't say who would read your application, nobody has told you the job exists.

The fix is the cutoff this whole article hangs on. Before you write a word of a cover letter, spend ten minutes finding the same role on the company's own careers page and one real person on that team (a manager, a teammate, a recruiter who lists that function). If you find both, apply and send that person a short note. If ten minutes passes and you have only one of them, or neither, drop it and move on. You haven't lost anything, because you spent ten minutes instead of forty.

Mistake two: sending volume and calling it effort

You'll recognize this one if your tracker has thirty rows and zero replies, and you can't remember what row twelve was. Volume feels productive because every submission gives you a small hit of "done." But a generic application to a role that isn't real is the same as no application, only slower.

So cap yourself. Five tailored applications a week, each one past the ten-minute check, plus five short messages to people. That's ten pieces of outreach, which is less than most people send in a single bad evening. Where does the saved time go? Into the messages, because those are the part that tends to get answered.

Mistake three: reading the requirements as a wish list

Take a recent example. A Reddit post on r/JobPH from October 9, 2026, announcing clinical roles at Cognizant, says a candidate must be a Registered Nurse with at least 1 to 3 years of experience in a BPO or healthcare account. That line isn't a suggestion. It is the filter somebody will run on the stack of applications, so find out whether you pass it before you do anything else.

You're making this mistake if you can't point to the exact line in your résumé that answers each hard requirement. The fix is to copy the two or three lines in any posting that sound like a gate (a license, a years-of-experience figure, a named tool) and put your matching evidence in the first third of your résumé, in the same words they used. The "nice to have" paragraph can wait. If you fail a gate, don't apply to that role. Write to a person about a neighboring role instead.

What does layoff news mean for hiring where you are?

This is mistake four, and it runs in two directions. Some people see a headline, such as the X post from the Kobeissi Letter on September 28, 2026 saying tech employment in Silicon Valley has been falling since its 2022 peak, and decide nobody is hiring anywhere. Others ignore it completely and keep applying the same way. Both skip the useful part. A fall like that tells you each posting probably has more people competing for it, which is a reason to reach a person before you reach the portal, not a reason to stop.

The early warning sign is hearing yourself say "the market is dead" after reading one story. Layoffs at one company send trained people to the companies next door, and those companies often start hiring to absorb work they can't cover. So look sideways. When a company in your field cuts staff, check its customers, suppliers, and competitors for the same function, and run your ten-minute check on those.

No report will show you this next part, only the pattern of who answers. Many "we're hiring" posts on social media are written by the manager with the empty seat, and that manager often reads replies and direct messages before anyone looks at the portal queue. A short, specific message under the post (two sentences on the work you've done that matches theirs) can beat a polished application sitting in a system nobody has opened. It fails when the post comes from a recruiting-agency account or a marketing team, because then no one reading your message owns the seat. Check the poster's title first.

One ordinary Tuesday

It's Tuesday and you have ninety minutes before dinner. I'd open the three newest rows in my tracker and run the check on each, with a timer on my phone. The first has a careers-page match and a team lead whose name I can find, so I write that lead four sentences about the closest thing I've shipped or run. The second has the role but no person, so I give it the ten minutes and drop it if no name turns up. The third is a repost from last spring, so I delete the row. If the second one does yield a name, that's two real leads out of three, and I'm done in under an hour.

A week you can actually run

Here is the week, about three and a half hours in all, which leaves your evenings alone:

  • Monday, 45 minutes: Collect ten hiring posts from anywhere. Run the ten-minute check on the first four and cross out the ones that fail.
  • Tuesday, 60 minutes: Tailor two applications and send two messages to people on those teams.
  • Wednesday, 30 minutes: Run the check on four more posts and send three messages.
  • Thursday, 60 minutes: Tailor the other three applications, one for each lead that passed.
  • Friday, 20 minutes: Follow up on anything you sent last week, with one new fact in each follow-up, not just "checking in."

If you'd rather not run that check by hand every morning, GoDotWebs can take it on: it searches an automated database against your profile many times over, drops anything no longer live, and coaches you on what comes back. You still read the matches and send the applications (https://godotwebs.com).

When to ignore all of this

If someone inside the company tells you to send your résumé directly, skip the check, because they've already done it for you. Small employers such as a local shop, clinic, or restaurant often have no careers page at all, so for them walking in or calling replaces the "own page" test. And in fields where openings are constant and applications are cheap, such as many licensed healthcare roles, sending more volume can be the right call. The ten-minute check is for when a post is all you have.

How you'll know the correction is working

Give it three weeks. You'll see fewer rows in your tracker and more replies from named people than from automated systems. You'll also be able to say, for any live application, who would read it and why you matched the gate. If you've sent fifteen well-chosen messages and heard nothing, don't conclude the method is wrong yet. Look first at whether your messages are specific, and whether the people you picked own the seat.

Today, open your tracker, take the three newest rows, and set a ten-minute timer for each. Keep only the ones where you find both the role on the company's own page and a real name on the team, and delete the rest.

Sources

About the author

Ricky Chan coaches job seekers and students on search strategy and writes for the GoDotWebs team. Questions and corrections go to info@godotwebs.com.

Last updated: 9 October 2026.

← Back to blog