Take-homes where AI is welcome.
A real task from your codebase, for engineering roles. Then a call about their own code.
Set it up in a chat.
Point Larpy at a merged pull request. It drafts the task, the tests and the answer key.
PR #2281 is a strong base: one hard decision (what is safe to retry without paying twice), real tests already in the repo, and small enough to cut to 90 minutes. Here is the plan.
- Task
- Retry failed payouts safely
- Level
- Mid-level backend
- Time
- 90 minutes
- They build
- The retry logic in
PayoutClient.send, with the queue and storage stubbed. - Scored on
- Correctness, safety under retries, rate limits, tests they add, how they direct AI.
- Answer key
- Acme’s merged code from #2281.
Use all the AI you want. We’ll show you how.
It records the task folder. Nothing else.
- No keystrokes and no other apps.
- One file candidates can read before they run it.
- A gap shows as a gap. Nothing is filled in.
- Hidden tests run after they submit.
Questions
Still have a question? Book a demo
How do we know the work is really theirs?
The code call checks they understand what they handed in. During the take-home, Larpy records the task folder and nothing else, and candidates can read exactly what it records before they start.
Can candidates use AI?
Yes. Larpy records which prompts wrote which code, then asks them about it. What they cannot explain counts.
Which languages work?
TypeScript, JavaScript, Python, Go, Java, Rust and Ruby.
Do candidates need to install anything?
One command, or a workspace in the browser.