An Architect on the HMS Architecture Team is responsible for defining, managing, and governing the architecture of a specific system area, aligned with Hivemind (HM) systems such as Pilot, Foundation, Forge, and Commander. They ensure seamless integration of their domain with the broader system architecture, balancing technical innovation with program objectives and customer requirements. The Architects will work with their HM counterparts to address any forthcoming challenges, before they become issues or risks for HMS programs. Architects must maintain a deep understanding of HMS program technical execution paths, feature needs, and develop a comprehensive approach to addressing both short- and long-term requirements while driving innovation. Serving as the central point of coordination ('belly button') for technical alignment between HM and HMS, architects convey how both organizations remain synchronized in their roadmaps and execution, actively participating in the joint Architecture Board. They are empowered through influence over the technical roadmap, systems engineering processes, and program execution strategies through collaboration with Chief Engineers. While Chief Engineers and System Engineers are responsible for the technical execution of their respective programs, the Architects are responsible for maintaining awareness, custody and governing the cohesive technical roadmap within HMS.
A Smarter and Faster Way to Build Your Resume