Ashby Staff Software Engineer interview questions

First of all, for anyone in the future looking at this, look at the percentage of negative feedback on their software interviews and save yourself some time. However, if you are still not convinced keep reading. First interview with the HM (normally 30 mins, it was 15 for me cause he was late): That is mostly to access if you are a "Product" engineer. Usual background questions, as well as "tell me one time you did X", but oriented on product. Not too bad, but I can't say much cause it was only 15'. Technical Screening: You are put into a call with an Engineer, he/she shares the screen and they tell you to change add another filter in a section that queries the interviews. As an idea it's not bad, however, it obviously adds a small layer of complexity the fact that you have to direct someone on what to do through a Zoom screen share, in a codebase you've never seen. But again, it could even be a quite good way to interview if it wasn't for the ridiculousness of the codebase. You are presented with a monorepo of everything thrown together. Which could still be ok, If the code was actually good. After a decade working in the same language and framework in some of the biggest tech companies and some chaotic startups, in my opinion that was the most unnecessarily over-engineered, convoluted code ever. It is the definition of the mid-level engineer's peak on the Dunning Kruger effect, thinking everything should be abstracted just another level (25 levels in), and generalized even more, just to make everything reusable. Now if you are used to this or good enough or whatever and you made it through, well done on you! However, I can tell you that's not how codebases of even thousands of good engineers look like, and I would urge you to consider if that is the best use of your mental energy - playing a mental juggle of nested Russian dolls - OOP style. But that's my 2 cents. you do you. The positive thing I can say is that everyone was quite polite with me and you were provided with a decent amount of information about the process, though it's just fluff really, nothing that amounts to anything useful.