Obviously step 1) is mastering all the fundamentals of CS. Once you know all the fundamentals of CS, master your particular stack so deeply that you can use them at will like a toolbox for any situation that presents itself. try to learn as many proglamgs as possible as they all teach you different ways of thinking.

Assuming you have a decent handle on more advanced ds+a I would say if you want to be a 10x engineer, you have to put in the effort to become 10x better than your peers/mentors and it just requires being handed problems you don't know how to do and then using all of your mental focus and all of your energy to get it done as fast as possible while also ensuring that its the shortest bit of code that could conceivably satisfy its specification. You can imitate this by doing random coding challenges online. They are fairly difficult at first but over time you pick up the little trickery here and there that sometimes gets in the way of properly understanding what the problem is truly asking.

Have the hunger to go the extra mile even if you're tired and keep devouring every bit of information you can get your hands on, and constantly be resynthisizing the whole of what you know into a coherent set of facts based on evidence. Instead of lazily re-using the same patterns over and over question everything and determine from 1st principles whether something makes sense or not.

Output needs to be 10x more than the best "non-10x engineer" to really count.

Makes me wonder how many 10X engineers does Google [claim] to have?