FieldRoutes Software Engineer interview questions

There was an intro call with someone in human resources and then a technical interview was scheduled. The technical interview is 2.5 hours and consists of some intro time, then 1.5 hours of coding, and then a review of your code. I was iffy when I heard there was no matching 401k. But I went ahead. I learned during the technical interview that PestRoutes operates with no framework, no CI/CD pipelines, and no tests in place. I didn't wait to hear back from them. I emailed them shortly after and thanked them for their time, but let them know I was not interested. I've seen enough home-brewed architecture to know I don't want that again. Couple that with no CI/CD or tests is a hard no. It could be a great place to work. I have no idea of course and just having those things doesn't make everything perfect. But I'll take my chances elsewhere. A note if PestRoutes reads this. I think code exercises can be a valuable way to weed out candidates that don't fit your technical criteria. I personally don't find the pressure of doing X in Y time conducive. It's not how most developers code and therefore is not a natural assessment. If it's working for you then certainly keep it. I would go a different route.