Expectation
Know big picture
Keep many different components at mind and see how they work
Know at higher level, not the low level
Management and developers look at you for the answer
Non functional requirement handling
Performance
Scalability
High availability
Will the change cause any bug?
Which part of software need change/refactoring for technical debt?
He is a teacher not the dictator
Training and upskilling team
Guide developers for solution
Reviews all major design initiatives
Collaboration with developer, management, product managers, operations and infrastructure engineers, other architects
Constantly listening and responding to feedbacks
Architect interaction with developer
Guide developers for solution
Reviews design proposal by developer considering big picture
Acts as teacher
Mentor
Shared vision with developers
Architect interaction with manager
Helps in evaluating performance of individual
Extension of management team
Train the team
Review plans for development team
Growth tips
Step back and learn
Reads about best practices
Attend conferences
Grow network with fellow architects
Be the scrum master of team you are tech leading help to drive the technical progress well
Books
Architecting for scale - Orielly - Lee Atchison
Keep holistic view of the solution
Gives the new suggestion for directing next level of solution
Understand product need
Understand customer need
Understand company roadmap
Look for architectural problems in your product
Types of architects
Development architect
Operation architect
Environment for architect
A motivated team