DEV Community

Cover image for I Got Rejected 2 Minutes After Applying. So Much for 'Skills-Based Hiring.'
Mika Flowers
Mika Flowers

Posted on

I Got Rejected 2 Minutes After Applying. So Much for 'Skills-Based Hiring.'

ATS resume filters spark fierce debate among devs

“Startup culture" on the job listing. FANG-style ATS vetting in the inbox.

I applied for a Junior Solutions Engineer role today.

Not a senior role. Not a staff role. Not some "10 years of experience required" fantasy posting.

A junior role.

The requirements were things like:

  • Hands-on experience in solutions engineering, technical support, sales engineering, or automation-focused work
  • Python
  • SQL
  • Data tooling
  • Automation
  • AI-driven products
  • B2B software
  • The right to work

reqs

And one other thing:

A degree in STEM, Finance, or another strong analytical field.

I don't have one.

I applied anyway, because I actually have experience doing a lot of the work they described.

I recently built an internal operations platform for a real business. The client was managing appliance inventory through a largely manual WooCommerce workflow, including product creation, photos, pricing, descriptions, and updates. I built them a custom inventory management system that turns appliance manifests and uploaded photos into structured product listings, automatically matches inventory data, generates titles and descriptions, surfaces sale price and MSRP, and lets staff review and edit everything before publishing changes to WooCommerce. I also built multi-device synchronization and safeguards so multiple people could work with the same inventory without overwriting or duplicating completed manifests. Along the way I handled API integrations, database work, deployment, troubleshooting, synchronization problems, and user feedback.

That is not a tutorial project. That is not "I followed a YouTube video and changed the button color." That is software being used to solve an actual business problem.

So I did what job seekers are constantly told to do: I tailored my application. I wrote the summary. I wrote the cover letter. I answered the extra question explaining my hands-on experience. I connected my actual work to the responsibilities of the role.

Then I hit submit.

A minute later, I got the application confirmation. About a minute after that, I got the rejection.

rejecton

That's the part that got me. I couldn't help but burst out laughing. Then it hit me: they signed it with a human name instead of just "Company X," which somehow made the whole thing feel even more insulting.

There is no way a human meaningfully reviewed that application

Maybe the degree requirement triggered it. Maybe one of the screening questions did...

I don't actually know. But that's not really the point.

Two minutes is not enough time to open a resume, open a cover letter, read a custom answer, cross-reference all three against a job description, and reach a considered decision. That's not skepticism — that's arithmetic. A recruiter who is fast, good, and fully focused still needs more than 120 seconds to read three documents and actually think about them.

Some rule fired. And that was that.

We hear constantly that tech hiring is becoming more "skills based." Build projects. Contribute to open source. Show initiative. Learn in public. Demonstrate impact. Have a portfolio. Solve real problems.

Cool. I did that.

But if the first layer of the hiring pipeline is still:

degree == true
Enter fullscreen mode Exit fullscreen mode

then a huge amount of that "skills-based" rhetoric starts to feel cosmetic.

The weird part is that I actually understand why filters exist

Companies get hundreds or thousands of applications. Nobody can manually inspect every GitHub profile. Recruiters need ways to reduce the pile. Applicant tracking systems exist for a reason.

I get it.

There is a difference between filtering noise and accidentally filtering out the exact kind of unconventional candidate the industry keeps claiming it wants.

“Someone without a traditional computer science degree is already doing something harder...”

But there is a difference between filtering noise and accidentally filtering out the exact kind of unconventional candidate the industry keeps claiming it wants.

Someone without a traditional computer science degree is already doing something harder: we have to manufacture our own proof. We build. We document. We learn in public. We find real users. We create our own experience because nobody handed us an internship pipeline.

Then we arrive at the application and discover that the credential may still matter more than the evidence.

That is exhausting.

"Equivalent experience" should actually mean something

If a company truly requires a degree because the work genuinely depends on academic training, fine. Say that clearly.

