First I had a recruiter call, then hiring manager call talking about past experience, then coding interview where you tell an engineer what to do their machine. Overall silly. Not sure what else to say here.
You’ll be given a silly question to debug something in their codebase. But you need to tell another engineer sharing their screen what to do, so it just takes ages.
On top of that the problem you’ll need to debug will be something really silly like: an interface that is implemented by dozens of classes with different overrides. There is a reason why React no longer uses classes but functions and why most front end applications don’t rely on OOP. It’s because debugging them is tedious and absurd. You should not structure a FE application the same way you do a BE service written in Java.
The following metrics were computed from 2 interview experiences for the Ashby Senior Product Engineer role in United Kingdom.
Ashby's interview process for their Senior Product Engineer roles in the United Kingdom is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Ashby's Senior Product Engineer interview process in United Kingdom.