"Interested" Is a Feeling. An Application Is Evidence.

"Interested" Is a Feeling. An Application Is Evidence.

By John Crager, CMRP, SHRM-SCP | Next Shift Blog at WorkReady.works Published September 2026 | ~1,450 words | 6 min read

Somebody posts an opening. Full description, requirements, location, a link that takes you straight to the application.

Then the comments start stacking up underneath it.

Interested. Interested. Interested. Interested.

Before anybody rolls their eyes at that, let's be honest about where it comes from. It isn't laziness. It's what happens after the forty-seventh application disappears into silence, and a comment box shows up attached to an actual human being with a face and a name. Of course people type into it. It feels like the first thing in weeks that might get seen by a person instead of swallowed by a system.

I understand the impulse completely.

It still doesn't work, and the reason is worth understanding, because it's the same reason the last two posts in this series exist.

Interest Is Not Candidacy

Nothing wrong with being interested in a job. The trouble starts when interest gets confused with candidacy.

Nobody hires interest. The person on the other end is trying to fill a specific need, and that evaluation starts with an application they can open, a resume they can read, and enough signal to decide whether a conversation is worth thirty minutes.

A one-word comment gives them none of that. Worse, it can mean almost anything:

• I saw this.
• I might apply at some point.
• I'd like you to contact me first.
• I didn't read the description closely.
• I'm not sure whether I qualify.
• I want to be visible without doing the tailoring.

Not one of those tells anyone your target role, your location, your eligibility, your relevant experience, your availability, or whether you can actually do the work.

And when the post lists four openings across three sites, "Interested" gets even thinner. Interested in which one? At what level? Where?

You haven't made anybody's job easier. You've added one more ambiguous thing to sort through, on a post that probably has sixty of them.

Yes, I Know What I Said About Portals

Now for the part where a regular reader of this blog raises an eyebrow.

I've written that roughly a third of postings are theater, that the portal swallows good applications for structural reasons that have nothing to do with you, and that the smart move is often to find the hiring manager directly and open a conversation outside the funnel.

All of that still stands. None of it argues for commenting "Interested."

Going around a broken system and skipping the step that creates a record of you are two different moves. The direct approach works because it puts a specific person in front of another specific person with a reason attached. A public comment does neither. There's no application for anyone to retrieve, no resume, no role identified, and no way to move you forward even from someone who wants to.

It's the only move in the whole search that carries the cost of the portal and none of the benefit of the back channel.

Go around the system when you have something to go around it with.

The Same Trap, Third Time

Post one in this series was about saying you do a bit of everything. Post two was about saying you learn fast.

Same failure underneath both. You're asking the other person to infer your competence, your motivation, and your fit from an unsupported statement, and then hoping they do that inference work on your behalf.

"Interested" is the purest form of it. It asks somebody to go find out whether you're any good.

What everyone on the hiring side is actually trying to do is reduce uncertainty. Can this person do the work? Did they apply? Which opening? Is the experience relevant? Can I locate them in the system in under a minute? Do they understand what this job involves?

Answer those and you're a candidate. Leave them open and you're a comment.

Read, Match, Apply, Message, Follow Up

Five steps. Run them in order and the whole thing gets easier.

Read the entire posting. All of it, not the summary somebody reposted. Requirements, location, work arrangement, minimum versus preferred qualifications, pay if it's disclosed, and the application instructions. Two minutes of reading saves you from applying to something you'd have turned down.

Decide whether the match is credible. You don't need every preferred qualification, and I've argued at length that those lists are usually wish lists. But you should be able to say in one sentence how your experience meets what the role actually needs. If you can't, that's information.

Tailor the resume. Not fabrication, not keyword stuffing. Reorder and rewrite so the most relevant work is where somebody will find it in the first ten seconds, using the words the posting uses.

Apply through the stated process. Whatever channel they named. That's the system where you get tracked, screened, routed, and documented, and it's the only way you exist as a candidate rather than as a name someone vaguely remembers.

Then message, if it adds something. A short note after you've applied can help. A short note instead of applying cannot.

Comment only when the comment carries information. Visibility is fine. Visibility with nothing attached is just noise with your name on it.

What to Write Instead

If you're going to comment publicly, make it do work:

Thanks for posting this. I've applied for the operations coordinator role at the northern site. My background covers scheduling, cross-functional coordination, and running work through multiple departments, and I'd welcome a conversation about the fit.

Short. Professional. Names the role, confirms you applied, gives a relevance signal, and asks for nothing urgent. Somebody can act on that in forty seconds.

For a direct message, the shape is similar and the details matter more:

Hello [Name], I applied today for the [exact title] role. My experience covers [two capabilities the posting actually asked for], including [one concrete result]. I'm particularly interested because [specific reason tied to the work or the organization]. Thanks for the consideration.

The purpose isn't to send your resume a second way. It's to make the first thirty seconds of triage easy, so that when they search their system for your name, they already know why they're looking.

Notice what both versions do. They make a claim of fit and they supply something behind it. Same principle as every other piece in this series.

The Bottom Line

The goal was never to get somebody to notice that you're interested.

The goal is to make it effortless for them to see that you're qualified, serious, and worth advancing. Those are different objectives, and only one of them ends with an interview.

Read the posting. Apply the way they asked. Tailor the resume. Explain the match in a sentence. Then, if you reach out, reach out with enough specificity that the conversation moves.

Interest is a feeling. An application is evidence.

Send the evidence.

← Previously: Stop Saying You're a Fast Learner

Follow along for more: @John Crager, @WorkReady, and @Veteran-X.

John Crager, CMRP, SHRM-SCP, is the author of Blue Collar Resume Mastery and Beyond Thank You for Your Service, both available on Amazon. He writes about career navigation, credentials, and the future of the workforce.

Follow the data. Trust the signal. Skip the noise.