Why I built Majken

When anyone can “vibe code”, it's harder to know who is a good developer hire.

I'm a senior developer and I hire other developers. These past years, the way we work has changed completely. Most code on my team now starts with an AI agent. The hard part of the job is now knowing if that code is good, smart and safe, and catching the small mistakes an agent makes.

The tests I used to send stopped telling me anything. A hard code challenge goes straight into Codex or Claude, and I learned nothing about how someone actually thinks. What I need to know is if someone can work fast with AI, with the skills to set clear requirements and not let small bugs, weak architecture or security holes through. And that they push back when something doesn't fit.

So I built the test I wish I'd had. A real spec, a pull request written by an AI agent, a few problems hidden in it. AI tools allowed, like on any normal workday. 25 minutes.

A wrong hire can cost months. Majken helps you avoid it.

Julia Wallin