You read a job post, you match seven of the ten requirements, and you close the tab. I will show you why your brain does that and the small daily rep that gets you to hit "apply" anyway.
Quick background so you know where this comes from. I'm Christopher. I spent nine years in the Marine Corps, then moved into software and data engineering, including edge computer vision work for the Air Force on a project called Athena. I have walked into rooms where I was clearly the least qualified person there, and I have also talked myself out of roles I would have crushed. The second one cost me more.
If you keep skipping applications, you are not lazy and you are not unqualified. Your filter is running the wrong math.
What you actually read
The posting says: "5+ years of Kubernetes experience preferred."
What you read: "Real engineers have this. You don't. Don't embarrass yourself."
That gap is the whole problem. A job post is a wish list written by a hiring manager in a hurry, sometimes copied from an old post nobody updated. You read it like a legal contract. So you only apply to roles you are overqualified for, you get bored in six months, and the cycle repeats.
Why it hits so hard
I don't believe you build confidence. I believe you unhide it. The same developer who will happily pick up an unfamiliar library on a Tuesday and ship with it by Friday will refuse to apply for a job that lists that library. The skill to learn is already there. What changed is that now someone might say no.
Your brain runs a selective filter called the reticular activating system, the RAS. It decides what gets your attention, and it learns from what life fed it. Maybe you got picked last. Maybe you applied for something big once and heard nothing back. Maybe someone told you to stay in your lane. Your filter took notes: reaching equals rejection, and rejection equals danger.
So now, when you read a job post, the filter skips the seven things you can do and locks onto the three you can't. You cannot logic your way out of that. Telling yourself "just apply, what's the worst that can happen" bounces off, because the filter does not run on logic. It runs on experience. So you feed it new experiences.
The daily rep: compliment a stranger
Once a day, give one genuine, specific compliment to a stranger. Nice jacket. Great laugh. That's a cool bike. Say it, smile, keep walking.
I know that sounds unrelated to a job hunt. It is the same muscle at low stakes. You are making an offer with no control over whether it gets accepted, while your body braces for a no. The first few will spike your heart rate. Then they stop.
The rule that makes it work: the win is the action, never the result. They ignore you, win. They light up, win. You only managed to think it, still a win. If you only count the ones that go well, you are training the old program that says reaching out only counts when people say yes. The rep is the point.
That is rung one of a short ladder:
- Genuine compliments to strangers
- Compliment plus a quick "how's your day going?"
- A longer conversation, no agenda
Move up only when the current rung stops spiking you.
Bring it to your job search
Once the stranger reps feel easy, run the same reps on applications.
Count what you have, not what you lack. Before you close a tab, write down every requirement you meet. If it is around 60 percent, you apply. That is the rule. No debate with yourself.
Translate the gaps. "No Kubernetes" becomes "I deployed containers with Docker Compose and I learn infra tools fast. Here is one I picked up in two weeks." A gap with a learning story is not a gap. It is proof you grow.
Apply to one stretch role a week. Not ten. One. A role that makes your stomach tighten a little. That stomach tightening is the rep.
Count the send, not the reply. Same rule as the compliments. You hit submit, win. They ghost you, still a win. Your job is the action. Their job is the decision. Don't do their job for them by rejecting yourself first.
Ask one real person. Message one engineer at the company: "I'm applying for the backend role. What does the team actually use day to day?" Most people answer. Each answer teaches your filter that reaching out is safe.
What Athena taught me about "not ready"
On Athena, edge sensors ran a local model. The model was never perfect. When it flagged something significant, it sent context from before, during, and after the event back to AWS so it could be retrained. If we had waited until the model was perfect before deploying it, it would never have gotten better, because the field data was the thing that made it better.
You are the same. You don't get ready and then apply. You apply, interview, get feedback, and that is what gets you ready. Waiting until you check every box is like keeping the model in the lab forever.
You already know how to learn the missing thing. Old training just taught you that asking for the chance is the dangerous part.
Your mission this week
- Compliment one stranger a day for seven days.
- For every job post you skip, write down which requirements you actually meet.
- Apply to one role where you meet about 60 percent of the list.
- Rewrite one "gap" in your resume or cover letter as a learning story.
- Message one engineer at a company you want to work for.
Then tell me in the comments: what is the requirement that always makes you close the tab, and how much of it could you learn in a month?
Top comments (1)
Your Kubernetes line is a good one to put a number on, because I counted exactly that this week. Of the employers with an open backend posting in Germany, 32% mention Kubernetes anywhere in the text, and "anywhere" includes "nice to have". In the UK it's 37%. Even the single most-mentioned technology in each of the five countries I looked at stopped at about half of employers.
So when a posting lists ten things, most of them are things that employer's peers don't ask for at all. That's your wish-list point with numbers under it, and it makes the 60% rule look generous.