Back to jobs
New

Principal Systems Engineer – Quantum Computing Systems

Boston, MA USA

Summary

We are seeking a Principal Systems Engineer to play a critical role in aligning engineering execution with scientific and machine-level progress in the development of large-scale quantum computers.

This role sits at the intersection of quantum science, hardware engineering, and control software, with a primary mission to make the system coherent, buildable, and integrable as it evolves. Unlike traditional product environments, many system requirements in quantum computing are discovered through experimentation, not defined upfront. Success in this role requires deep collaboration with scientists, rapid learning, and the ability to introduce structure only where it accelerates progress.

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 learning-driven R&D environment, pairing closely with internal quantum experts.

This is a technical leadership role with broad influence across teams. Authority comes from clarity, usefulness, and trust — not from gatekeeping or heavy process.

Core Mission

  • Bridge the gap between engineering tasks and quantum machine milestones
  • Make system architecture, integration status, and technical risk visible and actionable
  • Enable scientists and engineers to move faster together by reducing ambiguity, friction, and rework
  • Help the organization evolve from ad-hoc integration to disciplined, scalable system development — without slowing discovery

Responsibilities

1. System Understanding Through Scientific Partnership

  • Work closely and continuously with quantum scientists to understand how the machine is actually operated, tuned, and debugged in practice.
  • Spend significant time in the lab, observing experiments and participating in scientific discussions to absorb tacit system knowledge.
  • Treat scientists as primary system knowledge holders, approaching requirement gathering as a learning and synthesis exercise.
  • Build trust by accurately reflecting scientific intent and constraints in system models, requirements, and architectural decisions.

2. Requirements Co-Evolution & Traceability

  • Facilitate the co-evolution of system requirements as the machine progresses:
    • Start with lightweight, provisional requirements
    • Explicitly document uncertainty, assumptions, and open questions
    • Refine requirements as experimental results and understanding improve
  • Translate scientific goals (e.g., performance, stability, operability) into actionable engineering requirements while preserving necessary flexibility.
  • Establish traceability between:
    • machine-level goals
    • subsystem requirements
    • engineering deliverables (e.g., JIRA epics)
  • Ensure engineers understand the intent behind requirements, not just the wording.

3. System Architecture & Integration Leadership

  • Develop and maintain a living system architecture covering:
    • quantum hardware
    • control electronics and firmware
    • control software and orchestration layers
  • Produce clear, accessible architecture diagrams that reflect reality and evolve with the system.
  • Identify missing architectural elements, poorly defined interfaces, and integration risks early.
  • Lead system-level trade studies and technical decision-making in partnership with engineering and scientific leaders.
  • Ensure architecture reflects machine milestones and not just organizational boundaries.

4. Integration, Test Strategy, and Machine Protection

  • Define and drive a system integration and test strategy appropriate for an evolving R&D machine.
  • Help ensure engineering testbeds match machine configurations as closely as possible.
  • Push integration testing upstream so that machines are not used as primary test platforms.
  • Partner with engineering teams to define validation criteria tied to real machine behavior.
  • Reduce burden on lab teams by improving pre-deployment testing and integration readiness.

5. Early Wins & Trust Building

  • Deliver small, tangible improvements early that directly reduce friction for scientists and engineers, such as:
    • clarifying a recurring interface problem
    • creating a simple integration checklist
    • documenting a failure mode that saves days of debugging
  • Use these wins to establish credibility and reinforce the value of systems engineering.
  • Continuously gather feedback on what is helping vs. slowing teams down, and adapt approach accordingly.

6. Unlearning, Adaptation, and Process Design

  • Actively identify where traditional systems engineering assumptions do not apply to quantum computing.
  • Unlearn rigid models around fixed requirements, early design freezes, and linear development.
  • Introduce process and structure incrementally, calibrated to system maturity.
  • Champion systems thinking without dogma — prioritizing outcomes over formality.

7. Technical Leadership & Mentorship

  • Serve as a technical leader and mentor for engineers and emerging systems thinkers.
  • Help scale system knowledge through documentation, diagrams, and internal education.
  • Contribute to leadership discussions on technical strategy, integration risk, and execution pacing.

What Success Looks Like

Within 6–12 months:

  • Scientists feel supported by engineering integration work.
  • Engineering efforts show clearer linkage to machine milestones.
  • Integration issues are identified earlier and resolved faster.
  • System architecture is widely referenced and trusted.
  • Leadership has improved visibility into system readiness and risk.
  • Machine milestones are achieved

Qualifications

  • 10+ years of experience in systems engineering or system architecture for complex hardware–software systems.
  • Proven experience integrating multidisciplinary systems (hardware, software, controls).
  • Strong background in requirements definition, interface management, and system integration.
  • Ability to operate effectively in ambiguous, fast-evolving R&D environments.
  • Exceptional communication and collaboration skills.

Preferred Qualifications

  • Experience in aerospace, automotive, robotics, advanced instrumentation, or similar domains.
  • Familiarity with model-based systems engineering (MBSE) concepts or tools.
  • Experience working closely with research or experimental teams.
  • Exposure to quantum technologies is a plus, but not required.

Personal Attributes We Value

  • Intellectual humility and curiosity
  • Comfort learning from domain experts
  • Bias toward clarity and usefulness
  • Strong listening skills
  • Pragmatic, outcome-driven mindset

