<p><strong>Summary</strong></p> <p class="x_x_MsoNormal" data-olk-copy-source="MessageBody">We are seeking a <strong>Principal Systems Engineer</strong> to play a critical role in aligning engineering execution with scientific and machine-level progress in the development of large-scale quantum computers.</p> <p class="x_x_MsoNormal" data-olk-copy-source="MessageBody">This role sits at the intersection of <strong>quantum science, hardware engineering, and control software</strong>, with a primary mission to make the system <em>coherent, buildable, and integrable</em> as it evolves. Unlike traditional product environments, many system requirements in quantum computing are <strong>discovered through experimentation</strong>, not defined upfront. Success in this role requires deep collaboration with scientists, rapid learning, and the ability to introduce structure <em>only where it accelerates progress</em>.</p> <p class="x_x_MsoNormal">The ideal candidate brings extensive experience building complex hardware–software systems (e.g., aerospace, EVs, robotics, advanced instrumentation) and is motivated to apply systems engineering rigor in a <strong>learning-driven R&D environment</strong>, pairing closely with internal quantum experts.</p> <p class="x_x_MsoNormal">This is a <strong>technical leadership role</strong> with broad influence across teams. Authority comes from clarity, usefulness, and trust — not from gatekeeping or heavy process.</p> <p><strong>Core Mission</strong></p> <ul> <li data-olk-copy-source="MessageBody">Bridge the gap between <strong>engineering tasks</strong> and <strong>quantum machine milestones</strong></li> <li>Make system architecture, integration status, and technical risk visible and actionable</li> <li>Enable scientists and engineers to move faster together by reducing ambiguity, friction, and rework</li> <li>Help the organization evolve from ad-hoc integration to disciplined, scalable system development — without slowing discovery</li> </ul> <p><strong>Responsibilities</strong></p> <p class="x_x_MsoNormal"><strong data-olk-copy-source="MessageBody">1. System Understanding Through Scientific Partnership</strong></p> <ul> <li>Work <strong>closely and continuously with quantum scientists</strong> to understand how the machine is actually operated, tuned, and debugged in practice.</li> <li>Spend significant time in the lab, observing experiments and participating in scientific discussions to absorb tacit system knowledge.</li> <li>Treat scientists as <strong>primary system knowledge holders</strong>, approaching requirement gathering as a learning and synthesis exercise.</li> <li>Build trust by accurately reflecting scientific intent and constraints in system models, requirements, and architectural decisions.</li> </ul> <p class="x_x_MsoNormal"><strong data-olk-copy-source="MessageBody">2. Requirements Co-Evolution & Traceability</strong></p> <ul> <li>Facilitate the <strong>co-evolution of system requirements</strong> as the machine progresses:</li> <ul> <li>Start with lightweight, provisional requirements</li> <li>Explicitly document uncertainty, assumptions, and open questions</li> <li>Refine requirements as experimental results and understanding improve</li> </ul> <li>Translate scientific goals (e.g., performance, stability, operability) into actionable engineering requirements while preserving necessary flexibility.</li> <li>Establish traceability between:</li> <ul> <li>machine-level goals</li> <li>subsystem requirements</li> <li>engineering deliverables (e.g., JIRA epics)</li> </ul> <li>Ensure engineers understand the <em>intent</em> behind requirements, not just the wording.</li> </ul> <p class="x_x_MsoNormal"><strong data-olk-copy-source="MessageBody">3. System Architecture & Integration Leadership</strong></p> <ul> <li>Develop and maintain a <strong>living system architecture</strong> covering:</li> <ul> <li>quantum hardware</li> <li>control electronics and firmware</li> <li>control software and orchestration layers</li> </ul> <li>Produce clear, accessible architecture diagrams that reflect reality and evolve with the system.</li> <li>Identify missing architectural elements, poorly defined interfaces, and integration risks early.</li> <li>Lead system-level trade studies and technical decision-making in partnership with engineering and scientific leaders.</li> <li>Ensure architecture reflects machine milestones and not just organizational boundaries.</li> </ul> <p class="x_x_MsoNormal"><strong data-olk-copy-source="MessageBody">4. Integration, Test Strategy, and Machine Protection</strong></p> <ul> <li>Define and drive a <strong>system integration and test strategy</strong> appropriate for an evolving R&D machine.</li> <li>Help ensure engineering testbeds match machine configurations as closely as possible.</li> <li>Push integration testing upstream so that machines are not used as primary test platforms.</li> <li>Partner with engineering teams to define validation criteria tied to real machine behavior.</