Helia HR

Blog

200 CVs per opening is bad news for the employer too

2026-07-23 · Ihor Kosheliev, Founder, Helia HR

Hi everyone. I spent years as the product owner of an internal HR system at an IT services company, watching HR managers and accountants work with it every day. Now I'm building Helia HR, and I keep having the same conversation with founders of 10–50-person companies — so I'll write it down once.

The market flipped. Everyone noticed the wrong half.

DOU's 2026 job-market survey (part two here, 4,700+ respondents) says what every engineer already feels: searches run past two months, 44% of job seekers lowered their salary expectations, competition per opening is at a record.

Every founder I talk to reads this as good news: "finally, an employer's market." Post a vacancy — get 200 CVs. Great, right?

Here's the half nobody reads out loud: 200 CVs without a hiring process is worse than 20 CVs with one.

Why more CVs make small companies hire worse

It's not intuitive, so let's be honest about what actually happens in a 20-person services company when 200 CVs land:

  1. The screener is a delivery person. There's no recruiter. The CVs go to a tech lead or a delivery manager — someone whose hours are billable. Every hour they spend in an inbox full of PDFs is an hour a client didn't get. So screening happens "later". Later means never, or in one heroic evening with tired eyes.
  2. Screening debt compounds like tech debt. CV #7 looked decent on Monday. By the time someone answers on Friday of week two, CV #7 accepted an offer elsewhere — remember, the good candidates are exactly the ones whose search ends fastest, in any market.
  3. Ghosting burns the brand in a small pond. The Ukrainian IT community is a village. The 180 people you never answered will each tell three colleagues. In a candidate market they shrugged; in this market they remember. You're not just losing this hire — you're taxing every future one.
  4. Volume amplifies bias, not signal. Reading 200 CVs in one sitting, nobody evaluates candidate #147 on merit. They evaluate them on how tired the reader is. Sorting an inbox by "vibes at 11 p.m." is not a hiring bar; it's a random-number generator with extra guilt.

Reviewing 200 CVs by inbox is like debugging production through console.log: technically possible, practically painful, and everyone involved knows there's a better way.

What "a process" means when you're 20 people

Not a corporate TA department. Four things, none of which need a budget:

  1. One place where applications land. Not the inbox, not three Telegram chats. One list, one owner. If a CV can arrive in two places, it will get lost in both.
  2. A written screen, applied to everyone. Five questions per role, decided before you open the vacancy. Structured screening isn't bureaucracy — it's the only known cure for the "tired reader" problem, and it's the difference between comparing candidates and comparing your own moods.
  3. Scorecards after every interview. One page, filled in within an hour of the call, before interviewers talk to each other. If it's not written down, in two weeks your "strong yes" and your colleague's "meh" will both have become "I don't remember, seemed fine?"
  4. An answer SLA — even for the "no". Three lines, within a week, to everyone. It's employer branding that costs nothing — and in a market where candidates wait months for any signal, it's memorable precisely because it's rare.

And one thing to stop doing: don't post a vacancy "to see what the market has" if nobody owns the pipeline. That's how you manufacture 200 disappointed people and zero hires.

Do you actually need this?

Honestly — maybe not. If you hire once a year through referrals, a spreadsheet and good manners cover you completely. A process earns its keep when openings overlap, when more than one person interviews, or when the CV flow is bigger than one evening. Below that line, don't build machinery for a problem you don't have. The decision, as always, should be made through the lens of your own project's parameters — not because an article told you to.

Where the tooling fits (one honest paragraph)

I build Helia HR, where recruitment lives inside the same system as your people, projects and capacity — applications land in one kanban, AI parses the CVs into comparable profiles (a human still decides), scorecards are built in, and a hired candidate becomes an employee with an onboarding checklist in one click. If that sounds useful, the recruitment guide shows the whole flow. If a spreadsheet still covers you — genuinely, keep the spreadsheet.

The tooling isn't the point, though. The point fits in one line:

A process doesn't replace taste in people. It frees up the time to apply it.