Sr Silicon Bring-Up and Integration Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: Application Close Date, etc. Also remove EEO, legal, etc. Keep substantive info. We need to parse the posting. Let's extract sections: - About the role: The paragraph after "Job Description" maybe? Actually there is a description: "Blue Origin is pioneering the future of space-based communications with TeraWave...". Also earlier: "At Blue Origin, we envision millions...". That's about company mission. Could be "About the role" or "About the company". The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have: - Responsibilities: list under "Responsibilities Include but Are Not Limited To" with many bullet-like sentences. - Minimum Qualifications: list of qualifications. - Preferred Qualifications: list. - Skills: maybe combine Minimum and Preferred? But we have separate sections for Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements = Minimum Qualifications. Qualifications = Preferred Qualifications. Skills could be technical skills extracted? But we can also put skills under Qualifications? However instruction: Use sections only when posting has real specific content. We have content for Minimum Qualifications and Preferred Qualifications. Could map Minimum to "Requirements", Preferred to "Qualifications". Skills maybe not explicitly separate; we could omit Skills section if no distinct skills list beyond those. But we have many skill mentions in responsibilities and qualifications. Could create a Skills section summarizing technical skills: C/C++, Python, JTAG, etc. But we must not invent or summarize away detail; we must preserve ALL substantive information. If we create a Skills section, we need to take content from posting that is about skills. The posting includes many skill statements within Minimum/Preferred qualifications and responsibilities. We could keep them under Requirements and Qualifications; that's fine. Skills section could be omitted if no explicit "Skills" heading. Safer to omit Skills. Pay: There's "Base Pay Range For CA applicants is $230,398.00 - $322,556.85 WA applicants is $230,398.00 - $322,556.85 Other Site Ranges May Differ". That's specific pay info. So we should include Pay section with that content. Schedule: Not mentioned. No schedule info. So omit Schedule. Benefits: There's a Benefits section with details. Include Benefits. About the role: We have introductory paragraphs: "At Blue Origin, we envision millions of people living and working in space for the benefit of Earth. We’re working to develop reusable, safe, and low-cost space vehicles and systems within a culture of safety, collaboration, and inclusion. Join our team of problem solvers as we add new chapters to the history of spaceflight! Blue Origin is pioneering the future of space-based communications with TeraWave, a revolutionary satellite communications network designed to deliver symmetrical data speeds of up to 6 Tbps anywhere on Earth. This multi-orbit constellation will consist of optically interconnected satellites in low Earth orbit (LEO) and medium Earth orbit (MEO), providing enterprise-grade connectivity for critical operations worldwide." Also there is "Job Description As a Sr Silicon Bring-Up and Integration Engineer, you will be a key hands-on member..." That's more role-specific. Could be part of About the role. We'll combine. Thus About the role section will contain those paragraphs. Now we need to format with

for each section heading, then content: use

for prose,

