Invited to apply, rejected two days later
A recruiter invited a software engineer to apply. Two days later, the same email thread delivered a rejection that did not explain the reversal.
Stories
An open archive of what candidates go through: the ghosting, the seven-stage processes, the take-home tests nobody read, the roles that were filled internally before the advert went up.
Some are found in public. Some are sent in. Contributors choose whether to be named.
The second email, one minute later
A junior Solutions Engineer applicant tailored her materials around practical experience. A rejection followed about one minute after the confirmation.
Fifteen years of proof
After multiple onsite interviews, a technology company asked one candidate for employment records reaching back 15 years, including a paystub. One former employer had been acquired and another had …
Eight years of retail, read as a gap
A recruiter read eight years of retail as a gap because the page did not connect that work to two shipped Linux projects.
Seven rounds of silence
After six months and 500 applications, one candidate describes seven interview rounds, weeks of silence, automated rejection, and application systems that treat people like data-entry clerks.
The memo guessed. The file already had the answer.
An executive put a guess about a candidate's record in writing. The recruiter who received it was already holding the answer, and had no say in which one counted.
Three hours of tests before a human read the application
Three named assessment products, two to three hours, and an automated rejection — all before anyone had read the application. The applicant's own observation is the sharp part: the tests cost the …
Opening the project folder was enough
A company's paid take-home assignment arrived as a GitHub repository, and the repository executed a remote script the moment the folder was opened.
The rejection letter and the scorecard told different stories
A candidate obtained the internal scorecards behind their rejection. The feedback they received and the record the company kept did not describe the same submission.
Told that "I don't know" was a bad signal
Two months of interviewing, and the feedback that came back was that being nervous and admitting a gap both counted against them.
Four days of silence after a four-hour task
A cold approach on LinkedIn, a four-hour task for one company and a two-hour task for another, the final stages of both — and then one of them stopped replying, and the days started being counted.
A full meal, then a surprise AI interview
A co-founder ate through a candidate’s technical presentation. Another carefully worded invitation turned out to be an undisclosed AI interview.
Six interviews, then nothing
A recruiter, a CMO, and four more executives. Then no rejection, no update, nothing a person could use to close the loop.
Too good for the job, right for a worse one
They rang personally instead of using the scheduler. It was to say he was overqualified — then offer him something smaller in the same call.
120 applications, 8% callback
Six months, a hundred and twenty applications, and no reply at all to nearly half of them.
Three quarters, no human in the loop
Sixty applications over five months. Thirty-three were closed before anyone met her — and she was the one who had to work that out.
They rejected her, then posted her video
The assessment asked for an original video shot in-store. She was rejected on the first of May. Then she saw it on the company's own account.
Four rounds, five weeks, silence
Every stage professional, every signal positive. Then nothing.
The marketing internship in a basement
No website, no reviews, a basement office, and fifteen other people her age waiting in the lobby.
The recruiter who lied to get him in the room
The job was permanent only. The pitch suggested it might not be. The recruiter was betting that showing up would change his mind.