I don't have any work for you, but it would have helped if you had described your software engineering / computer science skills in more details. I'm not familiar with CLRS.
The acronym comes from its authors: (Cormen, Leiserson, Rivest, Stein)
You're almost certainly better off learning to code first and then learning about algorithms once you've got a decent coding level. In a typical entry level coding job you can easily go a whole year without implementing any algorithm more complex than a binary search (if that).
1. Domain knowledge (understanding the problems you are trying to solve, for who and why they need solving)
2. Full stack awareness (understand computer hardware, networking, OS, HTTP protocols, UI etc. AND whatever the core components of your domain are. This is crucial for being able to reason about and debug a running system.)
3. Technical communication in written and verbal form.
4. Programming fundamentals. Honestly I feel much more than "fundamentals" is a waste of time for new entrants. If you haven't been paying attention, GPT-3 has taken away the need for programming acumen for most creators. Prior to that Google+Stack Overflow got a whole lot of us through gaps in programming language expertise. Leetcode is literally just a proxy for formal education/privilege and has no direct application in daily work with the exception of a narrow few areas.
If you are truly a nuts and bolts person, let that be your domain. You could write a better inventory, search, and/or checkout system (wow bolts are easily stolen aren't they?!). You could also take the abstract mechanical intuition and focus on robotics.
One shouldn't aspire to work at a "tech company" - most of those that you might think of are actually ad companies. Following the analogy of 100 year old media, Googlers are out selling classified and yellow page ads in Search/Display, Netflix is a magazine publishing house, Amazon is the Sears-Roebucks catalog (Mail order homes!), Meta, the newspaper of newspapers. If you like sales, marketing, and influence it would make sense to work at such a place. I cannot tell you how many people are surprised by this, but it is vastly larger than it ought to be.
If you want to call yourself a developer/programmer/engineer/hacker then show up to build something that will run for a long time and not injure people during its operation. Build something better. If that isn't your ethos or ethic, there are better ways to make money.
I strongly disagree. GPT-3 is impressive technology, but it isn't even in the same universe as a team of sharp experienced developers. It is a valuable tool for them to use in some contexts, but it won't be replacing them anytime soon (at least not at a company I would work for).