There are many types of software architects and companies expect them to play different roles based on the company and the projects. But I do believe the following bullet points are necessary for any software architect.
An architect maintains control over the architecture lifecycle
parallel to the project’s software development lifecycle.
An architect stays on course in line with the long term vision. When
project's scope creep attempts to manipulate software architecture
in a certain way in order to satisfy the desires of myriad
stakeholders the architect must know when to say "NO" to select
requests in order to say "YES" to others.
An architect progressively makes critical decisions that define a
specific direction for a system in terms of implementation,
operations, and maintenance.
An architect works closely with executives to explain the benefits
and justify the investment in software architecture of a solution.
An architect inspires, mentors, and encourages colleagues to apply
intelligently customized industry’s best practices.
An architect fights entropy that threatens architect’s structural
approach to problem solving.
An architect creates and distributes tailored views of software
architectures to appropriate stakeholders at appropriate intervals.
An architect acts as an agent of change in organizations where
process maturity is not sufficient for creating and maintaining
architecture centric development.