Child route renders here
/app/vacancies · /app/v/:id · /app/settings
Eleven screens for in-house recruiters: cabinet → vacancy → candidates. High-density, frosted-cobalt surfaces, restrained chrome. Switch the variation to compare three working surfaces side by side.
/app/vacancies · /app/v/:id · /app/settings
Six new candidates analyzed in the last hour.
A clear description scores candidates better. Use a template if you'd like to start faster.
Be specific about must-haves. Better descriptions = better candidate scoring.
Start from a known shape, then refine.
8 yrs Go in payments at scale · led the migration of an event-sourced ledger to Postgres partitioning · open-source maintainer of go-idemp
Diff highlights: 5+ → 6+ yrs · + Kafka/NATS line · + on-call NTH
Edits create immutable snapshots. Existing candidates keep their score on the version they were analyzed.
Read-only · 5 vacancies · 117 candidates preserved
We'll score this candidate against the current version. If you re-score later on a new version, the old score is preserved.
Scored against Senior Backend Engineer · 2026 Q2 · maria_petrova_cv.pdf · 312 KB · 2 pages
8 yrs Go in payments at scale · led the migration of an event-sourced ledger to Postgres partitioning under live load.
Go · Postgres · Kafka · K8s · gRPC. Open-source maintainer of go-idemp. Public talks on idempotency.
Mentored 4 mids to senior. Cover letter is concrete and tactical, not buzzwordy. Conference speaker.
CS, MIPT (Russia). Also self-taught Rust 2023, evident from open-source contribs.
Junior → senior in 4 yrs at last role. Increasing scope: ledger → cross-team payments platform.
Strong written communication. Past startup → unicorn → indie OSS. Comfortable with ambiguity.
Strong match. Maria's direct experience in payments ledgers, comfort with Postgres at scale, and public OSS work line up cleanly with our must-haves.
The main calibration is comp band — her trajectory (junior→senior in 4 yrs) suggests she may be looking at staff comp by now. Lead with role scope before number, and confirm alignment in the first conversation.
Generated by Atlas v3 · GPT-4o · 14.2 s · 2026-04-22 14:47 UTC.
Three steps to your first ranked leaderboard. The vacancy you create now is the criterion every future candidate gets scored against.
Title · position · description. Templates available for the common shapes.
Drop a single PDF or batch up to 200. Pasted text works too.
Six weighted criteria · strengths · risks · re-rankable any time.
Profile · billing · integrations · preferences.
Up to 25 vacancies · 1 000 candidate analyses / month · 1 seat
Three steps to your first ranked leaderboard. The vacancy you create now is the criterion every future candidate gets scored against.
Title · position · description. Templates available for the common shapes.
Drop a single PDF or batch up to 200. Pasted text works too.
Six weighted criteria · strengths · risks · re-rankable any time.
A clear description scores candidates better. Use a template if you'd like to start faster.
Be specific about must-haves. Better descriptions = better candidate scoring.
Start from a known shape, then refine.
Drop a single PDF for a quick read, or queue up to 200 in batch mode. We'll score against the description you just saved.
tip · edit this vacancy later — only future candidates use the new version
First version of the vacancy. If you re-score later on a new version, the old score is preserved.
Scored against Senior Backend Engineer · 2026 Q2 · maria_petrova_cv.pdf · 312 KB · 2 pages
8 yrs Go in payments at scale · led the migration of an event-sourced ledger to Postgres partitioning under live load.
Go · Postgres · Kafka · K8s · gRPC. Open-source maintainer of go-idemp.
Mentored 4 mids to senior. Cover letter is concrete and tactical, not buzzwordy.
CS, MIPT (Russia). Self-taught Rust 2023, evident from open-source contribs.
Junior → senior in 4 yrs at last role. Increasing scope: ledger → cross-team payments platform.
Strong written communication. Past startup → unicorn → indie OSS.
Strong match. Maria's direct experience in payments ledgers, comfort with Postgres at scale, and public OSS work line up cleanly with our must-haves.
The main calibration is comp band — her trajectory (junior→senior in 4 yrs) suggests she may be looking at staff comp by now. Lead with role scope before number, and confirm alignment in the first conversation.