Show summary Hide summary
- How one hiring process turned into an 11-round marathon
- Why candidates say this crosses a legal and ethical line
- Industry reaction: from outrage to weary resignation
- Strategies for companies to avoid ethical pitfalls in hiring
- What open-source and licensing options mean for candidates
- Voices from the tech community and the broader hiring debate
A software engineer’s rejection email is drawing attention for how far hiring processes can stretch — and for what happened to the code he produced. After more than a dozen interview steps and a multi-day take-home task, the candidate was passed over and told the company would keep and use his submission. The message has reignited debates about tech recruiting, candidate rights, and the blurry line between assessment and unpaid labor.
How one hiring process turned into an 11-round marathon
The story began with a social post from an unemployed developer who said he sat through a very long sequence of interviews. The hiring funnel reportedly included a week-long project that required writing production-ready code.
Anglo-Saxon burial reveals “unprecedented” secrets: experts stunned by 1,400-year-old grave mysteries
What Your Instinctive Tree Choice Reveals About Your Personality—Experts Explain
Instead of a job offer, the final message thanked him for completing the “first phase” of interviews and for submitting the take-home work. Then came the surprise: the company told him his code would be merged into their codebase. They followed that with a rejection.
The combination of many technical rounds and a substantive take-home task is what upset people most. Candidates and observers called out the imbalance: applicants invest time and expertise, then get no pay and, in some cases, no credit.
Why candidates say this crosses a legal and ethical line
Many readers reacted by asking whether the company’s actions were lawful. The short answer: it depends on agreements in place and local laws.
- If a candidate signed a contract assigning IP or agreeing that test submissions become company property, the company may be within its rights.
- Without such an agreement, submissions typically remain the creator’s intellectual property, unless the work is explicitly licensed or sold.
- Employment and contractor rules vary by country and state, which complicates claims about unpaid work and IP ownership.
Legal exposure often hinges on paperwork: what the candidate signed, what the job posting promised, and whether the company represented the take-home as unpaid assessment or as work to be reused.
Practical steps candidates can take if this happens
- Preserve all communications: emails, job descriptions, and the submission itself.
- Check any agreements or NDAs you signed before submitting code.
- Ask the hiring team in writing to remove or stop using your work.
- Consider offering a license in exchange for compensation or attribution.
- Seek legal advice if the company refuses and the code is valuable or proprietary.
Industry reaction: from outrage to weary resignation
The post triggered a mix of disbelief and nods of grim recognition. Some social users suspected satire because the scenario seemed almost too exploitative. Others said similar things happen routinely in tech hiring.
Several commenters described their own experiences with multi-stage interview loops. One user said they walked away after learning they would be asked to work on enterprise code as a test. Another reported multiple phone screens followed by an expensive onsite trip.
What many shared was a sense of exhaustion. Candidates warned each other to set boundaries, call out red flags, and protect time that could be spent on paid work.
Strategies for companies to avoid ethical pitfalls in hiring
Recruiters and hiring managers can prevent controversy by making expectations and rights clear upfront.
- State whether take-home projects may be used in production.
- Offer compensation or a short paid trial for work that will be incorporated.
- Provide templates or agreements that assign rights only after compensation.
- Limit the number of technical rounds to respect candidate time.
Transparency and fair compensation reduce mistrust. When companies treat technical assessments as disposable, they risk public backlash and damage to employer brand.
What open-source and licensing options mean for candidates
Some responders suggested releasing disputed code under a permissive license. That approach can pressure a company or at least give the author control over how their work is used.
Common paths include:
- Licensing the submission under GPL or MIT and notifying the company.
- Requesting a takedown if the code is used in violation of an explicit agreement.
- Negotiating a retroactive license fee or attribution.
Licensing is not a silver bullet, but it can be a pragmatic step while legal remedies are explored.
Voices from the tech community and the broader hiring debate
Beyond legalities, the episode has amplified broader questions about recruiting culture. Is it reasonable to ask unpaid labor from job seekers? When does assessment become exploitation?
For many, the answer lies in balance: companies need ways to evaluate skills, and candidates deserve respect for their time and creativity. That balance requires clear policies, fair compensation when work will be reused, and limits on the length and intrusiveness of interview processes.
