Seven years of running this agency. One observation that doesn't fit any funnel: the same strong senior thrives in one team and leaves another after four months — same stack, same character. We're launching a separate research project to map that.
Seven years of running this agency. Hundreds of closed senior+ vacancies. And one observation that doesn't fit into any funnel and doesn't show up on any HR report. I'll tell it now and explain why we've launched a separate research project around it.
The same senior — same stack, same experience, same character — becomes a strong contributor in one team, and leaves another with a "not my fit" four months later. Not because the person got worse. Not because the second company is "bad". Because the team environment — its tempo, autonomy, management style, unwritten rules — didn't match how this person works.
Most ATS and assessment tools look at half the equation: the candidate. The team environment stays off-screen — at best, described in a job posting. We're building a product that tries to see the environment too. It's called The One.Pro.
Why we're doing this now
The cost of a wrong senior hire in 2026 ranges from €15K to €30K, easily. Direct costs: recruitment, onboarding, team productivity drag, lost product velocity. In a 100-person company at 15% turnover, the annual damage clears €300K.
The departure reason is almost always one of two euphemisms: "didn't work out" or "didn't match the culture". That's not a diagnosis — it's a symptom. Behind "didn't match the culture" hides anything from constantly slipping releases to a manager expecting autonomy where the person needs structure.
The One.Pro starts from a hypothesis: these "anythings" can be decomposed into parameters — measurable, observable, repeatable across teams. And compared with candidate parameters before the offer, not after.
What we call an "environment passport"
An environment passport is a structured description of how a team actually operates. Not what's written in the job posting. Not what the manager says in a candidate interview. What the person sees when they're in their third month on the job.
Five blocks in the passport:
- Tempo — how quickly decisions get made, how often priorities shift, how strict deadlines are.
- Autonomy — where the role has a "I decide" zone vs. mandatory approval. Often misaligned with seniority.
- Management style — goals, tasks, or instructions; expects initiative or expects results.
- Communication — sync or async, text or voice, density of meetings.
- Unwritten rules — what nobody tells the newcomer: what "normally urgent" means, whether early-leaving is OK, how errors are discussed.
The passport is built from one structured interview with the manager plus analysis of team artefacts — chats, retros, documentation. Two to three hours of consultant work.
Candidate profile
On the other side — the candidate. Not as a set of hard skills and lines on a CV, but as a set of behavioural markers: how they make decisions under uncertainty, what they do with disagreements, how they context-switch, what they consider "normal" workload.
Most of these markers come from text: CV, motivation letter, structured-question answers, interview transcripts. Not "AI magic reads between the lines" — linguistic markup against codebooks where every marker links to a source. If the system says "high autonomy" — there's a quote next to it.
Compatibility report — the actual deliverable
We don't compare "good person" vs. "bad person". We compare where the team environment and the candidate's behavioural profile overlap, where they'll friction, and how critical those frictions are for that specific role.
Example. A senior engineer with high autonomy and low tolerance for micromanagement arrives in a team where the CTO line-by-line reviews every PR. This isn't "bad candidate" or "bad team". It's a concrete friction in months 1-2 that's better discussed before the offer than dealt with after.
Why classic ATS doesn't see this
ATS manages the funnel: where the candidate is, how many stages, what status. Useful for process, but doesn't answer "what happens after hire". Assessment tools — Pymetrics, Bryq and Russian analogues — look at the candidate in isolation from the environment. All candidate-side.
Climate tools like Visier and Happy Job see the environment, but after the hire — via pulse surveys of already-employed people. Which is when the mistake has already cost money.
The remaining gap is: environment passport + candidate profile + pre-hire prediction with explanation. That's where we're going.
Why we can take this on
Seven years working in the exact segment we're building for — technology teams of 50-300 people. We've accumulated a corpus: interview transcripts, evaluation matrices, client feedback, adaptation histories where we can see how the hire actually played out.
This isn't just "a lot of data" — it's labelled material where we can see retrospectively which environment + candidate markers correlated with successful transitions vs. those who left in the first year. The One.Pro is an attempt to turn this operational base into a reproducible product.
Who we're inviting to the first pilot wave
We're opening the first pilot wave for:
- founders and CEOs of technology companies, 50-300 people;
- CTOs and engineering leaders who recently lost people in the first year;
- HRDs and heads of talent acquisition who want to move from "gut feel from the interview" to structured risk assessment.
What a pilot participant gets: environment passport for one priority role, profile for three candidates on that role, compatibility report per candidate, debrief with our analyst, and pre-hire recommendations. Timeline: 2-3 weeks from kickoff.
What's next
This is the beginning of a project, not its end. A lot of what's currently done by hand by a consultant we'll be moving into a software loop: NLP feature extraction, explainable scoring, case accumulation, model fine-tuning. That roadmap is a separate story we'll come back to in the blog.
Right now what we need most is pilot cases. The more team shapes we go through, the more precise the passport, codebooks and final report become. So the first wave is for those who are interested not just in receiving a service, but in participating in a project where the result improves with every new team.
If you're one of those — write us in Telegram or by email. We'll discuss whether your team fits the pilot and what we can do in the next 2-3 weeks.
We'll build an environment passport for one priority role, profile three of your candidates, deliver a compatibility report — pre-hire. Write to [email protected] to discuss format.
Apply for pilot →