Non-sarcastic question--how do you define "software architect"?
Typically the "architect" title I see thrown around today pertains to gluing together some abominations of "systems", typically cloud services to do web stuff at "scale"
Architect today seems == "cloud infrastructure decision maker" and has no bearing on the code written, libs/frameworks/whatever used
Infrastructure could be considered part of architecture but also, it should include other aspects such as how the code is organized on a per-project basis; what frameworks are used, how data should flow through the system, how the different modules are organized to form a functioning product that is resilient to requirement changes.
Typically the "architect" title I see thrown around today pertains to gluing together some abominations of "systems", typically cloud services to do web stuff at "scale"
Architect today seems == "cloud infrastructure decision maker" and has no bearing on the code written, libs/frameworks/whatever used