Embedded Software 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. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate like EEO, equal-opportunity, scam-warning, navigation, cookie, legal, application instructions. Also remove duplicated lines. We need to parse the posting. Content: - Intro about Heaviside Industries (company description). This could be "About the role"? Actually "About Heaviside Industries" is company overview. Could be placed under "About the role"? Usually "About the role" is description of role. But we have "What You Will Do" which is responsibilities. Also "What We Are Looking For" which is requirements/qualifications/skills. Also "NICE TO HAVE". Also compensation info: "Additional Compensation bands are determined by role, level, location, and alignment with market data. Individual level and base pay is determined on a case-by-case basis and may vary based on job-related skills, education, experience, technical capabilities and internal equity. In addition to base salary, for full-time hires, you may also be eligible for long-term incentives, in the form of stock options, and access to medical, vision & dental coverage as well as access to a 401(k) retirement plan." That's about Pay and Benefits. Also "To conform to U.S. Government space technology export regulations..." is about citizenship requirement (ITAR). That's a requirement. Also "Heaviside is an Equal Opportunity Employer..." is boilerplate to remove. Thus sections: - About the role: maybe we can include company description? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have About the role (maybe a brief description of the role). But we have "What You Will Do" which is responsibilities. So we could treat "About the role" as a short summary: maybe combine company description and role purpose? But we must not invent. We can include the company description under About the role? It's not exactly about the role but about the company. However we could still put it there as it's substantive. The instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should stick to those. We can put company overview under About the role. Responsibilities: from "What You Will Do" bullet list. Requirements: from "What We Are Looking For" bullet list (mandatory). Also include ITAR citizenship requirement as a requirement. Qualifications: maybe we can separate "NICE TO HAVE" as Qualifications? Or Skills? The instruction includes Qualifications and Skills separate. We could put "NICE TO HAVE" under Qualifications or Skills. Since they are nice-to-have experience/skills. Could treat as Qualifications. Skills: maybe we can list specific technical skills like Embedded C/C++, debugging, API integration, testing, documentation, etc. But those are already in requirements. Could split: Requirements = mandatory experience; Skills = technical skills (Embedded C/C++, debugging, etc). Qualifications = nice-to-have. Benefits: from compensation paragraph: medical, vision & dental, 401(k), stock options. Pay: from compensation paragraph: base salary determined case-by-case, long-term incentives (stock options). Could mention that pay is determined case-by-case, but we must not include filler like "commensurate with experience". However the text says "Individual level and base pay is determined on a case-by-case basis and may vary based on job-related skills, education, experience, technical capabilities and internal equity." That's substantive; we can include that. Also "Additional Compensation bands are determined by role, level, location, and alignment with market data." That's also substantive. So we can include Pay section with those sentences. Schedule: not mentioned; no info about schedule (full-time hires mentioned but not schedule). So we should not create Schedule section. We must not include boilerplate like EEO, etc. We must not include duplicated lines. We need to output only HTML fragment, no markdown fences. Let's craft. Structure:

About the role

Heaviside Industries builds multi-domain autonomous precision munitions for U.S. and allied special operations and conventional forces. The company designs economical precision strike capabilities for GPS-denied and spectrum-jammed battlefields, with all engineering and manufacturing conducted in-house at its Los Angeles, CA headquarters and Oslo, Norway office.

Responsibilities

• Design, write, and debug firmware for microcontrollers and embedded Linux platforms (including Raspberry Pi) that control sensors, actuators, and other production-floor hardware
• Translate systems-level requirements from hardware, controls, and manufacturing engineering into embedded software architecture and code
• Build and maintain integrations with our Manufacturing Execution System (MES) API — pushing machine and process data up, and pulling work orders, recipes, and routing instructions down
• Write unit and integration tests, and build validation fixtures to verify firmware behavior against requirements
• Debug field issues across the stack, from hardware/electrical faults up through firmware and network communication
• Document architecture, interfaces, and requirements traceability so systems and software stay in sync
• Collaborate with hardware, systems, and manufacturing engineering teams throughout the product lifecycle, from prototype to production deployment

Requirements

• Experience designing and debugging firmware for microcontrollers and/or embedded Linux platforms
• Ability to translate cross-functional systems requirements (hardware, controls, manufacturing) into embedded software design
• Experience integrating with APIs or external systems (e.g., MES, ERP, or similar production/data systems)
• Strong testing discipline — comfortable writing unit/integration tests and building validation fixtures
• Full-stack debugging skills spanning hardware/electrical, firmware, and network layers
• Solid documentation habits, especially around architecture and requirements traceability
• Comfortable working cross-functionally with hardware, systems, and manufacturing engineers across the full product lifecycle
• Proficiency in Embedded C and/or C++
• U.S. Person as defined by ITAR (22 CFR120.62)

