Senior Firmware Engineer, Security
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include. The posting includes:
- Application Close Date (metadata) - can be folded into short
maybe.
- Vision statement: "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."
That's about the company/role context. Could be "About the role" or "About the team". Use
About the role
and then with that content.
- Job Description: "As part of a hardworking team of specialists and engineers, you will develop low-level firmware for the secure enclaves of custom ASICs in the TeraWave system. You will work closely with silicon, software, security, and system engineering teams to develop the foundational firmware required to securely boot, provision, operate, update, monitor, and recover custom silicon throughout its lifecycle."
That's prose; could be part of About the role or separate "Job Description". But we can combine.
- Responsibilities: list of bullet points (multiple lines). Should be
Responsibilities
then - each.
- Minimum Qualifications: list of bullet points (multiple). Should be
Minimum Qualifications
then .
- Preferred Qualifications: list of bullet points. Should be Preferred Qualifications
then .
- Special Mentions: "Relocation provided", "Interviews will include a technical assessment". That's not a standard heading but could be under "Special Mentions" but not in list of allowed headings. The allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They say use those as examples, but not strictly limited? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also use other headings if needed but better to stick to those. "Special Mentions" could be folded into "About the role" or maybe "Benefits"? Relocation provided is a benefit. Could be under Benefits. Interviews will include a technical assessment could be under Responsibilities? Not really. Could be under "About the role". We'll include relocation under Benefits.
- Base Pay Range: includes specific numbers for CA and WA applicants. That's pay info, so we should include a Pay section. The posting states: "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 ranges. So we should include Pay
with
containing that info.
- Culture Statement: that's a paragraph encouraging applicants; could be part of About the role or separate but we can include under About the role.
- Export Control Regulations: that's legal boilerplate; should be removed per instruction (remove legal/EEO etc). So drop.
- Background Check Required: also legal boilerplate; drop.
- Benefits: list of benefits. Should be
Benefits
with .
- Equal Employment Opportunity etc: drop.
- Affirmative Action and Disability Accommodation: drop.
Thus sections: About the role (including vision, job description, culture statement), Responsibilities, Minimum Qualifications, Preferred Qualifications, Pay, Benefits.
We should not include Requirements as separate if we have Minimum and Preferred Qualifications; but we could combine them under Qualifications. However instructions allow Qualifications heading. Could do Qualifications
with sub-sections? But they said use for section headings; we could have Minimum Qualifications and Preferred Qualifications as separate headings. That's fine.
We need to preserve all substantive information. Ensure we don't lose any bullet points.
Let's extract bullet points exactly.
Responsibilities list:
- Develop ROM code, bootloaders, and runtime firmware for secure enclaves within custom ASICs.
- Design and implement firmware supporting secure boot, device attestation, and root-of-trust functionality.
- Develop firmware infrastructure for OTA updates, recovery, and secure firmware lifecycle management.
- Support manufacturing provisioning, including device identity, keys, credentials, and secure configuration.
- Develop and support secure debug, telemetry, tamper monitoring, and device recovery mechanisms.
- Work closely with ASIC, security, software, and system teams to define hardware/software interfaces and security requirements.
- Support pre-silicon firmware development and validation using simulation, emulation, FPGA, or other available development platforms.
- Support silicon bring-up, debugging, validation, and production deployment of secure-enclave firmware.
- Develop high-quality, maintainable embedded software with appropriate unit testing, code review, and documentation.
Minimum Qualifications list:
- Bachelor's degree in Electrical Engineering, Computer Engineering, Computer Science, or a related technical field.
- 8+ years of experience developing embedded software or firmware for complex SoCs, ASICs, microcontrollers, or similar embedded systems.
- Strong programming experience in C/C++ and low-level embedded software development.
- Experience developing bootloaders, ROM code, board-support software, device drivers, or low-level firmware.
- Strong understanding of embedded processor architectures, memory maps, interrupts, peripherals, and hardware/software interfaces.
- Experience debugging embedded systems using tools such as JTAG, trace, logic analyzers, or equivalent debugging environments.
- Experience with embedded security concepts such as secure boot, root of trust, cryptographic key management, device identity, or secure firmware updates.
- Ability to work closely with ASIC and hardware teams during pre-silicon development and silicon bring-up.
Preferred Qualifications list:
- Experience developing firmware specifically for secure enclaves, hardware roots of trust, or security subsystems.
- Experience with manufacturing provisioning, device attestation, anti-rollback, secure debug, and tamper detection.
- Experience with cryptographic hardware accelerators, key storage, OTP/eFuse, TRNG, or secure memory.
- Experience with custom ASIC or SoC pre-silicon verification and post-silicon bring-up.
- Experience developing firmware for high-reliability, aerospace, satellite, communications, networking, or other complex systems.
- Familiarity with ARM or RISC-V processor architectures and associated embedded development environments.
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 need to keep that last sentence as part of Benefits? It's a paragraph; we can put as
after the list.
Pay section: "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". We'll put as
.
About the role section: combine vision, job description, culture statement.
Vision paragraph: "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."
Job Description paragraph: "As part of a hardworking team of specialists and engineers, you will develop low-level firmware for the secure enclaves of custom ASICs in the TeraWave system. You will work closely with silicon, software, security, and system engineering teams to develop the foundational firmware required to securely boot, provision, operate, update, monitor, and recover custom silicon throughout its lifecycle."
Culture Statement paragraph: "Don’t meet all desired requirements? Studies have shown that some people are less likely to apply to jobs unless they meet every single desired qualification. At Blue Origin, we are dedicated to building an authentic workplace, so if you’re excited about this role but your past experience doesn’t align perfectly with every desired qualification in the job description, we encourage you to apply anyway. You may be just the right candidate for this or other roles."
We could also include "Application Close Date Applications will be accepted on an ongoing basis until the requisition is closed." That's metadata; we can fold into a short
maybe under About the role or separate small paragraph. But instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short
for that. Probably better to include it as a short paragraph at top.
Thus final HTML:
Application Close Date: Applications will be accepted on an ongoing basis until the requisition is closed.
About the role
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
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: - Application Close Date (metadata) - can be folded into short
maybe. - Vision statement: "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." That's about the company/role context. Could be "About the role" or "About the team". Use
About the role
and thenwith that content. - Job Description: "As part of a hardworking team of specialists and engineers, you will develop low-level firmware for the secure enclaves of custom ASICs in the TeraWave system. You will work closely with silicon, software, security, and system engineering teams to develop the foundational firmware required to securely boot, provision, operate, update, monitor, and recover custom silicon throughout its lifecycle." That's prose; could be part of About the role or separate "Job Description". But we can combine. - Responsibilities: list of bullet points (multiple lines). Should be
Responsibilities
then- each.
- Minimum Qualifications: list of bullet points (multiple). Should be
Minimum Qualifications
then- .
- Preferred Qualifications: list of bullet points. Should be
Preferred Qualifications
then- .
- Special Mentions: "Relocation provided", "Interviews will include a technical assessment". That's not a standard heading but could be under "Special Mentions" but not in list of allowed headings. The allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They say use those as examples, but not strictly limited? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also use other headings if needed but better to stick to those. "Special Mentions" could be folded into "About the role" or maybe "Benefits"? Relocation provided is a benefit. Could be under Benefits. Interviews will include a technical assessment could be under Responsibilities? Not really. Could be under "About the role". We'll include relocation under Benefits. - Base Pay Range: includes specific numbers for CA and WA applicants. That's pay info, so we should include a Pay section. The posting states: "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 ranges. So we should include
Pay
withcontaining that info. - Culture Statement: that's a paragraph encouraging applicants; could be part of About the role or separate but we can include under About the role. - Export Control Regulations: that's legal boilerplate; should be removed per instruction (remove legal/EEO etc). So drop. - Background Check Required: also legal boilerplate; drop. - Benefits: list of benefits. Should be
Benefits
with- .
- Equal Employment Opportunity etc: drop.
- Affirmative Action and Disability Accommodation: drop.
Thus sections: About the role (including vision, job description, culture statement), Responsibilities, Minimum Qualifications, Preferred Qualifications, Pay, Benefits.
We should not include Requirements as separate if we have Minimum and Preferred Qualifications; but we could combine them under Qualifications. However instructions allow Qualifications heading. Could do
Qualifications
with sub-sections? But they said usefor section headings; we could have Minimum Qualifications and Preferred Qualifications as separate headings. That's fine. We need to preserve all substantive information. Ensure we don't lose any bullet points. Let's extract bullet points exactly. Responsibilities list: - Develop ROM code, bootloaders, and runtime firmware for secure enclaves within custom ASICs. - Design and implement firmware supporting secure boot, device attestation, and root-of-trust functionality. - Develop firmware infrastructure for OTA updates, recovery, and secure firmware lifecycle management. - Support manufacturing provisioning, including device identity, keys, credentials, and secure configuration. - Develop and support secure debug, telemetry, tamper monitoring, and device recovery mechanisms. - Work closely with ASIC, security, software, and system teams to define hardware/software interfaces and security requirements. - Support pre-silicon firmware development and validation using simulation, emulation, FPGA, or other available development platforms. - Support silicon bring-up, debugging, validation, and production deployment of secure-enclave firmware. - Develop high-quality, maintainable embedded software with appropriate unit testing, code review, and documentation. Minimum Qualifications list: - Bachelor's degree in Electrical Engineering, Computer Engineering, Computer Science, or a related technical field. - 8+ years of experience developing embedded software or firmware for complex SoCs, ASICs, microcontrollers, or similar embedded systems. - Strong programming experience in C/C++ and low-level embedded software development. - Experience developing bootloaders, ROM code, board-support software, device drivers, or low-level firmware. - Strong understanding of embedded processor architectures, memory maps, interrupts, peripherals, and hardware/software interfaces. - Experience debugging embedded systems using tools such as JTAG, trace, logic analyzers, or equivalent debugging environments. - Experience with embedded security concepts such as secure boot, root of trust, cryptographic key management, device identity, or secure firmware updates. - Ability to work closely with ASIC and hardware teams during pre-silicon development and silicon bring-up. Preferred Qualifications list: - Experience developing firmware specifically for secure enclaves, hardware roots of trust, or security subsystems. - Experience with manufacturing provisioning, device attestation, anti-rollback, secure debug, and tamper detection. - Experience with cryptographic hardware accelerators, key storage, OTP/eFuse, TRNG, or secure memory. - Experience with custom ASIC or SoC pre-silicon verification and post-silicon bring-up. - Experience developing firmware for high-reliability, aerospace, satellite, communications, networking, or other complex systems. - Familiarity with ARM or RISC-V processor architectures and associated embedded development environments. 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 need to keep that last sentence as part of Benefits? It's a paragraph; we can put as
after the list. Pay section: "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". We'll put as
. About the role section: combine vision, job description, culture statement. Vision paragraph: "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." Job Description paragraph: "As part of a hardworking team of specialists and engineers, you will develop low-level firmware for the secure enclaves of custom ASICs in the TeraWave system. You will work closely with silicon, software, security, and system engineering teams to develop the foundational firmware required to securely boot, provision, operate, update, monitor, and recover custom silicon throughout its lifecycle." Culture Statement paragraph: "Don’t meet all desired requirements? Studies have shown that some people are less likely to apply to jobs unless they meet every single desired qualification. At Blue Origin, we are dedicated to building an authentic workplace, so if you’re excited about this role but your past experience doesn’t align perfectly with every desired qualification in the job description, we encourage you to apply anyway. You may be just the right candidate for this or other roles." We could also include "Application Close Date Applications will be accepted on an ongoing basis until the requisition is closed." That's metadata; we can fold into a short
maybe under About the role or separate small paragraph. But instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short
for that. Probably better to include it as a short paragraph at top. Thus final HTML:
Application Close Date: Applications will be accepted on an ongoing basis until the requisition is closed.
About the role
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