The interview process details can be found in their wiki, but in short: recruiter screening, take-home assessment, technical interview + other rounds that I didn’t get to do. The take-home assessment was pretty simple, I just had to do a code review. In the flow-up interview, I thought I did well since I implemented all my suggestions and verbalized my thoughts in a clear way, but I got a rejection email the next day.

Applied and forgot about it because a recruiter reached out to me one month later. So had a 30 minute zoom call with the recruiter. Asked me typical questions about my background and why I was in the market for a new position. After this I went on to the technical portion which was Merge Request review that I did on my own time. I was given access to this on Gitlabs where you need to review it and request changes for improving the Merge Request with the expectation of implementing these changes in a live coding session. It was pretty easy and was done in VueJS along with unit tests in Jest. The 90 minute Live Coding session went very smooth because I was well prepared and understood what the Merge Request was solving in the Issue tracker. But I focused too much on solving the Issue tracker and ensure it passed the unit test. So I failed the Live Coding session even though I thought I did amazing which took me off guard. The feedback I was given was that I need deeper experience in JavaScript and CSS. Also that I should look into working on a performance test on a VueJS app. - What I potentially missed - 1. I was completely tooken off guard, so I went back to look at the code and found two potential solutions in terms of performance. One was in the While loop, it could possibly turn into an infinite loop and maybe I should of limited retries to something small like 10 tries, but with how the conditional was setup it would at most only retry once or twice. Now if the conditional where to flip it could turn into an infinite loop. 2. Now what I did not think of was there was a method that ran upon button click which made an api call to an endpoint. I didn't think of this till after the interview, but in reality we did not need to make the api call over and over. We really either need to just call it once on mount and store it in the components data, or have a solution where the call happens once on button click and stored in the components data. Pretty mad at myself, hopefully future interviews might find this helpful but I really don't know if the two were the performance issues they were looking for, I do strong stand on the api call because you don't want x amount of the same request going out over and over. Now for the CSS portion I had no idea what they meant because part of the solution was to fix the view for mobile to match the mock and I was able to do this with media queries. Overall pretty easy interview process, but obviously not happy. As I have been interview in 2023 and 2024 I'm not liking these gotchas, I feel like its not representative in a one hour session. Its like they have a behind the scenes formula and hopefully you crack it.