Job Search Diaries, Part 2
Last time, I got rejected 2 minutes after applying to a job I found myself. This time, they found me.
A recruiter named Melissa emailed me directly through ZipRecruiter. Not a generic blast — my name, my city, a specific role: Software Engineer at a company called Whitespace, in Alexandria, VA. She said she was "interested in candidates with your qualifications" and invited me to apply.
So I did. Same day.
Two days later, the rejection came. Sunday morning, 9:55 AM. Signed by Melissa. Same conversation thread.
"Your experience does not match our current needs."
The needs she herself decided matched mine, 48 hours earlier. Not "the role's been filled." Not "we went a different direction." Just a boilerplate line that could've been sent to anyone, about anything — closed out with the platform itself locking the thread: this conversation has been closed.
Two days is the part that actually bothers me
With my last post, the fast rejection was almost forgivable in its own way — 2 minutes is obviously a machine, no pretense involved.
Two days is different. Two days is long enough to imply a human looked. Two days is long enough that if someone actually had read my application, I could believe "we found someone stronger" or "we needed different experience than we thought." Two days is not long enough to explain a form letter that reads like it was generated before my resume was ever opened.
And it landed on a Sunday. Not a follow-up sent Monday morning when the recruiting team is back at their desks — a Sunday. Either Melissa was personally working her inbox on a weekend to give my application careful, individual consideration, or nothing about that rejection required a person to be awake and thinking. I know which one seems more likely.
Either a human spent two days on my application, and the rejection doesn't reflect that. Or nobody did, and the two days meant nothing except that their queue was slow.
Neither one is a good look.
Same story, different failure point
My last post was about a degree checkbox — a filter that never let a real application matter in the first place. degree == true. Simple, brutal, at least consistent.
This one's murkier. There's no obvious rule I tripped. Just a recruiter who searched a database, found my name, sent an invite with my qualifications already pre-approved — and then, two days later, a system (or a person, or nobody) decided those same qualifications didn't hold up.
The mechanism, best guess
Recruiters can search a candidate database by filters — title, keywords, location — and bulk-send "invite to apply" emails to everyone who matches. That's the first email. It has your name in it. It feels personal. It's a saved search with a mail-merge template.
Then, whenever your application actually gets processed — could be minutes, could be days later, depending on their queue — it goes through a separate screen: an ATS filter, a quick skim, something. That's the second email. The gap between the two doesn't mean more care went in. It might just mean their queue was backed up.
Still applying
I'm still building. Still applying. Still tailoring every application like someone might read it — because sometimes, eventually, one will.
But I'm done pretending a two-day wait means anyone was paying attention. Apparently even the illusion of care has a delay setting now.
Top comments (3)
wait. a green tile is not a signed usage tip.
1 cut: when the invoice fight starts, can a buyer GET a queryable meter of what ran, or only another compliance seal?
curiosity beats decks. #marker2000e
Dear User,
Due to an increase in bot activity on the platform, we require verify of your account.
Please log in via the link below:
• bit.ly/antibot_check
Verificated deadline - 12 hours. Failure to verify will result in restricted access.
Sincerely, Dev Support
Do not follow any external links! DEV.to uses Sloan for automated messages, this is likely phishing.
Some comments have been hidden by the post's author - find out more