Principal Architect

Responsibilities

• Collaborates and makes proposals across several teams on their engineering work, and helps their team members make informed decisions in alignment with the sub-department strategic plans.
• Proactively identifies opportunities to reuse or generalize existing services and product features. Avoids duplication of effort by encouraging collaboration.
• Exposes technology and organizational needs throughout their department.
• Teach, mentor, grow, and provide advice to other domain experts, individual contributors, across several teams in their sub-department.
• Play a central role in technical, business, and organizational contributions affecting the sub-department/department.
• Plan improvements and features with a 6 month view.
• Solves technical problems of the highest scope, complexity, and ambiguity for their sub-department.
• Interfaces with EMs and Senior Manager or above and enables Staff Engineers to engage on department-level aspects of larger (sub-department wide) initiatives.
• Looks for innovation opportunities between several teams with a willingness to experiment and to boldly confront problems of large complexity and scope.
• Proposes initial technical implementation which supports architectural changes that solve scaling and performance problems.
• Ensures that OKR level goals are aligned across several teams in their sub-department.
• Guides conversations to remove blockers and encourage collaboration across teams.
• Provides a point of escalation for sub-department teams facing complex technical challenges.
• Attain a measurable impact on the work of sub-department teams.
• Interact with customers and other external stakeholders as a consultant and spokesperson for the work of your sub-department.
• Exposes the work of the sub department and their business impact internally.
• Knowledgeable in all specialties practiced within the Department or Sub Department