A very standard interview process, executed poorly: - Initial call with recruiter - 1-1 with Engineering manager - Take home challenge - 1-1 (which turned out to actually be with 2 people) technical interview which was solely to build upon said challenge - a fairly awkward experience. - Final interview The issue was with the challenge, which was fairly involved in terms of requirements - no code was provided to get up to speed quickly. The issue was that the challenge had a 3 hour time limit which essentially made building a backend to do api calls impossible - so corners had to be cut to make an API call in the browser (to avoid CORS issues) which resulted in using a service with a hard limit on requests (which I hit). The following technical chat built on top of what was essentially a hampered/hindered application. The service I used to make the api request again hit the limit during the interview, essentially breaking my application - meaning that I could no longer complete the challenge. This was extremely off putting and I felt myself getting flustered. For reference, this interview asked me to add recursion into the application and the person interviewing me had used the same service I did to get around CORS issues in his test (so I thought it was at least an acceptable decision). However this wasn't asked until we were around 80% through the interview meaning we ran out of time (irrelevant as my application had hit the request limit by this time). I think this interview could have been great, but Snyk should have provided a very basic backend and frontend to get started if their follow on was to build on top of it. Either than or completely remove the 3 hour time limit - I don't see any gain they achieve from putting this limit in, especially considering how involved the task was (writing "real" tests alone for an application of this complexity could easily take 3 hours). If they want to put the time limit in, then they should provide a basic application to get going.