Senior QPU Design Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes "About IonQ" and "The Role". We should not repeat job title as heading. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We have content: About IonQ (company description). That could be "About the role"? Actually "About IonQ" is company overview, not role. Could be "About the role"? The posting says "The Role:" then description. We could treat that as "About the role". But we need headings: maybe "About the role" for the paragraph describing role. Then "Responsibilities" list. Then "Requirements" list. Then maybe "Qualifications"? Not separate. Could combine. Also "Pay" section: they have US Salary Banding: $124,000 - $186,000 and Wage Transparency: £75,200—£112,800 GBP. Also mention compensation varies etc. That's specific content, so include Pay section. Benefits: they list comprehensive medical, dental, vision, matching 401(k), unlimited PTO and paid holidays, parental/adoption leave, legal insurance, home technology stipend. So Benefits section. Schedule: not mentioned. So omit Schedule. We need to remove boilerplate: EEO, legal, application instructions, etc. Also remove duplicated lines. Also remove navigation etc. We need to preserve all substantive info. So include company description, role description, responsibilities list, requirements list, pay, benefits. We need to format as HTML fragment: use

for each section heading, then content:

for prose,

• for lists. We must not include job title heading. Also not include Job ID etc. Let's extract content: About IonQ paragraph: "IonQ, Inc. [NYSE: IONQ] is the world's leading quantum platform and merchant supplier - delivering integrated quantum solutions across computing, networking, sensing, and security. IonQ's newest generation of quantum computers, the IonQ Tempo, is the latest in a line of cutting-edge systems that have been helping customers and partners including Amazon Web Services, and AstraZeneca achieve 20x performance results and accelerate innovation in drug discovery, materials science, financial modeling, logistics, cybersecurity, and defense. In 2025, the company achieved 99.99% two-qubit gate fidelity, setting a world record in quantum computing performance. Headquartered in College Park, Maryland, IonQ has operations in California, Colorado, Massachusetts, Tennessee, Washington, Italy, South Korea, Sweden, Switzerland, Canada, and the United Kingdom. Our quantum computing services are available through all major cloud providers, while we also meet the needs of networking and sensing customers across land, sea, air, and space. IonQ is making quantum platforms more accessible and impactful than ever before." That's substantive. The Role description: "We are looking for a Senior QPU Design Engineer to join our Processor Design team at Oxford Ionics, now part of IonQ. You will be responsible for integrating all the features required to operate our quantum computers into complex chips, contributing to the team's mission of advancing the design of high performance quantum processing units. You will work closely with scientists and fabrication engineers to bring new designs for ion trapping chips into production, and you will play an important part in shaping the hardware behind our work building the world's most advanced quantum systems." That's prose. Responsibilities bullet list: The posting shows: "In this position you will turn operational requirements into chip layout, supporting the delivery of devices that enable new technologies. You will have the opportunity to expand the range of features our chips support, contributing directly to the goal of building utility scale quantum computers. Guiding chips through the design process, from requirements to layout and tape outLaying out complex multi layer chips, including metal track routing and interfaces with photonics and CMOSCollaborating with scientists to discuss their requirements and settle on specificationsCoordinating with other teams to ensure feasibility and compatibilityTaking charge of projects independently and owning delivery of the final tape out" But later there is also a repeated list: "We're looking for someone who can guide chips through the full design process, from requirements through to layout and tape-out. You will have experience laying out complex, multi-layer chips, including metal-track routing and interfaces with photonics and CMOS. You'll collaborate with scientists to understand their requirements and agree specifications, while coordinating with other teams to ensure feasibility and compatibility. You'll also be comfortable taking charge of projects independently and owning the delivery of the final tape-out." And then "You'd be a great fit with: Experience in scripted generation of layout, using GDSFactory in Python or similarExperience using Cadence for IC layoutExperience in ion trap design, photonics design or IC packaging" We need to combine responsibilities and requirements without duplication. Let's parse responsibilities: The core responsibilities: turn operational requirements into chip layout; expand features; guide chips through design process from requirements to layout and tape out; lay out complex multi-layer chips including metal track routing and interfaces with photonics and CMOS; collaborate with scientists to discuss requirements and settle on specifications; coordinate with other teams to ensure feasibility and compatibility; take charge of projects independently and own delivery of final tape out. That's responsibilities. Requirements: experience translating design requirements into features, hands-on experience in chip layout; work across teams to discuss many aspects of chip design, understand how different parts influence and constrain one another, take on layout work themselves, contribute effectively within fast moving technical team; drive design process, solve problems, take responsibility for delivery. Also experience in scripted generation of layout using GDSFactory in Python or similar; experience using Cadence for IC layout; experience in ion trap design, photonics design or IC packaging. Also maybe "You'd be a great fit with:" list. We'll combine into Requirements section as list. Pay: US Salary Banding: $124,000 - $186,000. Also Wage Transparency: £75,200—£112,800 GBP. Also note compensation varies based on factors. We'll include that as prose. Benefits: comprehensive medical, dental, and vision plans, matching 401(k), unlimited PTO and paid holidays, parental/adoption leave, legal insurance, and a home technology stipend. We'll output sections: About the role? Actually we have About IonQ (company overview) and The Role (role description). Could combine into "About the role" heading? But we have both company overview and role description. The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have heading "About the role" for the role description. The company overview maybe could be placed under "About the role"? But it's about IonQ, not role. However we could treat it as part of "About the role" preceding the role description. Or we could create a heading "About IonQ"? Not in list. The instruction says use those headings as examples, not strictly limited? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. So we need to map content to those headings. "About the role" can include both company overview and role description? Might be okay. But we could also have "About the role" for role description, and maybe put company overview in a preceding

  without heading? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." It doesn't forbid other headings not in list, but suggests using those examples. Safer to use only those headings. So we will have:

  About the role

  containing both IonQ overview and role description? Might be mixing. But we can split: first

  about IonQ, then

  about the role. That's fine under same heading. Then

  Responsibilities

  with
  . Then

  Requirements

  with
  . Then

  Benefits

  with
  . Then

  Pay

  with

  . We'll omit Schedule. Now ensure we don't include filler like "commensurate with experience". Not present. Now craft HTML. Let's write:

  About the role

  IonQ, Inc. [NYSE: IONQ] is the world's leading quantum platform and merchant supplier - delivering integrated quantum solutions across computing, networking, sensing, and security. IonQ's newest generation of quantum computers, the IonQ Tempo, is the latest in a line of cutting-edge systems that have been helping customers and partners including Amazon Web Services, and AstraZeneca achieve 20x performance results and accelerate innovation in drug discovery, materials science, financial modeling, logistics, cybersecurity, and defense. In 2025, the company achieved 99.99% two-qubit gate fidelity, setting a world record in quantum computing performance. Headquartered in College Park, Maryland, IonQ has operations in California, Colorado, Massachusetts, Tennessee, Washington, Italy, South Korea, Sweden, Switzerland, Canada, and the United Kingdom. Our quantum computing services are available through all major cloud providers, while we also meet the needs of networking and sensing customers across land, sea, air, and space. IonQ is making quantum platforms more accessible and impactful than ever before.

  We are looking for a Senior QPU Design Engineer to join our Processor Design team at Oxford Ionics, now part of IonQ. You will be responsible for integrating all the features required to operate our quantum computers into complex chips, contributing to the team's mission of advancing the design of high performance quantum processing units. You will work closely with scientists and fabrication engineers to bring new designs for ion trapping chips into production, and you will play an important part in shaping the hardware behind our work building the world's most advanced quantum systems.

  Responsibilities

  • Turn operational requirements into chip layout, supporting the delivery of devices that enable new technologies.
  • Expand the range of features our chips support, contributing directly to the goal of building utility scale quantum computers.
  • Guide chips through the design process, from requirements to layout and tape‑out.
  • Lay out complex multi‑layer chips, including metal track routing and interfaces with photonics and CMOS.
  • Collaborate with scientists to discuss their requirements and settle on specifications.
  • Coordinate with other teams to ensure feasibility and compatibility.
  • Take charge of projects independently and own delivery of the final tape‑out.

  Requirements

  • Experience translating design requirements into features, with hands‑on experience in chip layout.
  • Ability to work across teams to discuss the many aspects of chip design, understand how different parts of a chip influence and constrain one another, take on layout work personally, and contribute effectively within a fast‑moving, highly technical team.
  • Drive the design process, solve problems as they arise, and take responsibility for delivery.
  • Experience in scripted generation of layout using GDSFactory in Python or similar.
  • Experience using Cadence for IC layout.
  • Experience in ion trap design, photonics design, or IC packaging.

  Benefits

  • Comprehensive medical, dental, and vision plans
  • Matching 401(k)
  • Unlimited PTO and paid holidays
  • Parental/adoption leave
  • Legal insurance
  • Home technology