I was given an initial interview with the HR rep, and then an algorithmic technical screen which I passed. A week later, they scheduled the React test screening.
I probably could have looked over the requirements in greater detail, but it was confusingly worded and weirdly described. At one point, it said to submit the answer only when all the answers were invalid.
They had two software engineers look at it, which, in my opinion, made it more awkward. Instead of it feeling like a genuine conversation while I coded, it felt like they were just watching and criticizing. Also, it involved some use of an API I had never used, and one of the interviewers seemed annoyed with me that I didn't know it.
After I finished it, the interviewer told me he wanted a more generic solution, but the solution he described was incomprehensible. If they had asked for a generic solution, I would have given one, but I'm not a mind reader. I completed the React part of the screening.
Overall, not terrible, but far from a good experience. I don't think I was truly assessed well and wish they would have given a clearer, more succinct version of their problem. It is their loss though; I am an excellent UI engineer and exactly what they were looking for.
Implement a 3X3 captcha where you can only submit the invalid elements.
The following metrics were computed from 1 interview experience for the Ridgeline Software Engineer role in New York, New York.
Ridgeline's interview process for their Software Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Ridgeline's Software Engineer interview process in New York, New York.