I coded the back-end for the borders of europe and it's basically CRUD. Okay, CRUD but distributed. Before that, I did commercial compilers - but the difficult parts were already built so it was just a matter of extending the grammar using what's already working pretty well. Before that - I did web development. Nowhere there did I do any concurrency, data structures, distributed software, nowhere did I need to know about computer architecture or any of the very difficult things I did in college - which prompted me to move away from web to seek bigger challenges, but in the end it's all CRUD, UI work, derivative extensions of already built codebases, fixing bugs and drinking coffee
I mean all I can say is come work in games - the technical challenges you will face will absolutely make you learn new skills. We wouldn't even hire someone who doesn't have good understanding of challenges of concurrency and performance optimization already. I've learnt this stuff at university but having to use it to make a game that runs at 60fps in a very constrained environment - that's the real challenge. Uni CS was super basic compared to that.
