You spent six hours on a take-home, got told your submission was "one of the strongest," and got rejected the same week. If you have been on r/recruitinghell or Blind recently, you have seen fifty versions of that story.
Here is what the 2026 data actually says, why the "strongest submission" line is usually literal instead of a lie, and how to decide whether to accept, negotiate, or refuse the next one.
The 45% number, and why it is worse than it sounds
Karat's 2026 engineering interview data says 63% of employers still run automated code tests and 45% still send take-home assignments, even as the format buckles under AI-generated submissions. Wonsulting's late-July 2026 piece adds a second number: of 51 top-tier companies with disclosed processes, 33% now include a take-home or async component, and the interview-to-hire ratio sits at roughly 27%. Roughly 73% of interviewed candidates walk away with no offer.
Stack those two facts and the picture changes. A take-home is not "one more step." It is unpaid work at the end of a funnel that has narrowed from 1-in-7 applicants reaching an interview in 2016 to 1-in-33 in 2026.
Down from 1-in-7 in 2016. Take-homes now sit at the end of a much longer funnel.
The Blind pattern that gave this article its title, "one of the strongest submissions we received, but we are moving forward with other candidates," is not usually a lie. Karat surveyed 400 engineering leaders across the US, India, and China and found 71% say AI has made it harder to assess real technical skill, and 62% of candidates already use AI during interviews even when disallowed. When employers cannot distinguish AI-authored from human work, they rank a strong pool and cut most of it. Strong is the floor now, not the ceiling.
The "strongest submission" rejection is a ranking artifact, not a lie
Read the recruiter literally. When they say your submission was one of the strongest, they mean it ranked in the top decile of an inflated distribution where everyone had AI, and they still had to cut 7 of 10 finalists.
The mechanism has three parts:
- AI floor-raising. HackerRank's 2025 Developer Skills Report puts AI usage at 97% of developers, with about a third of code written in 2025 already AI-generated. Everyone's take-home looks competent.
- Ranking, not gating. Employers used to use take-homes as pass/fail. They now use them as a forced ordering to pick 1 of 8, because everyone passes the "does it run" bar.
- Post-hoc resume filtering. On the Robinhood and HubSpot Blind threads, candidates report the hiring manager only opened the resume after the take-home landed. One Robinhood poster put it directly: the hiring manager did not look at the resume until after hours had been spent on the take-home.
That third point matters most. The take-home has quietly become a resume-avoidance mechanism instead of a skills test. The counter-play is not to work harder on the take-home. It is to make the resume so obviously on-target that the recruiter's incentive to send one collapses. That is the exact substitution Refolk makes cheap: paste the job posting, get your resume rewritten to answer the posting's specific asks, before you agree to anything unpaid.
Should you refuse the take-home? The answer depends on your function
Refuse if your skill is scarce. Accept, or negotiate, if your skill is oversupplied. Blanket "never work for free" advice ignores the supply asymmetry between roles, and that asymmetry is the whole game.
Here is the split from Refolk's US index of professional profiles:
| Cohort | US profile count | Notes |
|---|---|---|
| Software Engineers / Sr SWE with Python | 91,305 | Google, Figma, LinkedIn, Glean, Adobe lead |
| Product Managers + Product/UX Designers | 83,454 | Wonsulting flags these as most take-home-heavy |
| AI / ML Engineers (all seniorities) | 15,143 | ~5.5x smaller than the PM/design pool |
| Interviewed candidates who get no offer | ~73% | Derived from Wonsulting's 27% interview-to-hire |
Wonsulting specifically calls out that take-homes have "largely replaced" live coding and whiteboards for AI, PM, and design roles. Look at what that means against the supply data. The PM and design pool is 5.5x larger than the AI engineer pool. Employers can demand a free 6-hour project from PMs and designers because there are 83,454 substitutes. They cannot easily demand it from ML engineers because there are 15,143 total in the country and the frontier labs are already fighting over them.
Refusing a take-home works for scarce skills and backfires for abundant ones. The ethics are the same. The leverage is not.
So the decision framework:
- AI/ML engineer, staff-plus infra, security specialist: refuse or counter with a 45-minute paid conversation. Your pool is the 15,143.
- Senior SWE with a portfolio: counter with a public repo or a recent write-up that answers the same question. You are in the 91,305, but you have artifacts.
- PM, product designer, marketer, analyst, generalist operator: accept selectively, with time-boxing and IP protection built in. You are in the 83,454, and the market knows it.
The portfolio substitution that kills the take-home before it ships
The fastest way to skip a take-home is to hand the recruiter the artifact they were going to ask you to produce, before they ask. This works because the take-home's real function in 2026 is to force-rank finalists, and any pre-existing artifact of comparable quality collapses that need.
Concrete substitutions that have worked in recent Blind and r/recruitinghell threads:
- A GitHub repo with a README that mirrors a typical take-home prompt (data pipeline, small app, model eval) and a decision log at the top.
- A public case study, 800 to 1,500 words, with the tradeoffs section that most take-homes ask you to write anyway.
- A Loom walkthrough, 6 to 10 minutes, narrating a real project. Recruiters watch these at 1.75x and it still saves them the async review.
- A "portfolio instead of take home" line in your reply: "Happy to share three artifacts that answer the prompt directly. If those are not enough signal, I am open to a paid trial day."
The trick is getting the resume itself to point at those artifacts in a way the recruiter cannot miss. That is the exact work Refolk takes off you: paste the posting, get the resume back with the bullet order, keywords, and portfolio links reshuffled to match what this specific employer is screening for, plus a fit score that tells you whether it is even worth applying. If the score is low, refusing the take-home is easy. If the score is high, you have leverage to negotiate one.
How to negotiate a take-home without torching the offer
If you decide to accept, negotiate three things before you start: scope, time, and IP. Never all three at once. Pick the one that hurts you most and hold it.
Scripts that have landed on Blind without killing the process:
- Scope: "I can do the first 90 minutes of this and stop at a natural checkpoint. Happy to walk through what I would do next in the live round." Useful for Stripe, Ramp, or Faire style prompts that balloon past their stated time.
- Time: "Would a 48-hour window work instead of 5 days? I would rather do this in one focused sitting than spread it across the week." Signals seniority and cuts the scope creep employers get when they say "spend as long as you like."
- IP: "Can we agree in writing that the submission will not be used internally beyond the interview process?" The Boeing thread commenters floating wage-theft framing are a real hiring-brand risk to the employer, and most recruiters will just say yes.
- Payment: "I do paid trial days at $X. Would that work instead?" The ask itself repositions you even when the answer is no.
A recruiter on a Boeing-adjacent ML thread told a Blind poster that not wanting to do the unpaid take-home meant they should not be hired at all. That framing, "if you will not hustle, you are not the person," is worth remembering: it tells you exactly what the culture is before you sign. Use the take-home negotiation as a two-way signal. If they cannot handle a scope conversation, the job will not be able to either.
The transparent-AI submission now beats the "clean" one
Submit the take-home with an AI decision log. In 2026, a submission that hides its AI use looks more suspicious than one that documents it, and Karat CEO Mohit Bhende has publicly reframed the debate away from cheating and toward whether a candidate can direct AI at all.
The evidence:
- Meta ran a late-2025 CoderPad pilot with GPT-4o mini, Claude, and Gemini made available on purpose. The question flipped from "can you code" to "can you direct AI."
- Karat launched NextGen in December 2025, an AI-integrated live screen, effectively conceding that async take-homes as a clean signal are dying.
- 97% of developers use AI at work. A "clean" submission that outperforms that baseline reads as either dishonest or unrepresentative of how the person will actually work.
What to include in a transparent submission:
- A short README section: "AI tools used, prompts, and where I overrode the output."
- Two or three moments where you rejected the AI suggestion and why. This is the signal employers actually want.
- A tradeoffs section that goes past what the AI gave you.
The candidate who submits transparent AI-assisted work with a decision log now often outperforms the "clean" submission, because the clean one looks suspicious and the transparent one demonstrates the skill employers cannot test any other way: directing AI.
What to do this week
Three moves, in order:
- Audit your last three take-home outcomes. If two of the three ended in a "strongest submission" rejection, the take-home is not your problem. The resume-to-posting fit is. Refolk will tailor your resume to each posting and score how well you actually fit before you spend another six hours unpaid.
- Build one artifact. One public repo, one case study, or one Loom. It becomes your portfolio-instead-of-take-home offer for the next 20 applications.
- Draft your negotiation scripts. Scope, time, IP, payment. Have them in a note. When the take-home email arrives, you respond in 20 minutes instead of stewing for two days and then caving.
The take-home is not going away in 2026, but its signal is. The candidates who win this cycle stop treating it as an inevitable gate and start treating it as one negotiation point among four: resume, recruiter screen, take-home, and offer. Refuse when you can. Substitute when you have artifacts. Negotiate when you accept. And stop assuming the "strongest submission" line is a lie. It is usually true, and it usually still ends in a rejection, which is exactly why the fight has to happen earlier in the funnel.
FAQ
Is it legal for companies to use my take-home work internally?
The legal answer is murky and the practical answer is "assume they can unless you get it in writing." Most take-home terms are silent on IP. If the prompt asks you to solve a real business problem instead of a toy one, that is a signal to ask for written IP protection or a paid trial. Boeing thread commenters raising wage-theft framing are not wrong that the perception is a real hiring-brand risk, and most recruiters will agree to a one-line non-use clause if you ask.
How long should a take-home actually take in 2026?
Two to four hours of real work, capped. Anything longer is either scope creep or the employer using time-cost as a filter for desperation. If the prompt says "spend as long as you like," treat that as a 3-hour project and stop at a natural checkpoint with a written "what I would do next" section. Senior candidates who time-box and document their cutoff consistently outperform candidates who spend 12 hours polishing, because the 12-hour submission still gets ranked against everyone else's AI-assisted output.
Should I refuse a take-home if the recruiter has not read my resume yet?
Push back before you refuse. The Robinhood and HubSpot Blind threads document the exact pattern where the hiring manager did not open the resume until after the take-home was submitted. Respond with: "Before I invest the time, could we do a 20-minute call so you can confirm my background is a fit? I want to make sure the take-home is a good use of both our time." If they refuse, that is your answer about how the rest of the process will go.
What if my resume is the reason I keep getting funneled into take-homes?
That is the likely reason, and it is the fixable one. Take-homes get sent when the resume does not answer the recruiter's screening questions clearly enough to move you to a live round on its own. Fix the top of the funnel and the take-home either does not arrive or arrives as a formality instead of a filter.