But if the role is fundamentally about Python, SQL, APIs, automation, debugging, integrations, customer communication, and solving business problems, then actual demonstrated experience doing those things should at least earn a human look. Especially for a junior position.

I'm not arguing that I deserved the job — there may have been candidates with much stronger backgrounds, and that's hiring.

What bothers me is the possibility that none of that comparison ever happened. The application may have been dead before my projects mattered.

I'm still going to keep applying

This isn't a "give up on tech" post. Quite the opposite.

I'm building open-source software. I'm doing client work. I'm learning Python more deeply. I'm working with databases, Linux, APIs, automation, and deployment. I'm documenting what I learn.

And I'm going to keep applying to jobs where I can do the work, even when I don't perfectly match the pedigree section.

Because I refuse to pre-reject myself for companies.

They can do that themselves.

Apparently very, very quickly.

Top comments (16)

Collapse
 
georgekobaidze profile image
Giorgi Kobaidze •

Rejecting a candidate within minutes is ridiculous and unprofessional, no matter the reason.

It's sad that we've reached a point where candidates have to tailor their applications for an AI filter instead of a human being, just to get past the first step.

I've interviewed and hired quite a few developers over the years, and I always try to give everyone a fair chance unless something is extremely off. And you know what? Sometimes people with weaker CVs turn out to be much stronger than those with impressive ones. Recruiters need to do much better than this.

I really like your approach. Don't give up trying. Every rejection brings you one step closer to landing your dream job. You just have to keep going.

Collapse
 
mikachu profile image
Mika Flowers •

Thank you Giorgi! This just makes me want to keep going and try even harder <3

Collapse
 
georgekobaidze profile image
Giorgi Kobaidze •

That's the spirit! Love that! 😊

Collapse
 
maame-codes profile image
Maame Afua A. P. Fordjour •

Putting a real person's name on a two-minute automatic rejection is lazy and very unprofessional. And this is unfortunately the case today with a lot of companies....Pretending a human actually looked at your application in that short time is ridiculous.

It is completely their loss. You actually built a working system that solved real business problems and helped people. That kind of hands-on experience is worth way more than just having a degree.

I am glad you did not let that knock your confidence. There is a great saying that a person who keeps moving will eventually meet their luck. As long as you keep building your skills and putting yourself out there, you will definitely find a team that sees your real value.

They missed out on someone who can actually do the job before even giving you a fair chance. Keep your head up, keep going, and move on to the next one :D

Collapse
 
mikachu profile image
Mika Flowers •

Thank you so much for this. 💜 I think the part that frustrated me most wasn’t even the rejection itself but it was realizing how little opportunity there was for the actual work I’ve done to speak for me.

And that’s exactly where I’m landing with it: I’m going to keep building, learning, applying, and documenting the process. I refuse to pre-reject myself just because I don’t fit every traditional checkbox 😇

Collapse
 
sinarezaei profile image
Sina Rezaei •

There’s another side to this that I’ve seen in hiring.

Sometimes the first filter isn’t really about your skill. It’s about the signals on your CV: the degree, university, certificate provider, job title, years of experience, or even the exact keywords used.

For example, some recruiters may immediately question certificates from providers they don’t recognize, while others may filter by a specific degree or certification before looking at your actual work.

So a candidate can have the right skills and real projects, but still never get to the point where anyone evaluates them.

That’s the frustrating part: sometimes you’re not failing the skills test. You’re failing the filter before the skills test even exists.

Collapse
 
mikachu profile image
Mika Flowers •

Its honestly insane! The nerve of them to have Startup culture on their job description LOL

Collapse
 
peakblick profile image
Peakblick •

A 2-minute rejection is almost never a person it's the ATS keyword filter
firing before any human. But yeah it is really bad to hear about this. But you don't have to really worry about it, it does not tell anything about your skills . Perhaps optimizing resume mught help, or at least write a letter to that company.

Collapse
 
mikachu profile image
Mika Flowers •

