That's just it, it's stuff you learn in computer science, then forget about because you don't use it in your day job.
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.
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.