Qualifications

• Experience with C# and/or Python
• Prior work in a manufacturing or production-floor environment
• Familiarity with Manufacturing Execution Systems (MES) specifically
• Experience with Raspberry Pi or similar SBC platforms in a production setting

Skills

Embedded C/C++ programming, firmware debugging, API integration, unit and integration testing, validation fixture development, hardware/electrical troubleshooting, network communication debugging, documentation and requirements traceability.

Benefits

• Medical, vision & dental coverage
• Access to a 401(k) retirement plan
• Long-term incentives in the form of stock options (for full-time hires)

Pay

Additional compensation bands are determined by role, level, location, and alignment with market data. Individual level and base pay is determined on a case‑by‑case basis and may vary based on job‑related skills, education, experience, technical capabilities and internal equity. In addition to base salary, full‑time hires may be eligible for long‑term incentives (stock options).

We should not include Schedule section. Check for any duplicated content: We have responsibilities list includes "Write unit and integration tests, and build validation fixtures to verify firmware behavior against requirements". That's fine. We have Skills paragraph summarizing some of those; okay. We have Benefits list includes medical, vision & dental, 401(k), stock options. The original text also mentions "access to medical, vision & dental coverage as well as access to a 401(k) retirement plan." and "long-term incentives, in the form of stock options". Good. We have Pay section includes the compensation bands and case-by-case base pay and long-term incentives. Might be slightly redundant with Benefits but okay. We removed EEO, ITAR explanation beyond requirement, navigation, etc. Check for any leftover boilerplate: The sentence "To conform to U.S. Government space technology export regulations, including the International Traffic in Arms Regulations (ITAR) you must be a U.S. citizen, lawful permanent resident of the U.S., protected individual as defined by 8 U.S.C. 1324b(a)(3), or eligible to obtain the required authorizations from the U.S. Department of State. Learn more about the ITAR here." We incorporated only the requirement "U.S. Person as defined by ITAR (22 CFR120.62)". We omitted the rest. That's okay. Check for any mention of "Learn more about the ITAR here." removed. Check for any mention of "Heaviside is an Equal Opportunity Employer..." removed. Check for any mention of "Additional Compensation bands are determined by role, level, location, and alignment with market data." included. Check for any mention of "Individual level and base pay is determined on a case-by-case basis..." included. Check for any mention of "In addition to base salary, for full-time hires, you may also be eligible for long-term incentives, in the form of stock options, and access to medical, vision & dental coverage as well as access to a 401(k) retirement plan." we split into Benefits and Pay. Check for any mention of "All engineering and manufacturing is conducted in-house in Heaviside's Los Angeles, CA headquarters and Oslo, Norway office." included in About the role. Check for any mention of "Heaviside builds precision munitions designed to operate in GPS-denied and spectrum-jammed battlefields—where traditional systems degrade or fail—without inflated prices or sacrifice to performance." Not included. Should we include? It's substantive about company. Could add to About the role. Let's incorporate a sentence. Also "While modern warfare has rapidly evolved with the proliferation of unmanned systems, hyper-precise munitions in contested environments are the future of the battlefield. Economical precision strike capabilities are critical to U.S. and allied war efforts, enabling successful defeat of enemy military assets and infrastructure." Could also include. We should preserve ALL substantive information. So we need to include those descriptive sentences about the company and mission. Let's add them to About the role. Thus About the role paragraph(s) could be multiple

tags. We must not invent. So we will include those sentences. Let's craft About the role:

Heaviside Industries builds multi-domain autonomous precision munitions for U.S. and allied special operations and conventional forces. While modern warfare has rapidly evolved with the proliferation of unmanned systems, hyper-precise munitions in contested environments are the future of the battlefield. Economical precision strike capabilities are critical to U.S. and allied war efforts, enabling successful defeat of enemy military assets and infrastructure. Heaviside builds precision munitions designed to operate in GPS-denied and spectrum-jammed battlefields—where traditional systems degrade or fail—without inflated prices or sacrifice to performance. All engineering and manufacturing is conducted in-house in Heaviside's Los Angeles, CA headquarters and Oslo, Norway office.

That's good. Now ensure we didn't miss any other substantive info: The "NICE TO HAVE" list we captured as Qualifications. Good. Check for any other info: "Additional Compensation bands are determined by role, level, location, and alignment with market data." included. "Individual level and base pay is determined on a case-by-case basis and may vary based on job-related skills,