Take-Home Projects?

I recently did a take-home project for a company I'm interviewing with. Most take-homes are generally either a ZIP file sent via email, or cloned from a public repo. In most cases, the solution is sim

I recently did a take-home project for a company I'm interviewing with. Most take-homes are generally either a ZIP file sent via email, or cloned from a public repo. In most cases, the solution is simply emailed back in a ZIP file. In this case, the company asked me to upload my solution to a public GitHub repo on my personal account. Aside from the inconvenience of emailing ZIP files, leaving take-home projects and solutions on public repos exposes them to training by LLMs. For this project, it was immediately apparent that GitHub Copilot had seen the code before and began offering suggestions that closely matched the solution. (I turned Copilot off, so as not to risk submitting a solution that too closely matched previous submissions.) It got me thinking -- there has to be a better way of managing take-home projects. My idea is to copy the take-home project to a private GitHub repo, which an applicant is temporarily given access to. I'm seriously exploring the idea of building a GitHub integration to manage this. What are your pain points around take-home projects? Are they still relevant in an age of LLMs? For hiring managers, would your company be willing to pay for a tool to automate the process of administering and reviewing take-home projects? (I know there are tools such as CoderPad and others that handle coding assessments as well as take-home projects, but this would simply be a GitHub integration at a lower price point).