Your day job is writing CRUD services. That's the job.
Our tech interview - ~8 hour take-home assignment, it was well-paid consultancy - asked people to basically demonstrate they could write a CRUD service. It had reading XML, some business logic / calculations, a REST/JSON API and a front-end.
Ten years later, I'm still working with that basic model. I mean sure, it's been broken up here and there by a different tech stack (Angular instead of React, Go instead of Java, native iOS instead of web) but the basics are still the same.
I haven't had to invert a graph or do a depth / breadth first search since college. The most algorithmic thing I do is implement a comparator function for sorting.
People that are in their 40s aren't confused by the question but are more confused by why it's the question as being able to answer it is so disconnected from any metric of competency or quality.
It'd be like saying "so you have an engineering degree, oh a masters from 20 years ago. Cool, remember Lagrange multipliers and Hamiltonians? I'm sure you do. Here's a problem. You have 10 minutes"
That's why we keep seeing the failures of the past repeat. Tech selects for people too young to know it and too arrogant to study it.
I don't advocate for a free ride nor am I saying the tests are hard (they really aren't), just that they have a very weak correlation with building strong teams of the right people