The title
is not enough

A Software Engineer at a startupa banka scale-upa fintecha large enterprise

is not the same

Same title. Different outcomes

We analyze environments to send you the right candidates

Everyone reads the same CV
We read the context behind it

Job titles are noise. "Senior Engineer" means nothing without knowing: where, with whom, in what kind of company, at what stage

What recruiters see
Candidate profile
Software Engineer
5 years experience
PythonAWSDockerCI/CDAgile
This is all a traditional recruiter works with
Merky
What we see
Same title. Different world
BNP Paribas, Paris
Part of a 5,000-engineer org. Legacy Java stack. ITIL process. Change management boards. Waterfall delivery
CAC40Java / LegacyITILLow autonomy
Same title. Different world
Monzo, London
Scale-up, Series D. Go and Kubernetes. Microservices architecture. Full ownership of production. On-call rotation
Scale-upGo / K8sMicroservicesFull ownership
Same title. Different world
Stealth Startup, Berlin
Seed stage, 8 people. Python and React. Building everything from scratch. Wears all hats. Zero process, pure speed
Seed stagePython / React0 → 1All hats

We don't use the market's data
We build our own

Select a role. See the ontology our system builds around it

Role
Context

Owns everything alone. AWS, Terraform, CI/CD end to end. Decides architecture. On-call 24/7. The infrastructure is their product.

When a candidate comes to us,
we don't just read their CV

We scan. Layer by layer

Candidate profile
Sarah K
Senior Software Engineer · 6 years
PythonAWSDockerReactPostgreSQL
Company analysis

Works at a Series C fintech, 180 people

Engineering team of 35. Microservices. High ownership culture. 4 of her ex-colleagues went to scale-ups and stayed 3+ years

FintechSeries C180 peopleHigh retention
Colleague trajectories

3 similar profiles left in 2024, all joined scale-ups

Ex-colleague A → SRE at Datadog (still there). Ex-colleague B → Backend Lead at a Series B (promoted). Pattern: people from this team thrive in high-ownership environments

Scale-up patternLeadership pathHigh retention signal
Sectoral enrichment

"Senior Engineer" here = Staff-level elsewhere

In this company, at this stage, with this team size, her actual scope is Staff+. She owns 3 microservices, mentors 2 juniors, and leads architecture decisions. The title underrepresents the reality

Effective: StaffArchitecture scopeMentoringBest fit: Scale-up, 50-300
Profile enriched, ready for precision matching

We do the same thing on the company side

Who they hired. Where those people came from. Who stayed. Who left. What patterns emerge. We build a hiring DNA, not from job descriptions, but from reality

Ex-Datadog → joined as SREStayed 3 years
Ex-Stripe → joined as Backend LeadPromoted
Ex-startup (seed) → joined as DevOpsLeft in 6 months
Ex-Google Cloud → joined as PlatformStill there
Ex-consulting → joined as Eng. ManagerMismatch
Reinvent

We had to reinvent the wheel

Because the existing tools were built for a world where a title means something. It doesn't

0+
Skills normalized and clustered
0
Analysis phases per candidate
0+
Industries with sectoral context
0
One candidate, one role, the right place
“A job title says almost nothing. It erases the context, the environment, the trajectory, everything that makes someone thrive in one place rather than another. We built a system that rebuilds what actually matters: not to decide for you, but to make the invisible visible. The technology is complex. The result is simple: the right person, in the right place.”

Nicolas Loew, CTO & Co-founder, Merky

Jérémy

Jérémy Cohen

Founder, Merky

Add me. I'll look at your background, we'll talk, and I'll find you the place where you'll make a difference

WhatsAppQuick question? Text us
Email[email protected]