the mechanics of automated matching · for the specialist we invited

a match across 20+ requirements — you cannot do that by eye

The email did not arrive because somebody was leafing through CVs. Before the email, automated matching checked your public HeadHunter profile against the project requirements — every point separately. Below is the whole run: what we read, what we matched and what happens if you reply.

source
profile on hh
matching
20+ requirements
response
a link to your hh CV
  1. step 01

    public profile on hh

    we read the same thing any employer does

  2. step 02

    matching across 20+ requirements

    every point is checked separately

  3. step 03

    match

    the match is assembled point by point

  4. step 04

    invitation

    an email with a match page and a breakdown

  5. step 05 · yours

    your reply

    as a link to your hh CV — or as silence

only the last of the five steps is yours. the first four happen without you.

01 · the run

What happens at each step

step 01 / 04

steps 01–03 happen without you

step 01 of 04 · cold sourcing

We find your public profile

There is one source — HeadHunter (hh.ru). We read the open CV: exactly what any employer sees on hh. Nothing private, nothing beyond the profile.

source
public profile on HeadHunter
what we read
only what you published in your CV yourself
what we do not do
we change nothing in your profile and send no responses on your behalf

How did you get my data?

what exactly is matched

Every requirement is its own line

Below is a full run over one project: 21 checks, each with its own mark. This is precisely what arrives in the breakdown attached to the invitation.

matched

17 of 21 checks

matching basis — 20+ requirements example matching complete — example data
01 matched

Seniority — senior

02 matched

Stack — Go

hh: “Go, gRPC, PostgreSQL”

03 matched

PostgreSQL — 4+ years

hh: “PostgreSQL in production since 2019”

04 not verified

Kubernetes in production

not mentioned in the profile — we will clarify when you respond

05 matched

gRPC and microservices

hh: “gRPC, microservice architecture”

06 matched

High-load experience

threshold in this example: from 10k RPS

07 not verified

English — B1+

the level is not stated in the profile

08 matched

Time zone — MSK ±2

hh: “Moscow”

09 matched

Availability — full time

hh: “full-time employment”

10 matched

Format — remote

hh: “remote work”

11 matched

Rate — within the project range

the expectation from the profile falls within the range

12 matched

Industry — fintech

hh: “fintech, payment systems”

13 matched

No relocation required

no move is needed in this example

14 not verified

Start — within a month

the start date is not stated in the profile

15 matched

Duration — 6 months or more

the profile shows project-based work

16 matched

CI/CD — GitLab

hh: “GitLab CI”

17 matched

Docker

hh: “Docker, docker-compose”

18 matched

Code review in a team

hh: “code review, a team of 8”

19 not verified

Kafka or an equivalent

no brokers are named in the profile

20 matched

Mentoring experience

hh: “mentor to two juniors”

21 matched

Calls in MSK hours

the time zone matches the team

“Not verified” means your profile says nothing about it. Such a point is clarified when you respond; it does not turn into a rejection and is not guessed at on your behalf.

the 20+ requirements themselves are not listed by the source — above is an example run over one project

Your invitation breakdown shows the same report for your project

Matching happens without you. Visit when a match has already occurred.

There are hundreds of sites you have to live inside: visiting every day, working through filters, applying dozens of times. Here the mode is different. While you work, automated matching checks profiles against projects; you step in at the last stage — when the match has already been assembled.

  1. 01 you read the breakdown — which points matched
  2. 02 you decide whether the project is interesting
  3. 03 you reply with a link to your hh CV — once

what is behind this public site

Behind this public site there is a working platform: it does have a vacancy catalogue and an account area. The difference is not the feature set but the mode.

  • Vacancy catalogue yes
  • Account area yes

You do not have to work through them by hand — but nobody makes you do without them either: drop in when a match has occurred.

we do not show platform screens on the public site — this page explains the mechanics, it does not walk you through sections

no email yet?

find me a project

Automated matching works the other way round too: leave your profile — it goes into automated search. Once a project matches, an invitation arrives with the same kind of breakdown as above.

Find me a project

one short form — three fields

  1. 01 A link to your hh CV or a file
  2. 02 Contact
  3. 03 Specialization

the list of specializations is not set by the source — in the form the field is filled in freely

iconicompany

outstaffing aggregator ·
project work for IT specialists

for companies Platform

Client sign-in is a separate page, not this site for specialists.

specification notes
  • only the account-area theme is taken from the imatching project — none of the account-area functionality is carried over
  • colours — from the imatching account-area theme
  • fonts — from the imatching account-area theme: Bricolage Grotesque · Public Sans · JetBrains Mono
  • register — “the air of a public site”, not the density of an account area
  • product type — landing, a public site
  • not an admin console
  • not a mobile app
  • reference for the product type — skillstaff.ru, and for the type only
  • the brand and styling of skillstaff.ru are not copied
  • the themes differ: our own product (this public site) and the engine (the “Platform” page)
  • our own product is IT outstaffing; this public site is built for it
  • the tender story is not surfaced on the home page — it lives on the “Platform” page

© 2026 iconicompany

responding — as a link to your hh CV · without registration