Founder field note: the spreadsheet almost hired the wrong person
A few years ago, I watched a hiring process try to politely murder a good candidate.
Small team. Real role. No giant enterprise circus. We needed someone who could run customer ops, clean up messy workflows, talk to users without sounding like a terms-of-service update, and build enough structure that the founders could stop being human duct tape.
Naturally, the hiring stack wanted someone with the exact previous title, the exact software keywords, and the exact career path. Because modern candidate screening loves nothing more than mistaking vocabulary for competence.
One applicant — I’ll call her Lena — came in with a weird-looking resume. Office manager. Support lead. “Operations generalist.” A two-year gap explained in one sentence because apparently caregiving must be formatted like a security incident. She had fixed scheduling, onboarding, billing confusion, churn handoffs, and internal documentation at a 40-person company.
In normal human language: she had already done the job.
In ATS language: insufficient match.
The resume filter bots buried her under people who had “Revenue Operations Associate” in 14-point font and could say “cross-functional stakeholder alignment” without needing medical attention.
Takeaway: assume the filter is literal, not wise
If you are getting screened out, do not immediately conclude you are unqualified. The system may be matching labels, not labor.
Before applying, build a tiny translation table:
| Job post asks for | Your actual proof | Resume/interview wording |
|---|---|---|
| Improve onboarding workflows | Reduced first-week support confusion by documenting 12 recurring issues | “Built onboarding documentation that reduced repeated support questions” |
| CRM hygiene | Cleaned customer records before renewals | “Maintained CRM/customer records for renewal and support handoffs” |
| Cross-functional communication | Coordinated founders, support, finance, and customers | “Coordinated cross-functional customer operations across support, billing, and leadership” |
This is not lying. This is putting subtitles on work you already did because hiring algorithms have the imagination of a vending machine.
The bot score looked official, which made it more dangerous
The first screen produced a tidy little ranking.
Green candidates. Yellow candidates. Red candidates.
Nothing makes a mediocre decision feel scientific like conditional formatting.
Lena landed in yellow-red territory. Not rejected instantly, but not “priority.” The notes were vague in that modern hiring way:
- “May lack direct SaaS ops experience”
- “Unclear ownership level”
- “Potential culture fit question”
- “Missing advanced CRM keywords”
Translation: the system couldn’t tell whether her work counted because she hadn’t performed it inside the preferred costume.
This is where good candidates disappear. Not because anyone sat down and said, “This person is bad.” Because nobody sat down at all.
The automated hiring screen becomes a velvet rope. The AI recruiter becomes a bouncer. The hiring team says, “We’re being efficient,” while a qualified human gets filed under “maybe later,” which is where hope goes to decompose.
Takeaway: fight vague doubts with specific proof blocks
When the process doubts you vaguely, answer specifically.
A proof block is a compact chunk of evidence you can reuse in resumes, recruiter calls, AI interview preparation, and behavioral interview answers. Use this shape:
Problem: What was broken?
Action: What did you personally do?
Result: What changed?
Relevance: Why does it matter for this role?
Example:
Problem: New customers kept asking the same setup questions, slowing support response time.
Action: I reviewed 60 support tickets, grouped the top issues, and built a first-week onboarding checklist with templates for common replies.
Result: Repeat setup questions dropped, and support escalations got easier to route.
Relevance: This role needs someone who can turn messy customer patterns into repeatable ops systems.
That last sentence matters. Hiring teams are often too busy, too overloaded, or too hypnotized by their own scorecard to connect the dots. Connect them yourself.
Then she sent the “second-look” email
Lena did not write a desperate novel. She did not attach a 17-slide shrine to her own resilience. She did not say, “Just circling back,” the phrase candidates are forced to use when they have been socially trained not to scream into the applicant tracking system.
She sent a short email after the automated rejection-ish limbo:
Hi Sam — I saw the ops role and wanted to share a quick role-evidence map because my titles may not mirror the posting.
The role seems to need three things: customer workflow cleanup, internal documentation, and cross-team follow-through. I’ve done each in smaller-company environments, though under generalist titles.
I attached a one-page map with three examples and outcomes. If the team needs exact SaaS RevOps title history, I understand. If the priority is someone who has already cleaned up ambiguous customer operations, I may be closer than my resume makes obvious.
Annoyingly good.
Not needy. Not defensive. Not “please validate my existence, dear gatekeeper.” Just a calm correction to a dumb filter.
The attachment had three rows. Job requirement. Her proof. Relevant metric or artifact. That was it.
It forced the question the hiring process had avoided: are we hiring for the work, or are we hiring for the packaging?
Takeaway: send a second-look packet when the role is real and the miss is obvious
Do not do this for every job. That way lies madness, wrist pain, and a job search dashboard full of false hope.
Use it when:
- The posting is fresh and specific, not a ghost job with recycled corporate fog
- You are genuinely close to the work
- The rejection timing suggests a filter cut, not a final-round rejection
- You can show evidence in one page
- You have a human contact or a recruiter email
Your second-look packet should include:
A one-sentence positioning line
“My titles are nontraditional, but my work maps closely to the role.”Three proof blocks
Pick the three most important job requirements.One artifact if possible
A sanitized dashboard, checklist, process doc, writing sample, GitHub repo, portfolio page, or project summary.A polite escape hatch
“If exact industry experience is required, I understand.”
That escape hatch is not weakness. It shows judgment. It also makes the hiring team admit whether “requirements” are real or just decorative demands thrown into the posting like parsley.
The team argued — which was a good sign
When Lena’s packet came in, the team split.
One person said, “She doesn’t have the title.”
Another said, “But she has the pattern.”
That sentence should be printed on the wall of every hiring room, right next to “No, a sixth interview will not reveal their soul.”
The strongest candidates are often pattern matches, not title matches. They have done the work in a different room, under a cheaper title, with fewer resources, while also fixing the printer and explaining invoices to a furious customer named Glenn.
The scorecard said she lacked “ownership.” Her examples showed she had owned problems nobody had formally assigned her. The recruiter-speak was wrong because the evidence was better than the label.
We moved her forward.
In the live interview, she was not slick. She did not perform the hyper-polished TED Talk version of employability. She paused. She asked clarifying questions. She said, “I don’t know, but here’s how I’d find out,” which remains one of the most hireable sentences in the English language.
She got the offer.
Not because she became a different candidate. Because she made the right evidence visible before the process could flatten her into a bad match.
Takeaway: your comeback is usually a visibility problem
A lot of candidates are not losing because they lack talent. They are losing because their talent is illegible to the ritual.
Your job is to make your proof easy to repeat in every format:
- Resume bullet
- Recruiter screen answer
- One-way video interview answer
- Live panel story
- Follow-up email
- Portfolio artifact
If an AI interview screen is part of the gauntlet, practice translating your examples into clear, timed answers before the blinking avatar starts judging your eye contact like it went to business school. Tools like NoSweatKing can help decode questions and shape answers in your own voice, which is the correct use of bots: making the other bots less ridiculous.
What Lena changed before her rematch
The most important part of this story is not that one founder noticed one candidate.
That is too fragile. You should not need a benevolent human to wander into the machinery with a flashlight.
The useful part is what Lena changed:
She stopped leading with titles
Her old resume said:
Operations Generalist — handled customer support, scheduling, documentation, and admin tasks.
Her revised version said:
Built repeatable customer operations workflows across onboarding, billing handoffs, and support documentation for a 40-person services team.
Same work. Better subtitles.
She named the business problem
Instead of “created documentation,” she wrote:
Created internal support playbooks after identifying repeated onboarding questions across customer tickets.
Now the reader sees judgment, not clerical activity.
She prepared proof blocks, not scripts
Scripts make you sound embalmed. Proof blocks make you sound prepared.
For the culture fit interview, she did not say, “I thrive in fast-paced environments,” because she had self-respect. She said:
I work well in messy environments when priorities are explicit. In my last role, I created a weekly intake list so the founders could choose what mattered instead of everything becoming urgent by default.
That is “strong culture fit” with receipts.
Takeaway: rewrite your experience around decisions, not duties
Hiring teams overvalue job titles because duties are easy to skim and decisions are harder to see.
For each recent role or project, write down:
- What was unclear when you started?
- What did you decide or recommend?
- Who changed behavior because of your work?
- What got faster, cleaner, cheaper, safer, calmer, or less stupid?
- What would have broken if you had not handled it?
The answer to those questions is where your real value lives.
The rematch rule: do not ask them to believe in you — make disbelief expensive
This is the part I want candidates to tattoo somewhere metaphorical.
A good comeback does not sound like begging. It sounds like evidence.
You are not saying:
Please take a chance on me.
You are saying:
Here is the work you need done. Here is where I have done adjacent or identical work. Here is the proof. If you still need a narrower background, fine — but do not confuse unfamiliar packaging with lack of ability.
That is dignity. That is leverage. That is how you walk back into a process that tried to auto-sort you into the basement.
Modern hiring will keep pretending its filters are neutral. They are not. They reward familiar labels, keyword obedience, conventional paths, uninterrupted timelines, and candidates who already know how to speak bot-speak.
So learn the language. Then use it to tell the truth better.
Final takeaways for your next second look
Before you accept a fast rejection as a verdict, run this checklist:
- Did the rejection happen so quickly that job rejection timing points to automation?
- Did your resume use different words than the job post for the same work?
- Can you build three proof blocks tied to the role’s real problems?
- Is the posting fresh enough that a human might still be reviewing?
- Can you send a one-page role-evidence map without sounding like you are appealing a parking ticket?
- Did you track this in your job search operating system so you can see patterns instead of absorbing every rejection as personality damage?
If yes, take the rematch.
Not every company will reconsider. Some are too committed to their own nonsense. Some roles were never real. Some teams say they want builders and then hire the person who best describes building in approved fonts.
But sometimes the strongest candidate in the stack has the worst bot score.
Make them see the score was the problem.