Yeah, that’s exactly what I’m thinking too. The speed of the rejection makes it really hard to believe anyone actually looked at the application. I’m definitely going to keep tweaking my resume for ATS, but it’s frustrating that getting past the filter can feel like a completely separate skill from actually being qualified for the job 😭

Collapse
 
heytechomaima profile image
Omaima Ameen •

damn, rejected within 2 minutes after putting so much effort into an application is just frustrating tbh!! especially when you've actually built something real and have the experience to back it up.
I feel like this is exactly why so many self-taught developers struggle to get their foot in the door. You spend so much time building your own proof, and then sometimes it feels like nobody even looks at it( btw i'm also self-taught programmer).
Really hope you land somewhere that actually takes the time to see what you can do✨

Collapse
 
mikachu profile image
Mika Flowers •

Self-taught sis!!! It’s getting so hard to break in, but I feel like the fact that we’re self-taught shows that we’re disciplined and motivated. In my opinion, that should be a plus!

Collapse
 
akkitto profile image
Daniel Braniewski •

This time, I will be the one getting tons of flak here. 😉

While the applicant's side is obviously frustrating, I fully see, why such a system would be in-place. If you get thousands of application for a specifically demanded role at your company, with great pay, you can pick & choose more and you have to be very quick and efficient about it, or you will take ages to find the best candidates to actually review.

That said, it is absolutely normal, that a full review happens within a single minute. You don't believe me? Ask any recruiter worth their salt, who processes tons of applications daily. They already work long hours all the time. They work on holidays, including parts of Christmas. I've seen it all. Yet, they don't have the time and resources to read every application from end to end. That's just not how recruitment works.

Again, if anybody thinks, I don't know what I'm talking about, anybody is free to just ask recruiters and they will confirm exactly that, except they are some kind of premium ones looking for super high performers or something.

That does not mean, you should stop trying or be depressed about it.

It's just no use to complain about the situation too much. Just keep on going and expect this to happen lots of times.

Collapse
 
mikachu profile image
Mika Flowers •

Totally fair! and I don’t expect recruiters to read every application from beginning to end, a lot of these posts are basically me venting into the void and trying to make sense of the job search in public 😅 I know recruiting at scale is messy. I just find the disconnect between “please apply” and “instant rejection” frustrating enough to talk about.

Collapse
 
akkitto profile image
Daniel Braniewski •

Just keep trying and keep applying. At some point, there will be someone from HR or whoever the company tells to just find someone, who cares to read applications more carefully, because that person actually cares and you will easily get an interview.

Making a good first impression in the interview is the most important part during a recruitment process, I would say. ;)

Collapse
 
sameerqaisar17 profile image
Sameer Qaiser •

The line that hit me: "I refuse to pre-reject myself for companies."

I'm not job hunting — I'm two weeks into Python and trying to break into technical writing. But I've been running the exact same playbook you describe, and hitting the exact same wall.

Here's my version: I've published 15 articles on Dev.to. I've sent 7 pitches to companies that pay for technical content. I've followed up professionally. I've built a portfolio, a tracker, and a body of work that proves I can write.

The result so far? Zero replies. One company's form only had options for Ruby, Elixir, and JavaScript — no Python. Another said "not accepting new authors." Another required a paid subscription just to submit.

And the rest? Silence.

I keep telling myself the same thing you wrote: the application may have been dead before my work mattered. Maybe it was a filter. Maybe it was timing. Maybe there were 200 better candidates. I'll never know.

What I do know is this: the only thing I control is whether I keep showing up. So I keep writing. I keep pitching. I keep commenting on Dev.to posts at midnight because I want someone to see my name next to thoughtful work.

Your line — "they can reject me themselves" — is going on my wall. Because you're right. Pre-rejecting yourself does their job for them.

For what it's worth, your inventory platform sounds real. Real users, real problems, real integrations. That's not a tutorial project. Whoever didn't read that application missed out.

Keep going.

Some comments may only be visible to logged-in visitors. Sign in to view all comments.