Original listing text, shown exactly as published by the company.
Main Responsibilities
The main responsibilities include, but are not limited to
- Act as the primary technical interface with the client, engaging to understand future initiatives, business needs, and high-level technical requirements
- Contribute to the client's long-term technical roadmap, helping them understand the implications and feasibility of their plans
- Define the overall system architecture for the catalog value stream, including microservice boundaries, communication patterns, and technology choices
- Develop and communicate the long-term architectural vision for the catalog value stream, ensuring alignment with organizational and business strategy
- Identify and address potential conflicts or dependencies between the catalog value stream and other value streams
- Define security and compliance standards for the catalog value stream, ensuring all solutions meet regulatory and organizational requirements
- Define high-level tooling and automation standards for the catalog value stream, promoting consistency and efficiency across teams
- Conduct thorough technical evaluations of proposed technologies, including compatibility, scalability, and long-term viability, and present findings and recommendations to the Architecture Manager
- Facilitate high-level communication and collaboration between the different teams in the catalog value stream, owning the cross-team alignment agenda
Identify high-level areas where technical debt is hindering the value stream and provide strategic context and direction for resolution
- Drive strategic improvement initiatives and long-term architectural refactoring that affect the overall system
- Create high-level architectural diagrams and documentation for system-wide reference
- Provide direction on architecture-impacting changes when escalated, including significant refactoring with system-wide implications
We Expect Candidates to Have Knowledge In Some, But Not Necessarily All, of the Following
- Knowledge of non-functional requirements (performance, security, scalability, privacy, GDPR, etc.)
- Knowledge of Design Patterns, Clean Architecture, and Clean Coding principles
- Knowledge of microservices architecture and event-driven architecture (EDA)
- Knowledge of distributed systems applied to global, high-availability B2B applications
- Familiarity with API design and integration best practices
- Familiarity with Microsoft Azure services and cloud-native architecture patterns
- Knowledge of security and compliance frameworks applicable to global B2B systems…
