Architect IV

Domino's Pizza, which began in 1960 as a single store location in Ypsilanti, MI, has had a lot to celebrate lately: we're a reshaped, reenergized brand of honesty, transparency and accountability - not to mention, great food! In the rise to becoming a true technology leader, the brand is now consistently one of the top five companies in online transactions and 65% of our sales in the U.S. are taken through digital channels. The brand continues to ‘deliver the dream' to local business owners, 90% of which started as delivery drivers and pizza makers in our stores. That's just the tip of the iceberg…or as we might say, one “slice” of the pie! If this sounds like a brand you'd like to be a part of, consider joining our team!

The Cloud Native Applications Architect performs the necessary analysis, technical design and build tasks related to the development of cloud native applications, the short- and long-term strategy for migrating existing applications in line with the overall cloud migration strategy. The CNAA provides technology solutions, direction, guidance and when necessary hands-on assistance for strategic projects and initiatives aligned with the public and private cloud strategies of Domino's Technology. This role is responsible for evaluating, recommending, and developing relevant technologies, tools, practices, processes, and solutions aligned with business strategy and priorities.

Responsibilities:

Application Architecture: 60%

• 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. Able to identify potential build vs. buy situations.
• Leadership. This role does not manage people, but this is an important technology leadership role. As a leader, the architect will be called on to:
  • Contribute to and influence the wider Commerce and DevOps architecture as an advocate for application concerns.
  • Mentor developers and make difficult decisions and trade-offs.
• 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 very senior developer background with a wide range of programming, design, and architecture experiences. Object-oriented languages are desirable. Also provides guidance and leadership 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, etc.
• 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.

Development: 40%

• Working Architect. This is a working architect role. Approximately 50% of the role is architecture and 50% is development.
• 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.

• Bachelor's or higher in Computer Science, Engineering, or software development-related field or equivalent combination of education and experience
• 10+ years of IT industry experience
• 5+ years of software development experience
• 3+ years of working in an application architecture role.
• Hands-on experience building and architecting Java-based frameworks, applications, and systems.
• Able to lead teams of software developers.
• Ability to troubleshoot and manage problems independently.
• Ability to set and meet deadlines and manage diverse tasks across multiple development work streams.
• Ability to interact with internal business customers and upper management.
• Demonstrated effectiveness in a fast-paced rapidly changing environment.
• Experience in developing across or integration with multiple languages and tech stacks.
• Experience with in-memory distributed data storage systems like memcache, Hazelcast, Redis.
• Excellent written and oral communication skills.
• Experience working in Agile Software Development methodologies.
• Hands-on experience and certifications in Microsoft Azure
• Hands-on experience in Container-based application architecture, specifically with Kubernetes
• Prior experience in foodservice or retail industry
• Experience with high-tech web development environments, startups, or eCommerce business units.
• Experience with mobile and web development.
• Experience with data platforms and analytics.

All your information will be kept confidential according to EEO guidelines.