Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Handle the Take-Home Assignment in Interviews
Transcript
- Lucas: You apply for a role, you do a phone screen, you do a first-round interview, and then the recruiter says: 'Before we move forward, we'd like you to complete a short assignment. It should only take two to three hours.' Luna: And you know it's going to take five. At least. Probably more like eight. Lucas: Right. And you have no idea if anyone's actually going to read it. That tension — between wanting to show your best work and not wanting to get exploited — is real. Today I want to talk about the take-home assignment as an interview tool: when it works, when it doesn't, and how to protect your time. Luna: I have a friend who spent a full weekend — probably twenty hours — building a marketing strategy deck for a startup. She submitted it on Monday. She never heard back. Not even a rejection. Lucas: That's brutal. And it's surprisingly common. A 2025 survey from the recruiting platform Greenhouse found that 42 percent of candidates who completed a take-home assignment never received any feedback on it. Not even a template email. That's almost half. Luna: Forty-two percent. So there's a good chance your work goes into a black hole. But at the same time, some companies genuinely use these assignments to evaluate how you think. How do you tell the difference? Lucas: I think you start by asking a simple question before you accept the assignment: 'Can you tell me how this assignment fits into the overall hiring process, and who will review it?' If the recruiter gives you a vague answer — 'It'll be reviewed by the team' — that's a yellow flag. If they can say, 'The hiring manager and two team leads will score it against a rubric, and you'll get a debrief call within a week' — that's a green flag. Luna: A rubric. That's key. If they haven't even thought about how they're going to evaluate it, your effort is a donation. Lucas: Exactly. Another thing: ask about the expected time commitment upfront. And if the recruiter says something like 'three hours,' I'd clarify whether that's the company's estimate or the average time candidates actually spend. Because there's often a gap. Luna: And if the assignment genuinely feels like it would take longer than their estimate, do you push back? Or do you just do the extra work? Lucas: I think you push back — but diplomatically. You can say something like: 'I want to make sure I'm delivering something useful within the time frame you've suggested. Could you help me narrow the scope? For example, should I focus on one business segment, or cover all three?' That shows you're thoughtful and respectful of their constraint. Luna: That's smart. You're not saying 'this is too much work,' you're saying 'help me prioritize.' I did that once for a product management assignment. They wanted 'a full go to market plan for a new feature.' I asked if they'd prefer a deep dive on the customer segment or a broader overview. They chose the segment, I spent four hours instead of twelve, and I got the job. Lucas: That's a great example. And it points to another rule: scope your own work. Even if they don't give you guidance, you can define boundaries in your submission. Write a one-sentence assumption statement at the top: 'This analysis focuses on the North American market using publicly available data from Q1 2026. I've capped the recommendations at three priorities.' That tells the reviewer you know how to manage constraints. Luna: And if you submit a thirty-page deck, they're probably not going to read it anyway. So you're actually helping yourself by keeping it tight. Lucas: Exactly. Another tactic: time-box yourself. I know a data analyst who got a take-home to analyze a sales dataset. He set a timer for exactly three hours. When it went off, he stopped and wrote a one-paragraph summary of what he would have done with more time. The hiring manager told him later that the summary was what sealed the deal — it showed he could prioritize and communicate trade-offs. Luna: That's brilliant. It's like a 'pause button' for the assignment. You deliver something concrete and also show your thinking. Lucas: Now, there are some assignments that are just bad signals. If the assignment asks you to produce work that looks like it could be used directly by the company — a detailed marketing plan, a competitor analysis with proprietary data, actual code that solves a real problem — that's a red flag. I've seen companies post 'interview assignments' on Upwork. That is exploitation. Luna: Especially for creative roles. I've heard of designers being asked to redesign the company's homepage. That's not an interview, that's a spec project. Lucas: Exactly. So how do you protect yourself? One thing you can do is add a footer to every page of your submission: 'Confidential draft prepared for interview purposes only. Not for distribution or commercial use.' It's not a legal guarantee, but it establishes a boundary. And if the company pushes back on that, you have your answer. Luna: What about the flip side — when you're the candidate and you really want the job? Do you ever just eat the extra time? Lucas: Sure, sometimes. If it's your dream company and the assignment is reasonable, maybe you invest more. But I'd still set a hard maximum. For a mid-level role, I'd say five to six hours is the ceiling. For a senior role, maybe eight to ten. If an assignment would take longer than that, something is off. Luna: I think a lot of listeners have been in this situation. And honestly, it's one reason we keep doing this show ad-free — to help people navigate stuff like this without someone trying to sell them a course or a service. Lucas: That's a good point. We don't run ads on Interview Prep because it's about your career, not about our revenue. If you find episodes like this useful and want to support that choice, there's a link at buy me a coffee dot com slash fexingo. No pressure, no perks — just a way to keep it going. Luna: Exactly. And now back to the assignment: let's talk about what happens after you submit. You've sent it. A week goes by. Nothing. Lucas: I think you follow up once, politely, after five business days. Say: 'I hope you had a chance to review the assignment. I'm still very interested in the role and would appreciate any feedback.' If you get radio silence after that, you have your answer. And honestly, a company that ghosts you on a take-home assignment is probably not a great place to work anyway. Luna: So it's also a screening tool for the candidate. You learn something about the company's culture. Lucas: Exactly. And one more thing: if you do get feedback, pay attention to how it's delivered. Is it specific? Does it show they actually engaged with your work? That tells you more about how they treat employees than any mission statement ever will. Luna: Alright, so to wrap it up: ask about the process and expectations upfront, scope your own work, set a time limit, add a confidentiality footer, and use the follow-up as a signal. That's a solid framework. Lucas: And always remember: the assignment is not just them evaluating you. You're evaluating them too. If they respect your time, that's a green flag. If not, you know where you stand. Luna: Next time, I want to talk about how to handle technical tests when you're not a strong coder but the role is more about architecture. Lucas: That's a good one. We'll get into that. For now, thanks for listening — and we'll see you in the next episode.