Every candidate who makes it to our final round receives the same email: a take-home assignment, four to six hours, due by end of week, "to see how you think." We'd like to be transparent about something we've never said out loud in a hiring debrief: the assignment is not hypothetical. It is Q3's actual, unsolved, currently-on-fire problem, with the company name changed to "Acme SaaS" and a sentence added that says "there's no wrong answer here!"
There is, in fact, a wrong answer. The wrong answer is the one we're currently shipping.
How the assignment is written
Every take-home begins life as a real Slack thread. Someone on the team posts a genuine, unresolved question — "how should we restructure our pricing tiers," "what's actually causing this onboarding drop-off" — and three weeks later, with the thread still unresolved, someone in People Ops asks if it could become "a nice, scoped exercise for pipeline candidates." It is scoped. It is not solved. Those are different things, and the take-home assignment is the only format in business where that difference is treated as a feature.
"There's no wrong answer"
This is said in every assignment brief and has never once been true. There is a very specific wrong answer, and it is the thing our team already tried, already shipped, and is currently watching fail in production. When a candidate's take-home independently arrives at that same wrong answer, we do not update our internal strategy. We update the candidate's status in the applicant tracking system to "Not Moving Forward," while privately feeling a small, uncomfortable flicker of recognition, like seeing a photo of yourself from a weaker era.
The debrief
The hiring debrief for a take-home always includes someone saying, with real enthusiasm, "honestly, this is better than what we've been doing." This sentence is said out loud, in a meeting, about four hours of unpaid labor performed by someone who does not work here, is not being paid, and will find out about this verdict only in the form of a rejection email that says the team "went in a different direction," a phrase that in this specific case means "your direction, without you in it."
Why we keep doing this anyway
Because a real problem produces a real signal. A fabricated case study — "ReadRight.ai wants to increase retention, here's some fake data" — tells you whether a candidate can follow a worksheet. A real problem tells you whether someone can sit with genuine ambiguity, notice the thing your own team has been too close to see, and propose something you'll actually think about on the drive home. The ethical failure isn't using a real problem. It's using a real problem and not being honest that you did.
What we should be doing instead
Say what it is. "This is a live problem for us, your solution may genuinely inform our thinking, and we mean that as a compliment to the exercise, not a trap." One sentence. Nobody does it, because it makes the exercise sound exactly as consequential as it actually is.
Pay for it. Four hours is four hours whether it comes from an employee or a candidate. The fact that one of those four-hour blocks is currently free is an accounting trick, not a hiring philosophy.
Close the loop regardless of outcome. If the thinking was good, say so, specifically, even in a rejection. The candidate did real work on a real problem. The least owed in return is a sentence that isn't a template.
Our recommendation
Keep using real problems in interviews — they're the only ones worth testing against. Just stop pretending the "no wrong answer" framing is generosity rather than cover. The whole exercise works better, for both sides, the moment everyone agrees on what it actually is: a consulting engagement with an unusually bad rate.
If your last five take-homes were suspiciously specific to problems your team was already Slacking about, email us at contact@b2bsaas.guru. We'll help you write an assignment that's honest about what it's asking for. We will not, however, be doing it for free.