About
Why this exists.
AI writes the code. What is left for engineers is the hard part: working out what broke, deciding what to do, and standing behind the decision afterwards.
The interview stopped looking like the job
LeetCode had its moment and still teaches something useful: you do not choose between an index and a cache without understanding complexity. But the problem that shows up on a Thursday night comes with no prompt and no known solution, and that is exactly where a senior engineer separates from someone who memorised patterns.
What we do
Every challenge hands you the system as you would find it: architecture, the code that matters, logs, metrics, config. Then you answer in writing what is causing it, what you would change, what that choice costs, and how you would know it worked.
Where we are
Challenges ship in English and Brazilian Portuguese. We are early. An interactive environment for running the broken system, more challenges, and the hiring side are all in the queue.
Talking to us
Challenge ideas, mistakes in a solution, criticism of the product: the contact page exists for that, and a person reads the inbox.