Senior/Staff Electro-Optic Hardware Design Engineer

We need to output HTML fragment with sections: About the role? The posting includes a job summary, overview, responsibilities, core competencies, experience/qualifications, benefits, pay (salary ranges). Also schedule? Not mentioned. So we include sections: About the role (maybe from job summary), Overview, Responsibilities, Core Competencies / What Success Looks Like, Experience/Qualifications, Benefits, Pay. Use

for each heading. Use

• for lists. Use

  for prose. We must not repeat job title. No metadata like Job ID. Remove boilerplate: EEO, note about suspicious activity, etc. Also remove "PsiQuantum provides equal employment opportunity..." etc. Also remove "Note: PsiQuantum will only reach out..." etc. Also remove "We are not accepting unsolicited resumes..." etc. Also remove "Base pay is one part..." maybe keep pay section. But we need to include pay and benefits sections only if posting actually states them. It does state benefits and salary ranges. So include. We must preserve all substantive information. So include details from job summary, overview, responsibilities, core competencies, experience/qualifications (required and preferred), benefits list, pay ranges. We must not invent or summarize away detail. So we need to keep specifics. We need to format as HTML fragment. Let's craft sections:

  About the role

  (maybe from Job Summary). Content: "We are seeking a senior- or staff-level engineer to own the detailed design, integration, and qualification of electro-optic hardware modules used in advanced photonic systems. Working alongside the Photonic Hardware Architect, this role turns system requirements and high-level concepts into robust rack-mountable or blade-format products containing optical amplifiers, attenuators, polarization controllers, power monitors, control electronics, and related optical and electro-optic subassemblies. The engineer will lead internal design execution, direct external development partners, and establish the experimental evidence and verification rigor needed for sound technical and production decisions." That's prose; put in

  .

  Overview

  with prose: "Own detailed electro-optic module design from requirements and concept selection through prototype build, EVT, DVT, and transfer to manufacturing. Translate system architecture into complete optical, electrical, mechanical, thermal, firmware-control, and test interfaces for rack-mountable boxes and blade assemblies. Serve as the hands-on technical lead connecting system architects, photonics, electronics, mechanical engineering, test, operations, and external suppliers."

  Responsibilities

  with
  • each bullet. We need to copy each responsibility line from the posting. List: - Own the detailed design and integration of electro-optic modules incorporating optical amplifiers, variable or fixed attenuators, polarization controllers, optical switches, splitters, couplers, filters, power monitors, photodiodes, control electronics, and associated fiber infrastructure. - Convert system and subsystem requirements into engineering specifications, interface definitions, optical power and noise budgets, schematics, component selections, bills of materials, mechanical layouts, tolerance analyses, and assembly documentation. - Lead design trade studies across optical performance, noise, stability, dynamic range, control bandwidth, thermal behavior, reliability, serviceability, manufacturability, cost, and schedule; document decisions and residual risks. - Design controlled experiments, select appropriate instrumentation and statistical methods, analyze data, and make technically defensible decisions when models, component data, or vendor claims are insufficient. - Plan and execute module bring-up, characterization, margin testing, environmental testing, fault-injection testing, and reliability-oriented testing; automate measurements and data reduction where practical. - Author verification and acceptance requirements, test plans, procedures, and reports for engineering builds and externally supplied modules, including clear pass/fail criteria and traceability to requirements. - Lead EVT and DVT for internally developed and vendor-developed hardware; investigate failures, drive root-cause analysis and corrective actions, and ensure closure of test anomalies and design risks. - Oversee internal design reviews and configuration control, ensuring that drawings, schematics, BOMs, firmware or control interfaces, calibration data, and released test documentation remain consistent and production-ready. - Own technical collaboration with contract manufacturers and specialist vendors, including statements of work, requirements flow-down, design reviews, prototype acceptance, supplier qualification, and resolution of quality or yield issues. - Partner with manufacturing and operations to implement design-for-manufacture, design-for-test, calibration, alignment, service, and end-of-line acceptance strategies that support repeatable builds and field use. - Communicate status, decisions, risks, and recovery plans clearly across functions; provide concise, decision-oriented executive updates without losing the underlying technical rigor. That's all.

    Core Competencies / What Success Looks Like

    with
    • each bullet. List: - Detailed module designs meet performance, interface, safety, reliability, manufacturability, and serviceability requirements with objective verification evidence. - EVT and DVT are executed with complete, traceable documentation; failures and technical risks are surfaced early and closed decisively. - Internal teams and external suppliers deliver build-ready designs, consistent documentation, and repeatable acceptance results. - Technical decisions are made quickly but rigorously through focused experiments, clear trade studies, and concise communication.

      Experience/Qualifications

      maybe split into Required Qualifications and Preferred Qualifications as subheadings? But rule: use

      for section headings. Could have two

      sections: Required Qualifications and Preferred Qualifications. Or combine into one with

      Experience/Qualifications

      and then
      with required and preferred separated maybe with ? But better to follow instruction: include a section only when posting has real specific content. It does have Required Qualifications and Preferred Qualifications. Could make two sections:

      Required Qualifications

      and

      Preferred Qualifications

      . That seems okay. We'll output:

      Required Qualifications

      with
      • each bullet. List: - B.S. or higher in electrical engineering, optical engineering, physics, mechanical engineering, or a related field, with substantial relevant industry experience. - Demonstrated ownership of detailed electro-optic or opto-mechanical hardware design through prototype, verification, qualification, and manufacturing release. - Strong hands-on knowledge of fiber-optic components and subsystems, including amplifiers, attenuators, polarization control, optical power monitoring, photodetection, and practical fiber management. - Experience integrating optical, analog and digital electronics, thermal management, mechanical packaging, connectors, power distribution, communications, and safety features in rack-mountable or blade-format equipment. - Proficiency developing requirements, interface-control documentation, optical and electrical budgets, verification matrices, test plans, procedures, acceptance criteria, and formal test reports. - Strong experimental judgment, including test design, instrumentation, measurement uncertainty, data analysis, and the ability to distinguish component limitations from integration or test artifacts. - Experience leading EVT/DVT, hardware bring-up, structured debugging, failure analysis, root-cause investigation, and corrective-action closure. - Proven ability to direct vendors and contract manufacturers while maintaining technical ownership, schedule discipline, document quality, and configuration control. - Excellent written and verbal communication, with the ability to collaborate across disciplines and distill complex technical work into efficient executive-level updates.

        Preferred Qualifications

        with
        • each bullet. List: - Experience with high-power or low-noise optical amplification, photonic calibration, metrology, quantum photonics, or precision instrumentation. - Familiarity with laser and electrical safety, EMI/EMC, thermal and environmental qualification, reliability methods, and applicable product-compliance practices. - Experience creating automated laboratory or production test systems using Python, LabVIEW, MATLAB, or similar tools. - Working knowledge of statistical tolerance analysis, measurement-system analysis, design of experiments, reliability growth, and supplier quality methods. - Experience transferring low-volume, high-complexity hardware into repeatable production and supporting sustaining engineering or field failure analysis.

          Benefits

          with
          • each bullet. List: - competitive health coverage for you and your dependents - 401(k) with company match - equity grants - access to financial wellness tools and planning resources - wellness benefits - family support programs - life and disability insurance - paid leave programs - company-designated paid holidays - discretionary time off (DTO) - end-of-year company shutdown We could note that some have eligibility requirements etc. But we should preserve that detail: "Some of these benefits have eligibility requirements and may vary based on location, role, or employment status. Many of these benefits are subsidized or fully paid for by the company." That's substantive. So include as a

            after list maybe. Thus after

            we add

            Some of these benefits have eligibility requirements and may vary based on location, role, or employment status. Many of these benefits are subsidized or fully paid for by the company.

            Pay

            with prose: include salary ranges per zone. We need to preserve the exact ranges: Zone 1 $176,500—$207,400 USD, Zone 2 $158,900—$186,700 USD, Zone 3 $141,200—$165,900 USD, Zone 4 $123,600—$145,200 USD. Also note that base pay is one part of total compensation package, full-time roles eligible for equity and benefits, compensation ranges reflect cost of labor across multiple U.S. geographic markets, pay based on defined geographic zones, actual compensation may vary outside of these ranges dependent on various factors, recruiter can share more details. We should include that info as substantive. Thus

            Base pay is one part of the total compensation package. Full-time roles are eligible for equity and benefits. Our compensation ranges reflect the cost of labor across multiple U.S. geographic markets, and we pay based on defined geographic zones. This position may be filled within one of the following U.S. geographic zones, each with its own salary range. Actual compensation may vary outside of these ranges and is dependent on various factors including, but not limited to, a candidate's qualifications, relevant education and training, competencies, experience, geographic location, business needs, and internal equity. Your recruiter can share more details about the salary range applicable to your location during the hiring process.

            Then maybe a
            for zones? Could be
            • Zone 1 - Bay Area and NYC: $176,500—$207,400 USD
            etc. We'll do that. Now ensure we didn't include any boilerplate like EEO, note about suspicious activity, etc. We removed those. Check for any leftover: The posting also had "PsiQuantum's mission..." etc. That's company description; we might include as part of About the role? The job summary already includes that? Actually the mission description is before Job Summary. Should we include that as part of About the role? The instruction: "Preserve ALL substantive information". The mission description is substantive about company. Should we include it? Possibly as part of About the role or a separate section like "About PsiQuantum". But the instruction says use headings for sections like About the role, Responsibilities, etc. It didn't forbid adding other sections like About the company. However they said "use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. list is not exhaustive; we could add other headings if needed. But they said "Prefer a few substantive sections over many thin ones." The mission description could be included in About the role section as a paragraph. But the About the role currently only has job summary. We could expand About the role to include company mission description. However the job summary already includes "We are seeking a senior- or staff-level engineer..." The mission description is separate. Could we add a paragraph before that? The instruction: "Do NOT repeat the job title as a heading (the