Software Architect

The primary role of the Engineering function within the Product Development team is to create specifications and designs for new products or improvements and enhancements to existing products. The Software Architect works closely with customers, developers, and other stakeholders to understand and define customer needs, translating them into scalable, maintainable, and forward-looking system architectures. Features are aligned to a timetable and areas of responsibility. 

The Software Architect serves as the technical authority for software systems — establishing architectural vision, defining standards, evaluating emerging technologies, and ensuring that design decisions support both immediate product goals and long-term platform evolution. 

Responsibilities 

The primary objective of the "Software Architecture" specialization within the "Engineering (PD)" Job Family is to define, govern, and evolve the software architecture that underpins our products, ensuring systems are designed to meet current and future business and customer needs. 

Architecture & Design 

• Define and maintain the overall software architecture for products and platforms, including system decomposition, component interaction, data flows, and integration patterns. 

• Create and maintain architectural specifications, design documents, reference architectures, and technical roadmaps. 

• Evaluate and select technologies, frameworks, and tools that align with business objectives, scalability requirements, and operational constraints. 

• Establish and enforce architectural standards, design patterns, and coding guidelines across engineering teams. 

• Design systems for non-functional requirements including performance, scalability, reliability, security, and maintainability. 

• Lead architectural reviews and provide technical governance for project designs and implementations. 

Technical Leadership 

• Serve as the primary technical authority and decision-maker for software architecture across one or more product lines. 

• Mentor and guide senior software engineers and development leads on architectural best practices and design principles. 

• Lead cross-functional technical discussions and drive consensus on architectural direction among diverse stakeholders. 

• Lead project teams to achieve milestones and objectives, providing architectural oversight throughout the development lifecycle. 

• Serve as a best practice resource within the engineering function and across the broader organization. 

Collaboration & Stakeholder Engagement 

• Work closely with Product Management, Engineering, Quality, Operations, and customers to understand and translate business requirements into architectural solutions. 

• Collaborate and communicate effectively with all stakeholders — technical and non-technical — to articulate architectural decisions, trade-offs, and rationale. 

• Network with key contacts outside own area of expertise, including industry peers, vendor partners, and academic researchers. 

• Create formal networks involving coordination among groups to drive cross-team alignment on shared platforms and services. 

• Solicit feedback from customers, developers, and operational teams regarding product usability, system b