3y
Thank you for the feedback. We made some recent changes to our interviewing processes, which have caused some confusion.
To clarify, this is an oversight on our part, and we do not expect candidates to spend two hours on a coding assessment/survey. Having been through interviewing processes myself, I can empathize with the frustration of companies disrespecting a candidate's time, and I have always made it a point to avoid such practices when hiring engineers.
The intended purpose of the survey was a brief, five-minute sanity check to assess coding skills in TypeScript. Typically, we conduct this assessment live during the phone screening, as it provides valuable insights into a candidate's problem-solving approach. However, in this particular case (due to the absence of an engineering resource on the call) we didn't. We also incorrectly labelled it as taking 2 hours.
As a result, we are immediately reverting these policy changes. Going forward, we will only ask candidates to complete a five-minute coding question during a technical interview, with another engineering resource present.
To the candidate: I am the CTO responsible for this situation and would appreciate the opportunity to chat and receive your direct feedback. You can reach me via email at john@iv.ai or schedule a call with me using this link: https://calendar.app.google/HEYYkpFVpCLdkEo38. However, I completely understand if you choose not to take this further.
