Sr. Embedded Software Engineer, Mobile Robotics
for each section heading. Use - for any list of duties/requirements/benefits, and
for prose. Include only sections with real specific content. Remove boilerplate like EEO, accommodation, etc. Also remove application instructions, duplicated lines, cookie/navigation/legal. Keep substantive info.
We need to parse the description.
Key parts:
- Intro: Amazon Robotics seeking Senior Embedded Software Engineer to help lead development of safety-rated sensor processing firmware. You will set technical direction for major subsystems of perception-inferencing stack (real-time safety applications, sensor processing pipelines, system interfaces on heterogeneous multi-core MCU/CPU/GPU platforms) that let robots detect and respond to obstacles safely and reliably. You will own the team's hardest end-to-end problems, framing solutions where business need is clear but technical strategy not, and raise bar for engineers. Looking for technical leader deeply proficient in Rust (or strong in C/C++ and eager to work in Rust), fluent across boundary between RTOS and Linux on same chip, substantial experience with sensor data acquisition or signal processing, can architect systems meeting IEC 61508 functional safety certification. Influence beyond immediate team, shaping designs, resolving escalations, mitigating long-term one-way-door risks, mentoring engineers, collaborating closely with hardware, functional safety, navigation teams to deliver firmware where correctness is not optional.
- Key job responsibilities (section heading maybe "Responsibilities"): bullet list: The Ideal Candidate Is a Force Multiplier Who Sets Technical Direction Across Teams And Raises The Bar For Associate Safety. They Will Lead the design and architecture of major safety-rated and non-safety-rated firmware subsystems in Rust on heterogeneous multi-core platforms, where real-time safety code and Linux services coexist on the same chip. Set technical direction across the full sensor processing pipeline (driver integration, frame acquisition, point cloud generation, collision detection) and influence peer hardware, safety, and navigation teams. Own the team's hardest end-to-end problems, framing solutions where the business problem is known but the technical strategy is not. Raise the technical bar through design and code reviews, and mentor engineers so the team is more reliable because of your presence but does not require it. Produce direction-setting design documents and safety analysis artifacts that meet the rigor of third-party certification and witness testing. Lead debugging and root-cause analysis end-to-end, from raw sensor data to safety responses, on real robots at test facilities and in production. Leverage AI coding assistants as a force multiplier and lead the team to do the same.
- A day in the life: description of typical activities. Could be part of responsibilities or separate section? Might be considered responsibilities but we can include as part of responsibilities or separate "Day in the Life". However we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "A day in the life" could be part of About the role or Responsibilities. Probably include in About the role as prose.
- About The Team: description of team. Could be part of About the role.
- Basic Qualifications: list: 6+ years of non-internship professional software development experience; 6+ years of programming with at least one software programming language experience; 6+ years of leading design or architecture (design patterns, reliability and scaling) of new and existing systems experience; Experience as a mentor, tech lead or leading an engineering team; Proficiency in embedded development in Rust; alternatively, strong modern C/C++ embedded experience with demonstrated willingness and ability to work in Rust.
- Preferred Qualifications: list: 6+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience; Bachelor's degree in computer science or equivalent; Experience developing RTOS applications or bare-metal real-time systems; Experience with heterogeneous multi-core platforms (e.g., ARM Cortex-A + Cortex-R/M + GPUs); Experience with general troubleshooting and debugging of hardware; Experience writing low-level drivers (V4L2, I2C, SPI, DMA); Experience with gRPC, Protocol Buffers, or similar RPC/serialization frameworks; Familiarity developing embedded software in a safety-standards-controlled environment such as IEC 61508 or ISO 26262; Working knowledge of 3D geometry, coordinate transforms, or point cloud processing; Experience with robotics middleware (ROS/ROS2) or visualization tools (Foxglove, RViz).
- Benefits: description: Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at link (but we should drop link? It's part of benefits but maybe we keep description but not the link? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is substantive? It's a URL for more info. Might be considered boilerplate? It's not navigation/legal/EEO. It's a benefits link. Could keep as part of benefits but it's a URL. Probably okay to keep as plain text.
- Pay: The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Then lists: USA, MA, North Reading - 168,100.00 - 227,400.00 USD annually; USA, MA, Westboro - 168,100.00 - 227,400.00 USD annually. Also Company - Amazon.com Services LLC Job ID: A10553568 (but we should not put Job ID as heading; we can fold minor metadata into short
or drop it. Probably drop Job ID. Keep location and salary range.
- Schedule: Not mentioned. So we should not create Schedule section.
- Skills: Could be derived from qualifications but we have separate sections Requirements, Qualifications, Skills. The instruction: Prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But we have headings defined; we should only include sections when posting has real specific content. We have content for Responsibilities, About the role (maybe combine About the role and About the Team), Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe we can list specific technical skills like Rust, C/C++, RTOS, Linux, sensor processing, etc.) but we already have those in qualifications. Could create Skills section summarizing key skills: Rust, C/C++, embedded development, RTOS/Linux, sensor data acquisition, signal processing, heterogeneous multi-core, IEC 61508, driver development, gRPC/Protobuf, 3D geometry, ROS, etc. But that might be redundant. However we need to follow instruction: Use sections only when posting has real specific content. The posting does have specific content for skills (list of proficiencies). So we can create a Skills section with bullet list.
But we must not repeat content unnecessarily? It's okay to repeat if it's from posting. However we should aim to not duplicate too much. Could combine Basic and Preferred qualifications into Requirements and Qualifications sections. Skills could be a separate section highlighting specific technical proficiencies.
Let's decide sections:
- About the role: include intro paragraph, About the Team, A day in the life (maybe as prose). Could be one
or multiple
.
- Responsibilities: bullet list of key job responsibilities.
- Requirements: Basic Qualifications bullet list.
- Qualifications: Preferred Qualifications bullet list.
- Skills: bullet list of specific technical skills (maybe derived from both Basic and Preferred). Could include: Rust, C/C++, embedded development, RTOS, Linux, sensor data acquisition, signal processing, heterogeneous multi-core (ARM Cortex-A/R/M + GPU), low-level drivers (V4L2, I2C, SPI, DMA), gRPC, Protocol Buffers, IEC 61508, ISO 26262, 3D geometry/coordinate transforms/point cloud processing, ROS/ROS2, Foxglove/RViz, AI coding assistants, debugging, mentoring, design/architecture, safety analysis, CI/CD, etc.
- Benefits: bullet list of benefits (health insurance details, 401(k) matching, paid time off, parental leave). Could also include sign-on payments and RSUs? That's compensation not benefits. Might be part of Pay.
- Pay: paragraph about base salary range, sign-on payments, RSUs, location-specific ranges.
- Schedule: not present, omit.
We must not include boilerplate like EEO, accommodation, etc. Also remove duplicated lines (like repeated "Amazon is an equal opportunity employer").
Now produce HTML fragment: only the HTML, no markdown fences.
We'll need to wrap sections in appropriate tags: each section heading
then content: either
for prose or
- for lists.
We must not include or .
Let's craft.
First, About the role:
We can have multiple paragraphs: intro, About the Team, A day in the life.
We'll combine into maybe two
elements.
Paragraph 1: Intro + About the Team? Actually About the Team is separate but we can include.
Let's write:
Amazon Robotics is seeking a Senior Embedded Software Engineer to help lead development of safety-rated sensor processing firmware. You will set technical direction for major subsystems of the perception‑inferencing stack (real‑time safety applications, sensor processing pipelines, and system interfaces on heterogeneous multi‑core MCU/CPU/GPU platforms) that let robots in Amazon facilities worldwide detect and respond to obstacles safely and reliably. You will own the team's hardest end‑to‑end problems, framing solutions where the business need is clear but the technical strategy is not, and raise the bar for the engineers around you.
As part of the world‑leading Safety Firmware team, you will develop embedded safety systems deployed across Amazon's robotic fleet, integrating safety considerations from initial design through delivery to meet ambitious schedules without compromising quality. A typical day might involve aligning peer teams around a subsystem architecture in a design review, heading to the test floor to lead cross‑functional debugging, profiling pipelines to close latency budgets, and pairing with engineers to unblock their work.
That covers About the role.
Now Responsibilities: bullet list.
We'll extract bullet points from "Key job responsibilities" and "The Ideal Candidate Is a Force Multiplier..." etc.
List items:
- Lead the design and architecture of major safety-rated and non-safety-rated firmware subsystems in Rust on heterogeneous multi-core platforms, where real-time safety code and Linux services coexist on the same chip.
- Set technical direction across the full sensor processing pipeline (driver integration, frame acquisition, point cloud generation, collision detection) and influence peer hardware, safety, and navigation teams.
- Own the team's hardest end-to-end problems, framing solutions where the business problem is known but the technical strategy is not.
- Raise the technical bar through design and code reviews, and mentor engineers so the team is more reliable because of your presence but does not require it.
- Produce direction-setting design documents and safety analysis artifacts that meet the rigor of third-party certification and witness testing.
- Lead debugging and root-cause analysis end-to-end, from raw sensor data to safety responses, on real robots at test facilities and in production.
- Leverage AI coding assistants as a force multiplier and lead the team to do the same.
We'll put each as - .
Now Requirements: Basic Qualifications bullet list.
Items:
- 6+ years of non-internship professional software development experience
- 6+ years of programming with at least one software programming language
- 6+ years of leading design
for prose. Include only sections with real specific content. Remove boilerplate like EEO, accommodation, etc. Also remove application instructions, duplicated lines, cookie/navigation/legal. Keep substantive info. We need to parse the description. Key parts: - Intro: Amazon Robotics seeking Senior Embedded Software Engineer to help lead development of safety-rated sensor processing firmware. You will set technical direction for major subsystems of perception-inferencing stack (real-time safety applications, sensor processing pipelines, system interfaces on heterogeneous multi-core MCU/CPU/GPU platforms) that let robots detect and respond to obstacles safely and reliably. You will own the team's hardest end-to-end problems, framing solutions where business need is clear but technical strategy not, and raise bar for engineers. Looking for technical leader deeply proficient in Rust (or strong in C/C++ and eager to work in Rust), fluent across boundary between RTOS and Linux on same chip, substantial experience with sensor data acquisition or signal processing, can architect systems meeting IEC 61508 functional safety certification. Influence beyond immediate team, shaping designs, resolving escalations, mitigating long-term one-way-door risks, mentoring engineers, collaborating closely with hardware, functional safety, navigation teams to deliver firmware where correctness is not optional. - Key job responsibilities (section heading maybe "Responsibilities"): bullet list: The Ideal Candidate Is a Force Multiplier Who Sets Technical Direction Across Teams And Raises The Bar For Associate Safety. They Will Lead the design and architecture of major safety-rated and non-safety-rated firmware subsystems in Rust on heterogeneous multi-core platforms, where real-time safety code and Linux services coexist on the same chip. Set technical direction across the full sensor processing pipeline (driver integration, frame acquisition, point cloud generation, collision detection) and influence peer hardware, safety, and navigation teams. Own the team's hardest end-to-end problems, framing solutions where the business problem is known but the technical strategy is not. Raise the technical bar through design and code reviews, and mentor engineers so the team is more reliable because of your presence but does not require it. Produce direction-setting design documents and safety analysis artifacts that meet the rigor of third-party certification and witness testing. Lead debugging and root-cause analysis end-to-end, from raw sensor data to safety responses, on real robots at test facilities and in production. Leverage AI coding assistants as a force multiplier and lead the team to do the same. - A day in the life: description of typical activities. Could be part of responsibilities or separate section? Might be considered responsibilities but we can include as part of responsibilities or separate "Day in the Life". However we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "A day in the life" could be part of About the role or Responsibilities. Probably include in About the role as prose. - About The Team: description of team. Could be part of About the role. - Basic Qualifications: list: 6+ years of non-internship professional software development experience; 6+ years of programming with at least one software programming language experience; 6+ years of leading design or architecture (design patterns, reliability and scaling) of new and existing systems experience; Experience as a mentor, tech lead or leading an engineering team; Proficiency in embedded development in Rust; alternatively, strong modern C/C++ embedded experience with demonstrated willingness and ability to work in Rust. - Preferred Qualifications: list: 6+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience; Bachelor's degree in computer science or equivalent; Experience developing RTOS applications or bare-metal real-time systems; Experience with heterogeneous multi-core platforms (e.g., ARM Cortex-A + Cortex-R/M + GPUs); Experience with general troubleshooting and debugging of hardware; Experience writing low-level drivers (V4L2, I2C, SPI, DMA); Experience with gRPC, Protocol Buffers, or similar RPC/serialization frameworks; Familiarity developing embedded software in a safety-standards-controlled environment such as IEC 61508 or ISO 26262; Working knowledge of 3D geometry, coordinate transforms, or point cloud processing; Experience with robotics middleware (ROS/ROS2) or visualization tools (Foxglove, RViz). - Benefits: description: Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at link (but we should drop link? It's part of benefits but maybe we keep description but not the link? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is substantive? It's a URL for more info. Might be considered boilerplate? It's not navigation/legal/EEO. It's a benefits link. Could keep as part of benefits but it's a URL. Probably okay to keep as plain text. - Pay: The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Then lists: USA, MA, North Reading - 168,100.00 - 227,400.00 USD annually; USA, MA, Westboro - 168,100.00 - 227,400.00 USD annually. Also Company - Amazon.com Services LLC Job ID: A10553568 (but we should not put Job ID as heading; we can fold minor metadata into short
or drop it. Probably drop Job ID. Keep location and salary range. - Schedule: Not mentioned. So we should not create Schedule section. - Skills: Could be derived from qualifications but we have separate sections Requirements, Qualifications, Skills. The instruction: Prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But we have headings defined; we should only include sections when posting has real specific content. We have content for Responsibilities, About the role (maybe combine About the role and About the Team), Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe we can list specific technical skills like Rust, C/C++, RTOS, Linux, sensor processing, etc.) but we already have those in qualifications. Could create Skills section summarizing key skills: Rust, C/C++, embedded development, RTOS/Linux, sensor data acquisition, signal processing, heterogeneous multi-core, IEC 61508, driver development, gRPC/Protobuf, 3D geometry, ROS, etc. But that might be redundant. However we need to follow instruction: Use sections only when posting has real specific content. The posting does have specific content for skills (list of proficiencies). So we can create a Skills section with bullet list. But we must not repeat content unnecessarily? It's okay to repeat if it's from posting. However we should aim to not duplicate too much. Could combine Basic and Preferred qualifications into Requirements and Qualifications sections. Skills could be a separate section highlighting specific technical proficiencies. Let's decide sections: - About the role: include intro paragraph, About the Team, A day in the life (maybe as prose). Could be one
or multiple
. - Responsibilities: bullet list of key job responsibilities. - Requirements: Basic Qualifications bullet list. - Qualifications: Preferred Qualifications bullet list. - Skills: bullet list of specific technical skills (maybe derived from both Basic and Preferred). Could include: Rust, C/C++, embedded development, RTOS, Linux, sensor data acquisition, signal processing, heterogeneous multi-core (ARM Cortex-A/R/M + GPU), low-level drivers (V4L2, I2C, SPI, DMA), gRPC, Protocol Buffers, IEC 61508, ISO 26262, 3D geometry/coordinate transforms/point cloud processing, ROS/ROS2, Foxglove/RViz, AI coding assistants, debugging, mentoring, design/architecture, safety analysis, CI/CD, etc. - Benefits: bullet list of benefits (health insurance details, 401(k) matching, paid time off, parental leave). Could also include sign-on payments and RSUs? That's compensation not benefits. Might be part of Pay. - Pay: paragraph about base salary range, sign-on payments, RSUs, location-specific ranges. - Schedule: not present, omit. We must not include boilerplate like EEO, accommodation, etc. Also remove duplicated lines (like repeated "Amazon is an equal opportunity employer"). Now produce HTML fragment: only the HTML, no markdown fences. We'll need to wrap sections in appropriate tags: each section heading
then content: either
for prose or
- for lists.
We must not include or .
Let's craft.
First, About the role:
We can have multiple paragraphs: intro, About the Team, A day in the life.
We'll combine into maybe two
elements. Paragraph 1: Intro + About the Team? Actually About the Team is separate but we can include. Let's write:
Amazon Robotics is seeking a Senior Embedded Software Engineer to help lead development of safety-rated sensor processing firmware. You will set technical direction for major subsystems of the perception‑inferencing stack (real‑time safety applications, sensor processing pipelines, and system interfaces on heterogeneous multi‑core MCU/CPU/GPU platforms) that let robots in Amazon facilities worldwide detect and respond to obstacles safely and reliably. You will own the team's hardest end‑to‑end problems, framing solutions where the business need is clear but the technical strategy is not, and raise the bar for the engineers around you.
As part of the world‑leading Safety Firmware team, you will develop embedded safety systems deployed across Amazon's robotic fleet, integrating safety considerations from initial design through delivery to meet ambitious schedules without compromising quality. A typical day might involve aligning peer teams around a subsystem architecture in a design review, heading to the test floor to lead cross‑functional debugging, profiling pipelines to close latency budgets, and pairing with engineers to unblock their work.
That covers About the role. Now Responsibilities: bullet list. We'll extract bullet points from "Key job responsibilities" and "The Ideal Candidate Is a Force Multiplier..." etc. List items: - Lead the design and architecture of major safety-rated and non-safety-rated firmware subsystems in Rust on heterogeneous multi-core platforms, where real-time safety code and Linux services coexist on the same chip. - Set technical direction across the full sensor processing pipeline (driver integration, frame acquisition, point cloud generation, collision detection) and influence peer hardware, safety, and navigation teams. - Own the team's hardest end-to-end problems, framing solutions where the business problem is known but the technical strategy is not. - Raise the technical bar through design and code reviews, and mentor engineers so the team is more reliable because of your presence but does not require it. - Produce direction-setting design documents and safety analysis artifacts that meet the rigor of third-party certification and witness testing. - Lead debugging and root-cause analysis end-to-end, from raw sensor data to safety responses, on real robots at test facilities and in production. - Leverage AI coding assistants as a force multiplier and lead the team to do the same. We'll put each as - . Now Requirements: Basic Qualifications bullet list. Items: - 6+ years of non-internship professional software development experience - 6+ years of programming with at least one software programming language - 6+ years of leading design