Enterprise Architect

Your day tends to split between strategic planning and governance. You might spend the morning reviewing a proposed new system against the enterprise architecture roadmap, evaluating whether it aligns with standards and avoids creating redundancy. Then you might draft an architecture decision record, participate in a steering committee, or create reference architectures that development teams can use as starting points.

The role is heavily relational. You're influencing without direct authority over most of the teams you work with. Engineering teams, business stakeholders, security, and finance all have opinions about technology decisions, and your job is to ensure those decisions serve the organization's long-term interests, not just immediate project needs. This means a lot of persuading, negotiating, and sometimes being the unpopular person who says "no, that duplicates what we already have."

People who tend to thrive here are strategic thinkers with enough technical depth to be credible and enough diplomatic skill to be effective. If you enjoy seeing the big picture, can hold the complexity of an entire technology landscape in your head, and are comfortable advocating for long-term decisions that may not have short-term popularity, enterprise architecture can be deeply impactful. If you prefer building things over governing them, the advisory nature can feel frustratingly removed from the action.