SharePoint Architect looks very good word but what exactly skills needed to be real Architect?
There is many companies that is not mature to understand what an architect do. They often write in the job description/profile that you should have worked with SharePoint 2013 for 7+ years… They think you are some kind of swiss army knife. Having all these skills that they require and what you list is not possible. Usually they get what they ask for, someone with 3-5 years experience that exaggerate/lie. Ofc there is exceptions but in general people don’t. To keep up all the skills needed over 5 year cycle there is no time to keep up with all details.Â
One important thing as an architect is to build the trust of the development team and get them to engage them self in the work. I always let them be involved in architecture work, design and technical details. Same with IT pro, they are the experts! Same with estimations. Bottom up estimations makes the one doing the task more engaged to deliver the task within the hours than if someone else have done it. I try to  involved to keep the solution together on a higher level and that the quality is correct and the trade offs you need to do.
I think the architect should work between business and IT (talk both languages and can translate between the two) and his responsibilities is to make views/descriptions that both the business and IT can understand, share & agree.
The key to be a good architect is not in the details, learn the things that always applies to all situations. The core and fundamentals that applies to all systems/platforms/techniques like patterns for reuse, testability, scalability, manageability etc. In the end everything is built on 1’s and 0’s! 😉
