Skip to content
experience

The take-home that took me a week and got ghosted

Kunal Bhatia@kunal_dsa

May 28, 2026 · 2 min read

Yesterday I created this topic. Today I am writing the story that is the reason it exists. It is 1 am and I am still a little angry about it, two years later.

Series B fintech. Recruiter call went well. Then the take-home arrived: "should take 4 to 6 hours". The brief:

  • A payments reconciliation service with a REST API
  • Unit and integration tests
  • Dockerfile and docker-compose
  • A README with design decisions
  • "Bonus: a small UI to view mismatches"

I logged my time in my spreadsheet (yes, I log everything). 31 hours over 7 evenings. I did the bonus UI because I thought it would make me stand out.

Submitted on a Sunday night. Monday: "Thanks Kunal, the team is reviewing!" Then nothing. I followed up after one week. Two weeks. Four weeks. Nothing. Three months later the same job was posted again on LinkedIn with the same description.

Bhai kya hi bolu. Scene was bad.

My rules for take-homes now

  1. Ask how it is evaluated and who reviews it before starting. If they cannot answer, that is the answer.
  2. Ask for a time box. If it is honestly more than 4 hours, ask whether it is paid or whether a live pairing round can replace it. Good companies say yes to one of these.
  3. Time box yourself and write a "what I would do with more time" section in the README. Reviewers respect judgement more than gold plating.
  4. Put it on your GitHub (unless they made you sign something) so the week is not wasted.
  5. Follow up twice, then move on. Your energy is better spent on the next application.

Post your take-home stories here. Question types and time spent, please, not the exact assignment. Let's at least make these weeks useful for the next person.

Get the best of #interview_horror weekly

One email each Monday with the most useful posts. No spam; unsubscribe in one click.

Comments

9

Sign in to join the conversation.

Sign in to comment
Rohit Verma@rohit_codes6 rep in Interview Horror Stories
31 ghante 😭 bhai tumne spreadsheet mein ghante bhi log kiye the? classic kunal. but rule 2 sabse important hai, 4 ghante se zyada = paid ya live round
2 net votes
Kunal Bhatia@kunal_dsa#2 in Interview Horror Stories
Obviously I logged it 😅 that is how I know it was 31 and not "around 30".
1 net votes
Jo Brennan@jo_ships2 rep in Interview Horror Stories
Founder perspective: if a take-home takes more than 4 hours, the company is outsourcing its indecision to candidates. We pay $300 for ours and cap it at 3 hours. Applications didn't drop.
0 net votes
Sam Whitaker@segfault_sam5 rep in Interview Horror Stories
"bonus: a small UI" is how they get free frontend work for the real product lol
1 net votes
Dana Kowalski@dana_ml4 rep in Interview Horror Stories
Rule 4 is good. My best portfolio piece is a take-home from a company that never replied. It got me two other interviews.
2 net votes
Nikhil Sharan@nikhil_twopointers#1 in Interview Horror Stories
Sorry yaar. This happens way too often. Rule 3 also shows judgement, reviewers like "here is what I'd do next" more than extra features.
1 net votes
Achieng Owino@achieng_devrel1 rep in Interview Horror Stories
Ghosting after a take-home should be a reportable offence honestly. At minimum send a two-line rejection. It costs nothing.
0 net votes
Ankit Khurana@faang_or_bust#9 in Interview Horror Stories
series B fintech asking for docker + tests + ui for free. should have walked at the brief. thats on you tbh
2 net votes
Kunal Bhatia@kunal_dsa#2 in Interview Horror Stories
Yes, I know that now. That is literally the point of the post.
0 net votes