Menu

Before we had users, we wrote the CVs ourselves
πŸ“°

Before we had users, we wrote the CVs ourselves

DEV Community: careerΒ·JagritiΒ·about 4 hours ago
#wBOyn62Q
#devtocareer#devto#dev#pool#test
Long article (2321 words) β€” no AI summary yet.
Reading 0:00
15s threshold

kandidate.ai matches an engineer's CV against live tech jobs in Germany, in English or German. Early on we hit the problem every search product hits: how do you know the results are good before people use it? On day one you have job ads and nothing else. So we turned job ads into test candidates. We took a real job, built a strong-fit candidate from its own title and skills, and checked whether the matcher put that job near the top. A CV built from an ad should find that ad.

Making test data without users turned out to be the easy part. Keeping the measurement tied to what we actually serve was harder, and our own numbers fooled us three times:

A test harness printed results for four scoring versions while measuring a ranker no user was served.

Four in five rows in our served lists shared their score with another row, so retrieval order, not the score, decided their place.

Giving the ranker 500 candidate jobs instead of 300 made the top 100 worse.

How the matcher works

CV ──► parsed profile (titles,…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.