For companies

Who here can actually do it?

Most companies can't say who on their own payroll knows Kubernetes. MyMonday looks there first, then at the people you've worked with, and only then at everyone else.

What does the role need? Tap a few.

6

people could do this

  • 2 already work for you
  • 1 worked with you before
  • 3 more want to be found

Start with Kateřina, who already works for you.

KubernetesGo

An example cast of 26 made-up people, as if you were Vltava Digital. Nothing here is looked up.

Why now

Hiring turned into a pile.

Writing an application became free, so everyone sends more of them, and nobody believes the software that sorts them.

100 → 291

applications per hire, from early 2021 to the first quarter of 2026

Source: Ashby, recruiting benchmarks

70% · 8%

of hiring managers trust AI to make better hiring decisions, and of job seekers who call it fair

Source: Greenhouse, November 2025

Here: the people who fit, and why.

No pile to read. A ranked list the moment you post, with the reasons for every match, from people who wrote their own profiles.

Start inside

Your own people first.

A company of two hundred usually can't answer “who here knows Kubernetes” about its own payroll — and that is the cheapest hire there is, and the one nobody thinks to look for.

  1. Your peopleInvite your staff and the freelancers you already use, by email. When they fit a role, they're at the top.
  2. Worked with youEveryone you hire through MyMonday stays close. Next time, they're the second place you look.
  3. Everyone elseThen the people who want to be found, ranked on the same skills and levels. Widening is a step you take, not where you start.
An example: the people around one company.
  • Your people: Kateřina Horáková, Filip Marek, Tomáš Konečný
  • Worked with you: Petr Novotný, Markéta Fialová, Ivana Kučerová, Ondřej Malý, Tereza Malá
  • Everyone else: Anna Svobodová, Dominik Šťastný, Lea Brunner, Marek Havel, Oleksandr Kravets, Jan Procházka, Zuzana Krausová, Lucia Hrušková, Radim Černý, Simona Kratochvílová, David Kopecký, Eliška Dvořáková

One screen

Post it. See who fits.

Say what the role needs and how well, what it pays and where. Everyone who fits is ranked the moment you publish, your own people first.

New role

Title

Senior Platform Engineer

What it needs, and how well

  • Kubernetesmust-haveProficient
  • Gomust-haveProficient
  • TerraformCompetent
  • PostgreSQLCompetent
  • PrometheusAdvanced beginner

Pays

120 000–165 000 CZK/month

Where

Praha, or remote in the EU

An example. The yellow dot marks a must-have.

Senior Platform Engineer

Open
  • Kateřina HorákováYour people

    Senior Backend Engineer · Praha

    94% match Talking
  • Petr NovotnýWorked with you

    Platform Engineer · Brno

    78% match Interviewing
  • Dominik Šťastný

    DevOps Engineer · Praha

    91% match
  • Lea Brunner

    Site Reliability Engineer · Zürich

    69% match
An example: a role, a minute after it's published.

Every match explained

The same reasons, on both sides.

Your role and their profile meet one skill at a time. You see what came of each, and so do they — nobody gets a secret score, so the first conversation starts from the same page.

  1. Anna hasAnna hasExpert
    Kubernetes, a must-haveFitsalso written k8s, kube
    You ask forYou ask forProficientmust-have
  2. Anna hasAnna hasCompetent
    TerraformFits
    You ask forYou ask forCompetent
  3. Anna hasAnna hasPostgreSQL ·Proficient
    SQLFits — covered by PostgreSQL
    You ask forYou ask forCompetent
  4. Anna hasAnna hasCompetent
    Go, a must-haveBelow the level askedalso written golang
    You ask forYou ask forProficientmust-have
  5. Anna hasAnna hasnothing yet
    PrometheusNot on their profile
    You ask forYou ask forAdvanced beginner
  6. Anna hasAnna hasProficient
    LinuxDoesn't count here
    You ask forYou ask fornot asked for

The match

91% match

3 fit (1 through a skill that covers it), 1 below the level asked, 1 not on the profile — and you and Anna both see exactly that list.

  • Kubernetes and Go are must-haves. With either one missing from the profile, the role isn't matched at all.
  • SQL isn't on the profile, but PostgreSQL is — and PostgreSQL is an SQL database. So SQL counts, at the PostgreSQL level.
  • Linux isn't asked for, so it changes nothing here. It counts for the roles that ask for it.
  • How much each skill counts depends on the kind of role — a platform role leans on infrastructure. That weighting stays on our side.
An example: Anna and a Senior Platform Engineer role.

Reach out, talk, hire

Every conversation in one place.

Reach out with a line of your own, or answer the people who said they're interested. Each conversation moves through the same stages, and both sides see where it stands.

  1. Requested2

    • Lea BrunnerYou reached out
    • Radim ČernýInterested in the role
  2. Talking2

    • Kateřina HorákováYour people
    • Anna Svobodová3 messages
  3. Interviewing1

    • Petr NovotnýWorked with you
  4. Offer1

    • Dominik ŠťastnýOffer sent Monday
  5. Hired1

    • Marek HavelStarts 1 October
An example: one role's conversations, by stage.

Explainable by design

If someone asks why, you can tell them.

When software helps with a hiring decision, people expect an explanation — and in the EU, rules like the AI Act increasingly ask for one. Here it's on every match already.

  • People decide

    The software ranks and says why. Nobody is rejected by a machine; you choose who to talk to and who to hire.

  • Reasons you can show

    Which skills fit, which are below the level you asked, which are missing. The person you reach out to sees the same list.

  • The same rules for everyone

    Nothing about how a CV is written, where someone studied or what they look like goes into a match. Only the skills, at their levels.

What you won't get here

  • A pile of applications

    You get a ranked list with the reasons, not hundreds of CVs written by software.

  • Agency fees

    You talk to people directly. Nobody takes a cut of the rate.

  • Automatic rejections

    Nothing turns anyone down for you. People decide, with the reasons in front of them.

  • Paid boosts

    Nobody can pay to be seen first, and nobody can pay to hide from you.

  • Faceless candidates

    Real names on both sides, from the first message to the offer.

  • A score from nowhere

    Every match says why, in skills. We don't publish the weighting, so nobody writes to game it.

Questions

Asked before you post

What does it cost?

Nothing. MyMonday is free for companies hiring, and for people looking for work, while we're starting out.

How is this different from a job board?

You don't wait for applications. The moment you publish a role, everyone who fits is ranked against it with the reasons, starting with your own people, and you reach out to the ones you want.

Can I add the people who already work for us?

Yes. Invite your staff and the freelancers you work with by email. They're matched to your roles first, and everyone you hire joins them.

Will people who wrote a different name for a skill show up?

Yes. Spellings are one thing — k8s is Kubernetes. Skills that contain others are another: ask for PHP and the Laravel developers are in your list, ask for Excel and so are the people who wrote Microsoft 365. Each one's reasons say what covered the requirement.

Does an AI screen the candidates?

No. Software recognises skills when people type them and ranks matches by the skills and levels a role asks for. People decide who to talk to and who to hire.

Do the people I reach out to see the match?

Yes, the same match with the same reasons. They accept or decline, and if they accept you talk in one conversation.

Can people contact us first?

Yes. Someone who fits a role can tell you they're interested, with a line of their own. You accept or decline.

Real people. Real work.

Your next Monday is .

Know who could start by then. Post a role, add your team, or just look around.