Associate Application Architect III – @Retail

Job Description
The Associate Application Architect – @Retail performs the necessary analysis, technical design and build tasks related to the development of @Retail features. Provides technology solutions, guidance, and hands-on assistance for tactical and strategic initiatives aligned with the product roadmap of Domino’s @Retail ecosystem. This role is responsible for evaluating, recommending, and developing relevant technologies, tools, and solutions aligned with business strategy and priorities.
Main responsibilities
 
Development: 60%
 
Working Architect. This is a working architect role. Assignments related to hands-on development tasks are common.
Technical Design. Able to break down complex problems into manageable subcomponents. Understands and has applied best practices using design patterns, enterprise integration patterns and other industry standards. Needs to be able to balance the business needs and constraints with the best technical approach to achieve the most optimal solution.
Reusability. Understand when to build custom code and when to use reusable libraries and frameworks.
 
Application Architecture: 40%
 
Business Acumen. Relates business need and business value to craft a solution meeting the expectations and constraints of the business. Able to defend and/or promote the cost/effort justification for the architecture.
Compliance. Ensures that all team members are using the architecture as intended and are using it correctly. This is done through oversight and code reviews. Also understands how and when code needs to be refactored.
Technology. The architect needs to come from a senior developer background with a wide range of programming, design, and architecture experiences. Object-oriented languages are desirable. Also provides guidance for tool, environment, and other technology related decisions.
Quality. The frameworks and interfaces designed and implemented by the architect need to have a solid focus on supportability, testability, quality, and robustness.
Risk. A technical risk is typically a requirement that requires the project to implement an unknown, unproven, or untested technology. The architect identifies and understands technical risk and how to mitigate those risks. This is especially true for non-functional requirements such as performance and scalability.
Non-functional Requirements. Able to effectively architect solutions that take non-functional requirements into consideration. Requirements can include extensibility, maintainability, security, scalability, performance, among others.
Customer Support. May be called upon to interact with stakeholders to make sure their business needs are being met through the architecture and implementation.
Operations and Support. Ensure that the architecture is the right fit for production operations, support, and maintainability.