For talent
The Recruiter Saw Your CV for Six Seconds. Here's What They Missed.
Bullet point four is the one about the migration.
Nine months. Four teams coordinated. Zero downtime. Deployment time cut from forty-five minutes to four. You wrote it as one line, because that's what the format allows.
A recruiter never got that far.
She spent six seconds on your CV. Not six seconds per page — six seconds total, and this is not a myth, for the whole document. Your entire professional history, screened in less time than it takes to read this paragraph twice.
Recruiters spend an average of 7.4 seconds on the initial CV screen. TheLadders eye-tracking study, 2018. Seven seconds to decide whether three years of your work is worth a second look. In seven seconds nobody reads. They scan. And scanning only catches what's built to be scanned.
The first two seconds go to the companies' names. Is this a company she recognises — FAANG, a known startup, anything with brand weight. If not, you get filed under "maybe later," which can mean never. You could be the best backend engineer at a ten-person B2B SaaS company nobody's heard of. Doesn't matter. The logo didn't trigger recognition.
The next two seconds go to your job title. Staff beats Senior. Senior beats Engineer. It's pattern matching, not judgment. You were a Technical Lead doing Engineering Manager work? Different words, same work. Doesn't register. Next CV.
The last two seconds go to tenure and education. Two years reads as stable. Six months reads as a red flag — whether you left because the company folded or because the role turned out to be something entirely different from what you were hired for. Nobody has time to ask which. Then: degree, from where. Known university, check. Self-taught, deprioritised. Bootcamp — "we'll see if there's time." There never is.
That's the whole scan. Logo, title, tenure, degree. Everything else — unread.
Six seconds isn't an evaluation. It's a triage.
I. Unread
What was actually on that CV
You chose Postgres over MongoDB because you understood the query patterns and knew eventual consistency would break data integrity two years down the line. You rewrote the payment logic in Go because the Python version was hitting GIL bottlenecks at scale, and you saw that coming before it became an incident. There's no keyword for judgment. Nobody scans for "understood the tradeoffs."
Your CV says "led team of 5 engineers, delivered 12 features in 6 months." It doesn't say you hired three of them. It doesn't say you took two mid-levels to senior in eighteen months by handing them real ownership instead of checkbox 1:1s. It doesn't say you took the blame for a deployment that wasn't your fault, because that's what leading a team actually is. The recruiter saw "5 engineers." A number. Nothing else.
Your CV says "Senior Engineer" this year and "Engineer" three years ago. Reverse chronological order shows that your title went up. It doesn't show what changed in between — that you went from asking "can you review my code?" to being the person reviewing architecture proposals for the entire product. The title progression is visible. The slope isn't.
None of this is a writing problem. You could rewrite every bullet on that CV and it wouldn't matter, because the format can't hold what you're trying to say in seven seconds. The issue was never your prose. It's the read time.
You're not being evaluated on whether you're good at your job. You're being evaluated on whether your CV contains the specific signals a recruiter has been trained to find in under ten seconds. Those are not the same test, and most people have never been told the difference.
II. A different read
A headhunter looking at the same document sees something else entirely
She doesn't scan. She reads — fifteen minutes, not six seconds. She gets to bullet four and instead of pattern-matching the word "microservices," she asks what actually happened. How big was the system. What broke. What decisions got made under pressure and by whom. Then she writes it down the way she'd pitch you on the phone.
CV bullet: "Led architecture migration to microservices, improving system reliability."
What a headhunter would think: nine-month migration from a monolithic Rails app to microservices — not a greenfield rewrite, an incremental refactor under live production load, serving two million daily active users.
CV bullet: "Optimised database queries, reducing load time by 40%."
What a headhunter would think: rewrote the N+1 query loops as batch fetches. Cut API response time from 800ms to 340ms. That unblocked a mobile launch that had been stuck for six weeks.
CV bullet: "Mentored junior engineers."
What a headhunter would think: took two bootcamp grads to senior level in eighteen months by giving them ownership of real systems, not busywork.
Same facts. Same person. One version is legible to a seven-second scan. The other is legible to a human being.
This is the gap we built vairee to close — not with an algorithm pretending to read like a person, but with actual people doing what a good headhunter has always done, at the point where you build your profile instead of at the point where you happen to know one.
Right now that means our team reads your CV the way a headhunter would. We check what backs up the claims — your GitHub, your public work, whatever's out there — and we build your vairee-card from what's actually true, not from what sounds good on paper. You approve every word before anyone else sees it. Nothing goes live without your sign-off.
Your past. Your present. Your future.
This is early. It's manual. It doesn't scale to thousands of profiles a week yet, and we'd rather tell you that than pretend we've automated something we haven't.
None of this makes you more qualified than you are. It doesn't invent a skill you don't have, and it won't turn three years of experience into five. What it does is make those three years visible on the first read, instead of buried in bullet four where nobody gets to it. If you've done the work, this shows it. If you haven't, it won't hide that either. We're not selling qualification. We're selling the chance to be read properly, once.
Being excellent at your job should be enough. It shouldn't also require being legible to a seven-second scan — but right now, it does. That's not a law of nature. It's just a system nobody has rebuilt yet.
Try it. Tell us what's broken.
We built the first version of vairee — a digital professional profile that works for you, not against you. No forms, no black holes, no silence.
If you're a senior professional who's done sending CVs into the void, build your vairee-card. If you're a hiring manager curious what this looks like from the other side, build your own profile first. vairee learns how you think about a role, and uses that to find people who actually fit.
This is MVP. It's early. We're building it with real people, not in a vacuum — which means your feedback, including the bugs, is the point. Use the form or write directly to vairee@vairee.ai. We read everything.
Build your vairee-cardIII. Appendix
Sources
TheLadders, 2018
Recruiters spend an average of 7.4 seconds on the initial CV screen. Key insights on how job seekers can improve their résumés.