Tech Lead - Hardware /Embedded Engineer

We need to output only HTML fragment, no markdown fences. Use

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We need to parse the job posting. Key sections: - "Meet the Team" maybe about the team, but we can treat as "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content accordingly. We need to preserve all substantive info, no boilerplate. We need to remove cookie/navigation/legal/EEO etc. The posting includes "Message to applicants applying to work in the U.S. and/or Canada:" which is about salary range, benefits, etc. That's relevant for Pay and Benefits sections. We need to include Pay section if posting states salary range. Yes, they gave starting salary range $151,300 to $216,200 and also full salary ranges for certain locations. So we should include Pay section with that info. Benefits: they mention benefits: medical, dental, vision, 401(k) with match, paid parental leave, disability, life insurance, stock units, paid time away details, holidays, vacation, sick time, volunteer days, bonuses. So we should include Benefits section. Schedule: Not mentioned explicitly. There's no schedule info (like full-time, part-time, shift). So we should NOT include Schedule section. Skills: Could be derived from qualifications? Might be separate but we can include Skills if there is specific content. The posting lists many technical skills under responsibilities and qualifications. Could treat as Skills section summarizing those. But we need to avoid filler. We could include a Skills section with bullet list of relevant skills: custom PCB design, mixed-signal, high-speed electronics, FPGA, embedded systems, firmware, precision control algorithms, hardware APIs, etc. However those are already in Responsibilities. Might be okay to have Skills separate but we need to ensure not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put skills in both Responsibilities and Skills, we would be duplicating, which is okay as long as we preserve info. But better to keep responsibilities as duties, and qualifications as requirements. Skills could be extracted from qualifications. However we can also omit Skills section if we think it's not explicitly a separate section. The instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine qualifications and skills into Requirements/Qualifications. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include those that have content. We have: - About the role: Could be the "Meet the Team" and "Your Impact" paragraphs describing role and impact. That seems appropriate. - Responsibilities: The bullet list of duties under "You Will" etc. That's many responsibilities. - Requirements: Minimum Qualifications. - Qualifications: Preferred Qualifications. - Skills: Could be derived from both but maybe we can skip if we think it's thin. However we have many specific skills listed in responsibilities and qualifications; we could create a Skills section summarizing them, but that would be summarizing, which we should avoid. Better to keep them in Responsibilities and Qualifications. So we can omit Skills. - Benefits: Yes. - Pay: Yes. - Schedule: No. Thus output sections: About the role, Responsibilities, Requirements (Minimum Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay. We need to use

for each heading. Inside each section, use

for prose,

