When people say technical ability they are often drawing a distinction between overall ability to engineer (which includes many technical and non-technical thin

When people say technical ability they are often drawing a distinction between overall ability to engineer (which includes many technical and non-technical things) and ability in some super specific area (C++ template metaprogramming wizard). It's a forest for the trees sort of thing. In my limited experience with former googlers and microsoft people, they came from environments that were so far removed from real customers and product feedback that their only measure of success was if they could impress their peers by using the very latest features of C++ move semantics, as opposed to architecting/building a scalable system that actually solved a customer problem. Literally I know of a startup that basically failed because the ex-microsoft guy spent most of this time building C++ $WHATEVER to get better performance on our i/o bound app and the ex-googler spent most of his time reorganizing the repo. They never got around to delivering software that they could iterate on. [edit] Both of those places are big companies, if you feel the need to respond with how you work at company X and your team is great at getting things done, you really don't need to bother. We get it, companies with tends of thousands of employees probably have many different subcultures.