Architect is a not-standard role in tech. Sometimes mean a thing, others a different one. That said, normally it's referred to people dealing with architecture

Architect is a not-standard role in tech. Sometimes mean a thing, others a different one. That said, normally it's referred to people dealing with architecture problems, not so involved with the specifics on a single system, but on the interaction of different ones. - If you want to plan to career to be architect, either ask for it if your company has this role or keep an eye on openings in other companies. - It's a work which involves a lot of communication. Create good design docs, convince people of your design and solve their doubts, get requirements of different parties to have a design that covers everything... - Learn about different languages and systems. Be able to see common structures (e.g. design patterns) and when to apply and when not... - Learn about "the support parts" of software. Logging, HA, scalability, deployment... Everything that makes a production system truly "production"