• for lists. We need to preserve all substantive info, not invent. Let's extract content. About the role: Combine "Meet the Team" paragraph and "Your Impact" paragraphs maybe also the initial description about Outshift Quantum Research team. Let's capture: "The Outshift by Cisco team is one of Cisco’s most visible innovation organizations, driving the next generation of transformative technologies and business opportunities. As part of the Strategy, Incubation & Applications group led by Cisco’s Chief Strategy Officer, you will collaborate with some of the company’s most forward-thinking researchers, engineers, and technology leaders. Within the Outshift Quantum Research team and Quantum Labs, we are pioneering the design and development of practical, scalable, and efficient quantum networking technologies — foundational building blocks for the future Quantum Internet. Our multidisciplinary team of scientists and engineers is dedicated to advancing the state of the art in quantum networking, distributed quantum systems, and quantum-enabled applications." Then "Your Impact": "Cisco Quantum Research is seeking a highly skilled Embedded & Controls Engineer to help develop the next generation of deployable quantum networking hardware. You will take end-to-end ownership of the electronics and control architecture that connects our advanced photonic and quantum hardware to Cisco's software and orchestration platforms. Your work will span custom PCB design, mixed-signal and high-speed electronics, FPGA and embedded systems, firmware, precision control algorithms, hardware APIs, and rack-level system integration. Working closely with our photonics, software, systems, and mechanical engineering teams, you will transform laboratory prototypes into robust, manufacturable systems capable of operating outside the laboratory. You will address challenging requirements including ultra-low-noise electronics, precise synchronization, sub-nanosecond timing, high-speed signal integrity, closed-loop optical control, and reliable remote management. Your work will establish the electronic and control infrastructure required to bring Cisco's quantum networking technologies from research prototypes into scalable, field-deployable platforms." We can combine into a few paragraphs. Responsibilities: The list under "You Will" bullet points (starting with "Architect custom mixed-signal PCBs..."). Let's extract each bullet: - Architect custom mixed-signal PCBs for precision control, data acquisition, timing, and communication within rack-mounted quantum systems. - Develop embedded software and firmware to control custom electronics, optical components, and photonic devices. - Design high-speed analog and digital signal paths while maintaining stringent requirements for signal integrity, latency, synchronization, and noise. - Interface with embedded processors, FPGAs, ADCs, DACs, and discrete control and telemetry signals. - Design, implement, and tune digital control loops for precision regulation and stabilization of optical and electronic hardware. - Architect low-noise power distribution, grounding, and control electronics for sensitive quantum hardware. - Develop interfaces for system communication using technologies such as Ethernet, UART, SPI, USB, GPIO, and high-speed data-converter interfaces. - Define and implement APIs that enable higher-level software platforms to control hardware and access system status and telemetry. - Develop custom cable harnessing and interconnect solutions for RF, digital, analog, telemetry, and high-speed signals. - Collaborate with software, systems, mechanical, optical, and photonics engineers to optimize thermal performance, grounding, EMI/EMC, signal integrity, and overall system reliability. - Lead hardware bring-up and debug complex interactions between electronics, firmware, FPGA logic, and system-level software. - Create and implement comprehensive hardware, firmware, and system-level test plans; analyze results and drive design improvements. - Transform laboratory and benchtop prototypes into reliable, manufacturable, field-deployable rack-mounted systems. We need to preserve all. Requirements (Minimum Qualifications): The block: "Minimum Qualifications Bachelors + 8 years of related experience, or Masters + 6 years of related experience, or PhD + 3 years of related experience, or equivalent related work experience. 3+ years of experience developing custom electronic hardware and embedded control systems. Experience designing mixed-signal PCBs incorporating embedded processors, microcontrollers, or FPGAs. Experience in embedded software/firmware development using C/C++. Experience with FPGA-based systems, including familiarity with RTL and/or High-Level Synthesis (HLS)." We should keep as sentences; could be a

  or

  . Since it's a list of qualifications, we can use
  • each. Qualifications (Preferred Qualifications): The block: "Preferred Qualifications Experience developing electronics and control systems for lasers, electro-optic modulators, optical switches, photonic integrated circuits, or other photonic devices. Experience with analog and digital electronics, signal integrity, impedance matching, grounding, and high-speed PCB designExperience working with ADCs, DACs, and mixed-signal data-acquisition and control systems. Experience with common communication interfaces including Ethernet, UART, SPI, USB, and GPIO. Experience designing low-noise power distribution and electronics for sensitive instrumentation. Background in classical optics, quantum optics, quantum networking, photonics, or precision instrumentation." Note there is a missing space after "PCB designExperience". We'll keep as is but maybe separate sentences. We'll split into items. Benefits: The block after "Why Cisco?" includes many details. We need to capture all substantive benefits. Let's extract: "Why Cisco? At Cisco, we’re revolutionizing how data and infrastructure connect and protect organizations in the AI era – and beyond. We’ve been innovating fearlessly for 40 years to create solutions that power how humans and technology work together across the physical and digital worlds. These solutions provide customers with unparalleled security, visibility, and insights across the entire digital footprint. Fueled by the depth and breadth of our technology, we experiment and create meaningful solutions. Add to that our worldwide network of doers and experts, and you’ll see that the opportunities to grow and build are limitless. We work as a team, collaborating with empathy to make really big things happen on a global scale. Because our solutions are everywhere, our impact is everywhere. We are Cisco, and our power starts with you." That's more about company; still substantive but maybe considered boilerplate? It's not EEO, it's about Cisco culture. Might be okay to keep as part of About the role? But we already have About the role. Could include a paragraph about Cisco culture in Benefits? Actually Benefits section should focus on benefits. The "Why Cisco?" is more about company culture; could be considered part of About the role or maybe we can include a separate section but not in list. Since we only have allowed headings, we could incorporate that into About the role or maybe omit as it's somewhat generic. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info somewhere. Could add a

    under About the role after the team description. But we already have About the role with team and impact; we can add another paragraph about Cisco's mission etc. Then benefits specifics: "Message to applicants applying to work in the U.S. and/or Canada: The starting salary range posted for this position is $151,300.00 to $216,200.00 and reflects the projected salary range for new hires in this position in U.S. and/or Canada locations, not including incentive compensation*, equity, or benefits. Individual pay is determined by the candidate's hiring location, market conditions, job-related skillset, experience, qualifications, education, certifications, and/or training. The full salary range for certain locations is listed below. For locations not listed below, the recruiter can share more details about compensation for the role in your location during the hiring process. U.S. employees are offered benefits, subject to Cisco’s plan eligibility rules, which include medical, dental and vision insurance, a 401(k) plan with a Cisco matching contribution, paid parental leave, short and long-term disability coverage, and basic life insurance. Please see the Cisco careers site to discover more benefits and perks. Employees may be eligible to receive grants of Cisco restricted stock units, which vest following continued employment with Cisco for defined periods of time. U.S. employees are eligible for paid time away as described below, subject to Cisco’s policies: 10 paid holidays per full calendar year, plus 1 floating holiday for non-exempt employees1 paid day off for employee’s birthday, paid year-end holiday shutdown, and 4 paid days off for personal wellness determined by CiscoNon-exempt employees** receive 16 days of paid vacation time per full calendar year, accrued at rate of 4.92 hours per pay period for full-time employeesExempt employees participate in Cisco’s flexible vacation time off program, which has