Here's how you can transition into system architecture using your previous experience.

Some point could be: -Understand System Architecture Fundamentals: -Acquire Technical Skills. -Gain Experience with Design Patterns -Develop Soft Skills -Work on Projects and Gain Practical Experience -Stay Updated and Continuously Learn

You're role will be between the engineering team and businesses team. You need to understand the business domain language very well. Next step will be to translate business needs into a process design with Event Storming or similar methodology. You need to know about typical performance bottlenecks in infrastructure and technologies that will limit your designs. Your excellent coding skills will be useful when prototyping of proposed architectural concepts will materialize. All that knowledge and experience you gain along your career path as software developer will be useful for software architecture. Stay in the team and close with the code don't follow the ivory tower path.

Books are best as an introduction to software architecture world. For me following two titles are industry must have: Clean Architecture: A Craftsman's Guide to Software Structure and Design By Robert C. Martin Software Architecture: The Hard Parts by Neal Ford, Mark Richards, Pramod Sadalage

Model systems that are existing in your company. Follow the design process and understand why they were designed in that particular manner. See the trade-offs. Point the parts of the design that are troublesome to maintain or change. After your architectural sandbox, step up your game with cooperating with software architects in your company. Watch, listen and learn. When you gain some confidence go and participate in Architectural Kata. If you can't find any in your hometown you can propose to organize them in your company. The best way to master the Software Architecture craft is practice.

To build your network of software architects in most efficient way you must attend local meetups. Ask questions about their presentations. Maybe catch them after the meeting and have a chat. If your knowledge is good enough you can attend those meeting in a role of a speaker. Prepare a presentation about certain topic that you comfortable with. Maybe lesson learned slides about fail deployment of some architectural pattern that your company did. Networking is a king to find a mentor first, and to find a job as a Software Architect in the second step.

Maîtriser l'architecture système nécessite des compétences dans divers domaines (os, réseau, protocoles, intégration...), tant infrastructure quand ingénierie. Outre des compétences en spécification, documentation... et l'application de l'état de l'art.