Triplebyte does notionally allow you to apply (to Triplebyte) via a trial project. But it&#x27;s in addition to the interview(s), and the feeling they get from you during the interview trumps the project. They gave me the following feedback:<p>&gt; This was a tough decision and one that we were on the fence about. We really appreciate you taking the time to work on the take home project. We&#x27;re aware this requires a substantial time commitment and we are really grateful that you invested the time in completing it. We thought you wrote a great, very full featured [trial project]. It was especially impressive how much you dug into the academics behind [the project].<p>&gt; However we made the decision because we felt that while going through the project together during the interview, we didn&#x27;t see the fluency of programming when adding to it that we had hoped for. While we specifically designed the take home project track to help overcome the difficulties of coding under time pressure with someone watching, we do still need to see a certain level of programming during the interview. This didn&#x27;t seem to be the case here, where making changes to the project seemed to be slower and more difficult than we&#x27;d have liked.<p>tptacek had some advice for hiring-through-a-work-test that I (from my armchair) agree with, which is that it&#x27;s important to give everyone <i>the same</i> work test so your applicants are comparable. There&#x27;s a little bit of tension (I don&#x27;t think it&#x27;s unresolvable) between that and &quot;The test needs to be set up so that the candidate can demonstrate they can do exactly the same things all other employees do on a day-to-day basis, or it&#x27;s not a work-hire test&quot;.