Ghosted After Take-Home? Turn It Into a GitHub Playground
Don't delete unused take-home code—publish it publicly on GitHub, iterate with new patterns, and transform it into a showcase that attracts contracts elsewhere.
Extract Value from Wasted Effort on Take-Homes
Take-home assignments demand serious time investment, like a weekend building a full Android app spec: integrate Google Places API via raw HTTP (no SDK), handle location permissions, display nearby restaurants in list and map views, add search, and persist favorites. Deliver with single-module functional architecture, working tests, and a detailed README. Ghosting after submission—recruiter silence post-Sunday evening handoff—feels like total loss, tempting project deletion. Instead, recognize the code's inherent value as a ready-made foundation free from production constraints.
Iterate as a Safe Experimentation Hub
Make the repo public on GitHub immediately to shift mindset from failure to opportunity. Treat it as a low-stakes playground: layer in new APIs, libraries, and concepts before risking them in real projects. Avoid designing everything upfront; let organic evolution happen through repeated passes. This approach yields a polished three-module Clean Architecture app—modular, testable, and demonstrably robust—far superior to the original spec-compliant version.
Unlock Unexpected Career Wins
Repurposed take-homes become portfolio standouts that signal skills to future employers. The author's evolved project directly secured a contract at another company, proving ghosted work can pivot to tangible gains. This beats deletion by turning frustration into a live, growing artifact that showcases initiative, adaptability, and depth beyond interview checkboxes.