Sr Technical Product Manager - Gemini

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes Summary (which could be About the role). It has Responsibilities section. It has Qualifications section. It mentions "We consistently monitor external market data..." about compensation but no specific salary numbers; it's vague. It says "We determine base compensation decisions on several factors..." and "In addition to our base salary offerings, we also provide equity grants for all new hires." That's some compensation info but not specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention equity grants, base salary, but not specific numbers. Is that enough to include a Pay section? It says "We consistently monitor external market data and update base salary ranges accordingly." That's generic. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The posting does not give actual numbers, just says they monitor market data and determine based on factors. That's vague but not placeholder like "commensurate with experience". However it's still not specific. The instruction: "Prefer a few substantive sections over many thin ones." Probably we should not include Pay because it's not specific numbers. Benefits: mentions equity grants for all new hires. That's a benefit. Could include Benefits section with that detail. Also maybe mention "We consistently monitor external market data..." as part of Benefits? Actually that's compensation. Benefits could be equity grants. Also maybe mention "We are committed to cultivating a diverse work environment..." that's EEO boilerplate, should be removed. So we should strip EEO. Thus sections: About the role (from Summary), Responsibilities, Qualifications. Possibly Skills? The qualifications include skills; but we can combine into Qualifications. Could also have a Skills section if we want to extract skills but not required. The instruction: prefer few substantive sections. So we can have About the role, Responsibilities, Qualifications, Benefits (equity grants). No Pay or Schedule. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID etc. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to parse the posting and produce HTML. Let's extract About the role: The summary paragraph(s) after "Summary". It includes: "QuEra is seeking a Senior Technical Product Manager to join the Quantum Computing Services team at our Boston headquarters. You will play a foundational role in shaping the company's product strategy and processes and taking responsibility for the success of our products and services. The team's mission is to transform neutral atom quantum computing technology into products and services offering cutting-edge quantum computing functionality, delivered both via the cloud and as managed on-premise solutions, and interfaced by users via a variety of in-house and third-party software. As the Senior TPM, you will partner closely with scientists, engineers, executives, and customers to define, communicate, and deliver the roadmap for quantum computing products and services. You will gather and synthesize both functional and non-functional requirements from customers, translating them into a clear and actionable product roadmap. Working closely with cross-functional teams, you will ensure that development efforts are both feasible and timely, delivering solutions that meet customer needs. In addition, you will drive project and program management activities to align with key milestones, ensuring execution stays on track and goals are achieved. In-depth exploration and a solid grasp of application algorithms for NISQ and early FTQC will be essential in shaping product features and roadmap priorities. This role calls for comprehensive technical expertise across the quantum computing stack—including hardware, control systems, compilers, quantum error correction, and algorithmic software. Given the product's early stage, advancing both the maturity and stability of the technology is paramount. Success will require the ability to navigate complex trade-offs, balancing the push for rapid feature development with the need to ensure system robustness and reliability. Initial Projects Year 1-2: Define, deliver, and execute a roadmap of products and services built on QuEra's Gemini-class platform, enabling customers to access and develop on QuEra's first-generation gate-based systems. Manage scope and timelines to meet both functional and non-functional requirements, ensuring a high level of customer satisfaction. Through successful product development, demonstrate QuEra's QPU as the leading choice for executing algorithms in select, high-impact use cases. Bloqade, QuEra's open-source software for creating, simulating and executing quantum program, will be a core part of the offerings and will require product management in its own right, as part of the role's scope. Year 2-3: Extend this roadmap to QuEra's next generation, QEC QPU platform, supporting continuous supply of qubits, and logical, error-corrected quantum computation. This roadmap needs to be aligned with our long-term technical roadmap for 2027 and 2029. In parallel, you will establish and operate a product management process to synthesize, negotiate, document, and track requirements across internal and external stakeholders." That's a lot. We'll keep as prose in

  . Could break into multiple paragraphs but okay. Responsibilities: bullet list under "As Senior Technical Product Manager, you will be expected to lead and drive the following activities:" then list items. Also "You will also be expected to contribute to the following:" then another list. We need to combine into a single

  • list? The instruction: Use
    • for any list of duties/requirements/benefits. So we can make one list containing all responsibilities items. Could separate into two lists but still okay. Qualifications: list under "Qualifications" heading. Then bullet list of qualifications. Also "Preferred:" items. Could combine into one list but maybe separate into Required and Preferred? But we can just list all as items. Benefits: equity grants for all new hires. Also maybe mention base salary? But we decided not to include Pay. Benefits: equity grants. We must not include EEO boilerplate. Let's craft HTML. Structure:

      About the role

      ...

      Responsibilities

      • Define and articulate the product vision and roadmap for QuEra's quantum computing services (cloud-based and on-premise), ensuring alignment with company strategy and customer needs.
      • Gather and synthesize requirements from physicists, engineers, application developers, and customers across hardware, software, and operational domains.
      • Translate technical requirements into actionable deliverables, including structured product specifications, prioritized backlogs, and feature timelines.
      • Collaborate with engineering and R&D teams to deliver against specifications and milestones, balancing competing priorities, resource constraints, and technical uncertainties.
      • Lead product launch planning and execution, including customer adoption strategies, success metrics, and go-to-market support for new systems and services.
      • Establish, operate, and continuously refine product management processes, ensuring effective communication, decision-making, and execution across the company.
      • Collaborate with application developers and scientific partners on pilot projects, benchmarking efforts, and use-case validation.
      • Incorporate customer feedback and market insights into technical development and roadmap prioritization.
      • Support quality assurance, system integration, and operational readiness, ensuring reliable delivery of products and services.
      • Contribute to business development activities, including customer demos, RFP responses, and strategic partnerships that expand QuEra's market presence.

      Qualifications

      • Proven experience (7+ years) in product management or technical leadership roles, ideally in deep-tech fields (quantum computing, HPC, semiconductors, complex hardware/software systems).
      • Strong technical background with the ability to engage deeply across the quantum computing stack—from hardware and control systems to compilers, quantum error correction, and algorithmic software.
      • Advanced degree in physics, engineering, or computer science.
      • Demonstrated success building and managing roadmaps that bridge science, engineering, and business needs.
      • Ability to succinctly capture requirements and convert them into actionable specifications and structured backlogs.
      • Experience with software and/or hardware lifecycle management, from prototyping to deployment and support.
      • Proven success in project and program management, balancing scope, timelines, and resources while navigating technical and organizational ambiguity.
      • Excellent communication skills, with the ability to engage effectively with both technical experts and business stakeholders.
      • Willingness to travel periodically to customer and machine locations worldwide.
      • Proficiency with product management tools (e.g., Atlassian suite, Aha!) and agile methodologies.
      • Direct experience in quantum computing research, product development, or application algorithms (NISQ and early FTQC).
      • Familiarity with cloud-based services, managed infrastructure offerings, and enterprise adoption of emerging technologies.
      • Experience supporting customer-facing activities such as pilot projects, benchmarking, RFPs, and strategic partnerships.
      • Demonstrated ability to establish and scale product management processes within a growing organization.

      Benefits

      • Equity grants for all new hires.
      We should not include Pay or Schedule. Check that we didn't repeat job title as heading. Good. We removed boilerplate. Check that we preserved all substantive information: The summary includes many details; we included them in About the role paragraph. Did we miss any? The summary includes "Initial Projects Year 1-2" and "Year 2-3" details; we included them in the paragraph. Good. We omitted the line "We consistently monitor external market data and update base salary ranges accordingly. We determine base compensation decisions on several factors, including as geographic placement, role-specific knowledge, skills, and/or experience." That's compensation info; we omitted because we didn't create Pay section. But is that considered substantive? It's about compensation but vague. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state base salary and equity grants. However we decided not to include Pay because it's not specific numbers. But we could include a Pay section with that prose. The instruction: "never emit a heading followed by filler/placeholder text (e.g., 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The text "We consistently monitor external market data and update base salary ranges accordingly. We determine base compensation decisions on several factors, including as geographic placement, role-specific knowledge, skills, and/or experience." is not exactly placeholder like "commensurate with experience". It's a statement about process. Could be considered substantive. However the instruction also says "Prefer a few substantive sections over many thin ones." Adding a Pay section with just that sentence might be thin. But we already have Benefits section with equity grants. Could combine compensation info into Benefits? But Benefits is for non-salary compensation. Could we include a Pay section with that sentence? Might be okay. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state base salary and equity grants. So we could include Pay section with that sentence, and Benefits section with equity grants. But that would be two thin sections. Might be better to combine compensation and benefits into one "Compensation and Benefits" section? But headings are fixed: we can only use those headings. Could we put both under Benefits? Benefits heading could include equity grants and mention base salary determination? That might stretch meaning of Benefits. Better to follow instruction: only include sections when posting has real, specific content for it. The posting does state base salary process, but it's not specific numbers. Is that considered "real