It happens from time to time, but yes - there is no specific job / hiring for this.
The default/common path is evolving into the architect role which seems like a "bad" process of developing an architect.
The best way to develop a new architect, is to have him learn alongside a mentor/teacher who is an architect himself. Developing and architecture are very different jobs which require different mindsets and skills. Also, I've seen many places, teams, etc where people are mostly made to implement feature after feature with no time in between for learning, self-development, courses, etc.
Otherwise, after you've just "arrived" to that architect role you start learning on your own what architecture really is and means.
Developing and architecture are absolutely related. Many ideas seem great on paper till you go and implement them and find out the pain points. All the great architects have often been in the weeds of their systems.
The default/common path is evolving into the architect role which seems like a "bad" process of developing an architect.
The best way to develop a new architect, is to have him learn alongside a mentor/teacher who is an architect himself. Developing and architecture are very different jobs which require different mindsets and skills. Also, I've seen many places, teams, etc where people are mostly made to implement feature after feature with no time in between for learning, self-development, courses, etc.
Otherwise, after you've just "arrived" to that architect role you start learning on your own what architecture really is and means.