• for lists. We must not include any markdown fences. Let's extract responsibilities list items: They are sentences after "Responsibilities Include but Are Not Limited To". Each starts with a capitalized phrase and ends with a period. We'll make each a
• . List: - Silicon Bring-Up: Perform first-silicon power-on, initialization, configuration, functional bring-up, and debugging of custom SoCs and ASICs. - Low-Level Silicon Software: Develop C/C++ software, firmware, diagnostics, and Python-based test infrastructure used to configure, control, exercise, and validate custom silicon. - Pre-Silicon Readiness: Develop bring-up software, test sequences, register-access utilities, diagnostics, and validation capabilities prior to silicon availability using simulation, emulation, FPGA prototypes, or other available pre-silicon platforms. - HW/SW Integration: Integrate and debug low-level software and firmware with silicon hardware, including initialization sequences, clocks and resets, memory interfaces, peripherals, data paths, and high-speed interfaces. - Post-Silicon Validation: Develop and execute functional, performance, stress, and corner-condition tests to validate silicon behavior against design and system requirements. - Silicon Characterization: Support characterization across voltage, temperature, frequency, operating modes, and silicon process variation. - Complex Debug: Investigate and root-cause failures spanning silicon hardware, RTL, firmware/software, boards, clocks, power, interfaces, and system-level behavior. - Lab Automation: Develop automated test infrastructure for DUT configuration, lab instrumentation, data collection, regression testing, and analysis. - Interface Bring-Up: Bring up and debug low-speed and high-speed interfaces such as JTAG, SPI, I2C, UART, PCIe, Ethernet, SerDes, DDR/LPDDR, and custom chip-to-chip interfaces as applicable. - Bring-Up Hardware Support: Define requirements for evaluation boards, fixtures, sockets, instrumentation, and debug capabilities required for silicon bring-up and validation, and work closely with board-design teams on their implementation. - Cross-Functional Integration: Collaborate closely with ASIC architecture/design, verification, firmware/software, RF/DSP, board, system, manufacturing, and test teams to resolve silicon integration issues. - Silicon Maturation: Support issues from initial engineering samples through characterization, validation, and production readiness, including verification of hardware and software fixes across silicon revisions. Now Minimum Qualifications list: - 7+ years of experience in ASIC/SoC bring-up, post-silicon validation, embedded systems, silicon integration, or closely related fields. - Bachelor’s degree in Electrical Engineering, Computer Engineering, Computer Science, or a related technical field. - Hands-on experience with ASIC or SoC bring-up, post-silicon validation, or low-level hardware/software integration. - Strong C/C++ programming experience for low-level hardware control, embedded software, firmware, or silicon diagnostics. - Strong Python or equivalent scripting experience for test automation, instrumentation, and data analysis. - Strong understanding of SoC architecture, memory-mapped registers, interrupts, DMA, clock/reset architecture, memory systems, and hardware/software interfaces. - Experience with low-level interfaces and debug protocols such as JTAG, SPI, I2C, UART, PCIe, Ethernet, SerDes, or DDR/LPDDR. - Hands-on experience using oscilloscopes, logic analyzers, spectrum/signal analyzers, power supplies, and other silicon bring-up and validation equipment. - Demonstrated ability to debug complex problems spanning hardware, firmware/software, and system boundaries. - Ability to read schematics, silicon specifications, register maps, timing diagrams, and hardware design documentation. - Must be a U.S. citizen or national, U.S. permanent resident (current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum. Preferred Qualifications list: - Experience with first-silicon bring-up of complex custom ASICs or SoCs. - Experience developing post-silicon validation frameworks, diagnostics, and automated regression environments. - Experience debugging high-speed SerDes, PCIe, DDR/LPDDR, Ethernet, or custom chip-to-chip interfaces. - Experience with mixed-signal SoCs containing ADCs, DACs, PLLs, clocking, RF, or other analog/mixed-signal subsystems. - Understanding of signal integrity, power integrity, clocking, reset sequencing, and board-level effects on silicon operation. - Familiarity with Linux device drivers, embedded RTOS environments, boot flows, and low-level firmware. - Experience with silicon characterization across voltage, temperature, frequency, and process corners. - Experience supporting root-cause analysis and validating RTL, firmware, software, or silicon fixes. Benefits list: - Medical, dental, vision, basic and supplemental life insurance, paid parental leave, short and long-term disability, 401(k) with a company match of up to 5%, and an Education Support Program. - Stock Options for all regular employees (working at least 20 hours/week) - Paid Time Off: Up to four (4) weeks per year based on weekly scheduled hours, and up to 14 company-paid holidays. - Dependent on role type and job level, employees may be eligible for benefits and bonuses based on the company's intent to reward individual contributions and enable them to share in the company's results, or other factors at the company's sole discretion. Bonus amounts and eligibility are not guaranteed and subject to change and cancellation. Please check with your recruiter for more details. We could keep as prose or list. Since it's a list of benefits, we can use
  • . Pay section: Provide the base pay range info. Could be a

    . Now About the role: We'll combine the introductory paragraphs and the Job Description sentence. Let's craft About the role content as maybe two paragraphs. Paragraph1: At Blue Origin, we envision millions of people living and working in space for the benefit of Earth. We’re working to develop reusable, safe, and low-cost space vehicles and systems within a culture of safety, collaboration, and inclusion. Join our team of problem solvers as we add new chapters to the history of spaceflight! Paragraph2: Blue Origin is pioneering the future of space-based communications with TeraWave, a revolutionary satellite communications network designed to deliver symmetrical data speeds of up to 6 Tbps anywhere on Earth. This multi-orbit constellation will consist of optically interconnected satellites in low Earth orbit (LEO) and medium Earth orbit (MEO), providing enterprise-grade connectivity for critical operations worldwide. Paragraph3: Job Description As a Sr Silicon Bring-Up and Integration Engineer, you will be a key hands-on member of the team responsible for bringing complex custom SoCs and ASICs from pre-silicon development through physical silicon bring-up, validation, and system integration. You will develop low-level C/C++ software, diagnostics, and Python-based test infrastructure used to configure, control, exercise, and validate custom silicon. You will work closely with ASIC design, verification, firmware, board, RF/DSP, and system engineering teams to support first-silicon bring-up, characterize device behavior, and debug complex hardware/software integration issues. This role is highly technical and hands-on and requires the ability to work across silicon hardware, low-level software, lab instrumentation, and system-level debugging. We could keep as one paragraph but it's long; better split. Now we must not include any boilerplate like "Application Close Date", "Culture Statement", "Export Control Regulations", "Background Check", "Equal Employment Opportunity", etc. Also remove "Special Mentions" lines? Those contain relocation, travel, interviews, location. Those are substantive? They mention relocation provided, travel expected up to 20%, interviews will include a technical assessment, role based onsite in San Diego, Kent, WA, or Austin, TX. Temporary remote work exception. This is specific info about the role. Should we include? The instruction: include sections only when posting has real specific content. There's no specific heading for "Special Mentions". Could we incorporate that info into About the role or maybe a separate section like "Details"? But we only allowed headings from the list. Could we put location info under About the role? Possibly. But the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid adding other headings, but says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies we