• Define the platform architecture. Work with the MissionOS Product Owner to design the long-term vision for how infrastructure, runtimes, CI/CD, developer tooling, and self-service portals fit together into a cohesive developer platform. • Drive technical direction. Lead build vs. buy evaluations, architectural trade-off decisions, and integration design across multiple platform capabilities (pSDO, LSRE, Quiver, and future tools). You're the deep-dive technical voice that informs product decisions. • Partner with engineering teams. Work closely with engineering managers building individual MissionOS capabilities to ensure implementation aligns with the broader platform vision. Talk shop. Review designs. Solve integration challenges. • Move fast on emerging needs. Program teams need platform capabilities now. You balance long-term architectural consistency with the urgency of delivering value quickly. You know when to build for the future and when to ship something that works today. • Represent platform needs externally. Engage with corporate IT (CIOS), security (CIS), and compliance teams to ensure platform decisions align with enterprise standards, security requirements, and regulatory constraints. • Cover security and compliance. Ensure MissionOS platform decisions account for security, compliance, and operational risk. You speak confidently with security teams about how the platform addresses their concerns. • Enable self-service at scale. Design infrastructure- and policy-as-code patterns, golden path templates, and developer portal experiences that let teams provision environments, deploy applications, and access services without waiting for tickets.