Why This Role Matters

You will help build a machine that has never existed before — not by enforcing process, but by making the system understandable, integrable, and scalable. This role is foundational to turning scientific breakthroughs into reliable quantum computers.

QuEra is committed to cultivating a diverse work environment and is proud to be an equal opportunity employer. We highly value diversity in our current and future employees and do not discriminate (including in our hiring and promotion practices) based on race, religion, color, national origin, gender, gender expression, sexual orientation, age, marital status, veteran status, disability status, or any other characteristic protected by law.

#LI-NB1

Create a Job Alert

Interested in building your career at QuEra Computing, Inc.? Get future opportunities sent straight to your email.

Apply for this job

*

indicates a required field

Resume/CV*

Accepted file types: pdf, doc, docx, txt, rtf

Cover Letter*

Accepted file types: pdf, doc, docx, txt, rtf

Education

Select...
Select...
Select...
Select...
Select...
Select...
Select...

Voluntary Self-Identification

For government reporting purposes, we ask candidates to respond to the below self-identification survey. Completion of the form is entirely voluntary. Whatever your decision, it will not be considered in the hiring process or thereafter. Any information that you do provide will be recorded and maintained in a confidential file.

As set forth in QuEra Computing, Inc.’s Equal Employment Opportunity policy, we do not discriminate on the basis of any protected group status under any applicable law.

Select...
Select...
Race & Ethnicity Definitions

If you believe you belong to any of the categories of protected veterans listed below, please indicate by making the appropriate selection. As a government contractor subject to the Vietnam Era Veterans Readjustment Assistance Act (VEVRAA), we request this information in order to measure the effectiveness of the outreach and positive recruitment efforts we undertake pursuant to VEVRAA. Classification of protected categories is as follows:

A "disabled veteran" is one of the following: a veteran of the U.S. military, ground, naval or air service who is entitled to compensation (or who but for the receipt of military retired pay would be entitled to compensation) under laws administered by the Secretary of Veterans Affairs; or a person who was discharged or released from active duty because of a service-connected disability.

A "recently separated veteran" means any veteran during the three-year period beginning on the date of such veteran's discharge or release from active duty in the U.S. military, ground, naval, or air service.

An "active duty wartime or campaign badge veteran" means a veteran who served on active duty in the U.S. military, ground, naval or air service during a war, or in a campaign or expedition for which a campaign badge has been authorized under the laws administered by the Department of Defense.

An "Armed forces service medal veteran" means a veteran who, while serving on active duty in the U.S. military, ground, naval or air service, participated in a United States military operation for which an Armed Forces service medal was awarded pursuant to Executive Order 12985.

Select...

Voluntary Self-Identification of Disability

Form CC-305
Page 1 of 1
OMB Control Number 1250-0005
Expires 04/30/2026

Why are you being asked to complete this form?

We are a federal contractor or subcontractor. The law requires us to provide equal employment opportunity to qualified people with disabilities. We have a goal of having at least 7% of our workers as people with disabilities. The law says we must measure our progress towards this goal. To do this, we must ask applicants and employees if they have a disability or have ever had one. People can become disabled, so we need to ask this question at least every five years.

Completing this form is voluntary, and we hope that you will choose to do so. Your answer is confidential. No one who makes hiring decisions will see it. Your decision to complete the form and your answer will not harm you in any way. If you want to learn more about the law or this form, visit the U.S. Department of Labor’s Office of Federal Contract Compliance Programs (OFCCP) website at www.dol.gov/ofccp.

How do you know if you have a disability?

A disability is a condition that substantially limits one or more of your “major life activities.” If you have or have ever had such a condition, you are a person with a disability. Disabilities include, but are not limited to:

  • Alcohol or other substance use disorder (not currently using drugs illegally)
  • Autoimmune disorder, for example, lupus, fibromyalgia, rheumatoid arthritis, HIV/AIDS
  • Blind or low vision
  • Cancer (past or present)
  • Cardiovascular or heart disease
  • Celiac disease
  • Cerebral palsy
  • Deaf or serious difficulty hearing
  • Diabetes
  • Disfigurement, for example, disfigurement caused by burns, wounds, accidents, or congenital disorders
  • Epilepsy or other seizure disorder
  • Gastrointestinal disorders, for example, Crohn's Disease, irritable bowel syndrome
  • Intellectual or developmental disability
  • Mental health conditions, for example, depression, bipolar disorder, anxiety disorder, schizophrenia, PTSD
  • Missing limbs or partially missing limbs
  • Mobility impairment, benefiting from the use of a wheelchair, scooter, walker, leg brace(s) and/or other supports
  • Nervous system condition, for example, migraine headaches, Parkinson’s disease, multiple sclerosis (MS)
  • Neurodivergence, for example, attention-deficit/hyperactivity disorder (ADHD), autism spectrum disorder, dyslexia, dyspraxia, other learning disabilities
  • Partial or complete paralysis (any cause)
  • Pulmonary or respiratory conditions, for example, tuberculosis, asthma, emphysema
  • Short stature (dwarfism)
  • Traumatic brain injury
Select...

PUBLIC BURDEN STATEMENT: According to the Paperwork Reduction Act of 1995 no persons are required to respond to a collection of information unless such collection displays a valid OMB control number. This survey should take about 5 minutes to complete.