Earlier quoted context omitted.
>The ones I am thinking about are people who pick up new things absurdly quickly; pick up on patterns very easily; have general experience in enough domains to make quick connections; etc. That's my experience as well. Generalists are often the most productive people. A good generalist can often grasp the whole system faster than a niche programming language specialist. And you usually don't need those niche programm…
I hire at a FAANG for two roles where we specifically target generalists: Solutions Architect (design solutions for complex real-world problems) and Technical Solutions Engineer (last line of support for really gnarly cases). Both need people who can cover a lot of ground, and it's hard to be good at either if you don't have significant practical experience and can't traverse the stack from source code to tcpdumps if…
I have the title right now but it is a new one in the company and it is up to me to navigate really what it means for us.
EDIT: And are there any books or other resources you or you see Solution Architects recommend?