Skip to main content

User stories

Five people. Five rejection loops. Five resumes that broke them.

The most common shape of a CVHive user story isn't “I learned a new skill.” It's “I started writing my CV the way recruiters actually read it.” Here are five.

NEW GRADUATE

I applied to 64 companies and got 1 interview. Then I rewrote my CV. 11 interviews from the next 20.

Maria K., 23, Computer Science graduate, Barcelona.

My family kept asking when I'd get a 'real job.' I had a CS degree from a top Spanish university and zero offers. Six months in, I started believing them.
Q: What was on your old CV?
A: GPA at the top. Three internships I'd done, listed with one-line descriptions like "supported the engineering team." Then a Volunteer section. The recruiter spent 7 seconds on it and moved on.
Q: What changed?
A: I rebuilt it project-first. Side projects with measurable outcomes, things like "Built a job-board scraper that processed 12k listings in 4 hours, used by 30 people in my class." The GPA dropped to the bottom. The volunteer section went away.
Q: How long until you saw a response?
A: 19 days. First reply was from a Series B fintech in Madrid. The recruiter said the projects "told a story." I'd never had a recruiter say that before.
Q: What's the one thing you'd tell another grad?
A: Stop listing what you did. Show what you built and what happened because of it. Recruiters don't care that you worked in a team. They care that the team shipped something measurable.

What changed? Maria stopped writing the CV her university told her to write, and started writing the one a recruiter could scan in 7 seconds.

Build yours →

CAREER SWITCHER

I spent 6 years in marketing. Two months ago I switched to product. The CV did the work.

James T., 34, ex-marketing lead now Product Manager, London.

Everyone told me a career switch at 34 was either too late or too risky. I'd already been told 'you don't have product experience' nine times in two months.
Q: What were you doing before?
A: Six years in B2B marketing. I'd worked on positioning, gone deep on customer research, done a few product-launches for the marketing team. None of it counted, according to my old CV.
Q: What did the old CV say?
A: Job-title-first. "Senior Marketing Manager." Then bullets about campaigns. Reads like a marketing CV, because it was.
Q: What did you change?
A: I moved the cross-functional product-launches to the top of every job, and I wrote them as product work. "Launched a self-serve onboarding flow that lifted day-7 retention from 21% to 38% in two quarters." That's the product team's metric, not the marketing team's. It was always there. The old CV just buried it.
Q: How fast did things turn?
A: Four first-round interviews in the first 20 applications post-rewrite. Two onsites. One offer. Done.

What changed? James didn't get new skills in two months. He stopped describing the work he'd already done as marketing work, and started describing it as product work.

Build yours →

CAREER COMEBACK

I took 4 years off to raise my son. Re-entering tech at 41 felt impossible. I had 2 offers in 9 weeks.

Liana R., 41, Senior Backend Engineer, Bucharest.

The first phone call back from a recruiter, I cried. Not because they offered me a role. They didn't, that day. Because someone had actually read the CV instead of seeing the gap and stopping.
Q: What did the gap look like on the old CV?
A: A blank between 2021 and now. Reverse-chronological. Anyone reading it saw 4 years of nothing first.
Q: What did you change?
A: I led with a section called "Open-source and consulting during career break." It was real. I'd done a small Rust contribution to a CLI tool I used, and one paid Drizzle migration for a friend's startup. Two lines. Both real. Both measurable.
Q: Did you hide the gap?
A: No. It was still there. But it came AFTER something. The first thing the recruiter saw was that I'd been technical during the years, not absent from tech.
Q: How many applications?
A: 18 to get to 5 onsites. Two offers from the same week. I picked the one that didn't ask me to explain the gap. They'd already read the answer.

What changed? Liana stopped letting the gap be the first chapter of her CV. The four years became context, not a verdict.

Build yours →

INTERNATIONAL APPLICANT

I was applying from Lagos for US-remote roles. 0 responses in 8 months. Then 6 first-rounds in 10 weeks.

Daniel O., 27, Backend Engineer at a US Series C, working remote from Lagos.

You start to think it's the country on the CV. You're not wrong. Recruiters do filter. But the filter isn't always your country. Sometimes it's how the CV looks before the country is even read.
Q: What was the original CV doing wrong?
A: It looked like every other CV that hits a US-remote pipeline. Same format, same buzzwords, same generic "passionate engineer" line. The recruiter has 800 of those a week. Mine wasn't different enough to read past the location.
Q: What did you change?
A: I led with three specific open-source contributions and a Stripe-integration project I'd shipped for a Nigerian fintech that now processes ~$200k/month. Numbers. Specifics. Things that exist on GitHub or that have public URLs.
Q: Did being in Lagos still hurt?
A: Yes. Some companies don't hire outside the US for compliance reasons. But the ones that DO hire globally now had a reason to read past the location, because the work in the first third of the CV was the kind of work US engineers couldn't show.
Q: What's the takeaway for international applicants?
A: Recruiters don't reject your country first. They reject your CV looking the same as everyone else's first. Be the specific candidate, not the generic one. The country becomes the second filter, not the first.

What changed? Daniel made his CV impossible to skim past: measurable, public-URL'd, specific. The country was still there. It just stopped being the deciding chapter.

Build yours →

EX-BOOTCAMP / SELF-TAUGHT

I have no CS degree. I did a 12-week bootcamp 2 years ago. I got an offer from a Series B fintech this month.

Priya S., 25, Full-Stack Engineer, Berlin.

Every CV template I tried put 'Education' at the top. So the first thing every recruiter saw was '12-week bootcamp.' Then they stopped reading.
Q: How did the standard templates fail you?
A: They assumed education matters first. For people with a CS degree, that works. For me, putting "12-week bootcamp" at line 6 was sending the wrong opening signal. It was like saying "before we start, here's my weakness."
Q: What did you do instead?
A: I built the CV with Projects at the top. Three real projects from my bootcamp days that I'd extended after the program. Each with a public URL and three measurable lines: users / latency / GitHub stars. Then a "Self-taught path" section that turned the bootcamp from a credential into a story. Education ended up on page 2.
Q: Did recruiters push back on no degree?
A: Two of them mentioned it. Six didn't. The pattern: companies that hire on portfolios don't care; companies that hire on credentials do. The new CV moved me to the first kind of company.
Q: What worked?
A: Treating the bootcamp as a starting point, not the endpoint. "I learned the basics in 12 weeks. Then I shipped these things." That's a different story than "I did a bootcamp."

What changed? Priya stopped letting the credential-section be the first thing recruiters scored her against. Her shipped work became the credential.

Build yours →

Stories shared with CVHive users' permission. Names and identifying details have been changed for privacy.

Customer experiences represent individual outcomes. Your results may vary based on background, market, and effort.