What is Kanvis?

Every hiring process starts with a document in which someone says things about themselves. The résumé, the profile, the cover letter. On the other side is a person with a stack of them, a role to fill, and no way to tell a true sentence from a generous one.

So they do the only thing they can. They stop evaluating and start pattern-matching. A company name they recognise stands in for the quality of the work done there. A title stands in for the scope of it. An unbroken run of dates stands in for reliability. None of that is what they actually want to know, but all of it fits in the time they have.

Candidates adapt, because they’d be foolish not to. You learn to write for the pattern. The keyword the filter wants, the title that maps to the one being filled, the phrasing that survives a six-second skim. The document drifts away from the work it’s meant to describe, and both sides have good reasons to let it.

You end up with a market where good work in the wrong shape loses to ordinary work in the right one. Everyone involved knows it, and nobody can fix it alone. That’s the problem Kanvis is built around. The problem isn’t that applying is slow or that there are too many applicants. It’s that the document at the centre of it all can’t be checked.

A Kanvis profile is built the other way round from a résumé. Instead of writing a document and hoping it’s believed, you talk. Upload a résumé or just describe what you’ve done, and that conversation is what builds the page. It lives at kanvis.me under a handle you choose, and there’s nothing on it but you.

The layout isn’t the important part. What matters is that every entry on the page can be traced back to the exchange that produced it. A recruiter reading about a project can see where the claim came from instead of taking it on faith. That’s the difference between a page about you and evidence of you.

It also lets the page be honest about its edges. Something you mentioned in passing looks different from something you described in detail, because the record behind them is different. Nothing has to be flattened into the confident tone a résumé forces on everything.

You decide what’s on it and who can reach it. A profile can be listed for search, or reachable by link only, which matters when you’re looking quietly and would rather your current employer didn’t know. It stays private until you say otherwise.

The most common failure in hiring isn’t rejection. It’s the question that never gets asked. A recruiter reads something interesting, has a follow-up, and weighs two options. Message you and wait a day for a reply, or move on to the next profile. The second costs them nothing, so that’s usually the one they pick.

A Kanvis profile closes that gap by answering. Someone reading it can ask about a gap in your dates, a tool you used once, a decision you made three jobs ago, and get an answer drawn from your record, whatever time of day they happen to be reading.

You don’t have to be involved, and you shouldn’t have to be. It’s your own account of your work, given once, doing its job while you’re asleep or at your current job or on a train. The reader doesn’t get a chatbot’s impression of you. They get what you said.

Once the record exists, the expensive parts of applying get cheaper. You can check how you measure up against a specific job before you spend an evening on it, and see which requirements you can back up and which you can’t. Better to know that before you apply than after you’re rejected.

You can have a résumé written against that one job description, in a format applicant tracking software can actually read, so the document you attach and the page you send agree with each other. Kanvis makes the file. Sending it is up to you.

And you can apply by talking. Instead of retyping your history into a form that asks for things your profile already contains, you answer a short set of questions about this role in particular. The hiring team gets your answers with the evidence behind them.

On the other side of the same hire, a team describes a role the way they’d describe it to a colleague, rather than filling in a posting template. What comes back isn’t a pile of applications to sort through.

Every applicant arrives already interviewed against that description and scored on the evidence behind their answers, on one board the team can question in plain language. The transcript sits a click behind the score, so a hiring manager who disagrees with a ranking can see exactly what produced it.

This is also what makes the candidate side free. Hiring teams are the customer, and they pay for the roles they have open rather than for how many people apply. It’s the only arrangement where nobody has a reason to want fewer applicants.

Kanvis evaluates. It shows what you’ve done, answers questions about it, and measures it against a role. It doesn’t act for you. It doesn’t write to employers, it doesn’t apply to jobs on your behalf, and it doesn’t negotiate, accept or decline.

That’s deliberate, and it’s not a gap we’re planning to close. An application sent by software is worth exactly what the person receiving it thinks it’s worth, which is very little once they suspect it. A page that answers for you is only valuable if the answers are yours.

So the things that stay yours are the ones that should. What goes on the page, what comes off it, whether it’s listed, when it goes public, which roles are worth your evening, and every word you give an employer.