Embedded Systems Engineer

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

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We have: About the role? The description includes a paragraph about role: "The Embedded Systems Engineer will design..." That's about the role. So we can have

About the role

with

containing that paragraph. Responsibilities: list of duties. Use

• . Requirements? The posting has "Essential Skills" and "Additional Skills & Qualifications". Could treat as Requirements and Qualifications sections. We need to decide: Use headings Requirements and Qualifications if content exists. The "Essential Skills" could be Requirements. "Additional Skills & Qualifications" could be Qualifications. Or we could combine. The instruction: Prefer a few substantive sections over many thin ones. But we need to include sections only when posting has real specific content. We have content for Essential Skills and Additional Skills & Qualifications. Could make two sections: Requirements (Essential Skills) and Qualifications (Additional Skills & Qualifications). Or we could make one Skills section covering both. But we have separate headings allowed: Skills, Requirements, Qualifications. We need to decide best mapping. The posting includes "Essential Skills" (list) and "Additional Skills & Qualifications" (list). Also there is "Work Environment", "Job Type & Location", "Pay And Benefits", "Workplace Type", "Application Deadline", "About Actalent", etc. We must remove boilerplate like EEO, legal, etc. Also remove application instructions, etc. We need to preserve substantive info: Work Environment description, Job Type & Location (Contract to Hire based out of Auburn Hills, MI), Pay And Benefits (pay range $60-70/hr, benefits list), Workplace Type (fully onsite in Auburn Hills, MI). Application Deadline (position anticipated to close on Sep 30, 2026) - is that substantive? It's a date; we could include maybe in a short paragraph under a heading? There's no specific heading for deadline; we could fold into a short

  maybe under a generic heading? But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No heading for deadline or work environment etc. However we can include those details in other sections if appropriate, e.g., Work Environment could go under About the role or maybe under Skills? Not ideal. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we must map content to those headings. If a section doesn't have content, we omit it. So we need to decide which of those headings have content. - About the role: we have description paragraph. - Responsibilities: we have list. - Requirements: we have Essential Skills. - Qualifications: we have Additional Skills & Qualifications. - Skills: maybe we could combine essential and additional? But we already used Requirements and Qualifications. Could also have Skills section for overlapping? Might be redundant. Better to use Requirements and Qualifications, omit Skills. - Benefits: we have benefits list. - Pay: we have pay range. - Schedule: we don't have schedule info (like full-time, shift). Not present, so omit Schedule. We also have Work Environment, Job Type & Location, Workplace Type, Application Deadline, About Actalent. Those are not among allowed headings; we must either fold them into existing sections or drop them if they are not essential? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info somewhere. We can incorporate them into About the role or maybe into a generic

  without heading? 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 says use

  for section headings (e.g. ...). Likely they want us to use those headings for sections; we could still add other headings if needed, but they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the allowed headings. To be safe, we should only use those headings and embed other info within those sections. Thus we need to incorporate Work Environment, Job Type & Location, Workplace Type, Application Deadline, About Actalent into About the role or maybe Responsibilities? Probably About the role can include a paragraph describing the role, work environment, location, etc. We'll keep the original role description paragraph and then add additional sentences about work environment, location, contract type, deadline, and about Actalent (maybe brief). But we must not invent or summarize away detail; we can just concatenate the existing sentences. We need to ensure we don't include boilerplate like EEO, legal, etc. Remove those. Let's extract substantive paragraphs: From description: "The Embedded Systems Engineer will design, develop, and maintain firmware that powers small unmanned aircraft systems and associated ground equipment for demanding mission applications. You will work across flight-controller integration, battery management, motor control, lighting systems, and communication links, covering the embedded stack from bootloaders and device drivers through control loops and PX4 integration. This role offers the opportunity to see your firmware operating on real aircraft within weeks, with direct exposure to the full product lifecycle including design, electronics, assembly, production, and flight testing, and a high level of technical ownership over assigned systems and components." That's the role description. Work Environment: "This role is primarily on-site in a temperature-controlled office and warehouse environment. You will work in a hands-on, product-focused startup setting with direct access to aircraft, electronics labs, and test equipment. The environment supports close collaboration among firmware, electrical, manufacturing, and flight-test teams, providing visibility into the entire product lifecycle from design through production and flight testing." Job Type & Location: "This is a Contract to Hire position based out of Auburn Hills, MI." Workplace Type: "This is a fully onsite position in Auburn Hills,MI." Application Deadline: "This position is anticipated to close on Sep 30, 2026." About Actalent: paragraph about Actalent being global leader etc. That's substantive but maybe considered boilerplate? It's about the company; could be considered relevant. We'll keep it but remove EEO etc. We also have Pay And Benefits section with details. Now we need to format. We'll produce:

  About the role

  ... (combined role description + work environment + job type + location + workplace type + deadline + about actalent)

  But that may be long; still okay. Then

  Responsibilities

  with
  • each responsibility. Then

    Requirements

    with
    • essential skills. Then

      Qualifications

      with
      • additional skills & qualifications. Then

        Benefits

        with
        • benefits list. Then

          Pay

          with

          pay range. We must not include Schedule. Check that we didn't repeat job title as heading. Good. We must not include Job ID/requisition numbers. We must remove duplicated lines. Now let's extract each list. Responsibilities list from posting: - Develop, test, and maintain embedded firmware in C and C++ for STM32 and similar ARM Cortex-M microcontrollers. - Integrate with and extend a PX4-based flight-control stack to support small unmanned aircraft systems. - Design and implement device drivers and control loops using SPI, I2C, UART, and CAN communication interfaces. - Build robust embedded communication links using MAVLink and DroneCAN/UAVCAN protocols. - Support board bring-up and hardware verification in close collaboration with the electronics engineering team. - Implement secure boot, cryptographic signing, signed firmware updates, and field-update mechanisms to enhance system security and reliability. - Debug, profile, and harden firmware to ensure reliable operation under real-world field conditions. - Develop production flashing, testing, and provisioning tools to support manufacturing and deployment workflows. - Participate in aircraft flight testing and conduct post-flight log analysis to validate performance and identify improvements. - Collaborate closely with electrical, manufacturing, and flight-test personnel throughout the product-development lifecycle. - Troubleshoot issues across embedded software, electronics, communications, and system-level integration. - Contribute to board bring-up activities and system testing, working hands-on with custom PCB hardware. - Participate in PCB design reviews by reading and interpreting electrical schematics and providing firmware-focused feedback. That's 14 items. Essential Skills list: - 3+ years of professional embedded C/C++ development experience with firmware that has shipped in a product. - Strong proficiency in C and C++ for embedded systems and firmware development. - Experience developing on STM32 or similar ARM Cortex-M microcontrollers. - Bare-metal and RTOS development experience with NuttX, FreeRTOS, Zephyr, or similar real-time operating systems. - Experience implementing and troubleshooting SPI, I2C, UART, and CAN communications. - Hands-on hardware debugging experience using oscilloscopes, logic analyzers, and JTAG/SWD tools. - Strong understanding of microcontroller architecture, including interrupts, DMA, and timing. - Ability to troubleshoot issues across embedded software, electronics, communications, and system-level integration. - Understanding of the interaction between firmware and custom PCB hardware. - Ability to work collaboratively during board bring-up and system testing. - Strong ownership mentality and willingness to work across traditional engineering boundaries. - Comfort working in a hands-on, product-focused startup environment. That's 12 items. Additional Skills & Qualifications list: - Bachelor’s degree in Electrical Engineering, Computer Engineering, Software Engineering, or equivalent demonstrated experience. - Direct PX4 development experience or experience with ArduPilot. - Experience with STM32 HAL/LL and NuttX. - Experience with MAVLink and DroneCAN/UAVCAN communication protocols. - Experience implementing secure boot, cryptographic signing, signed firmware updates, or anti-tamper mechanisms. - Ability to read electrical schematics and participate effectively in PCB design reviews. - Experience with board bring-up and hardware verification. - Experience developing production flashing, testing, and provisioning tools. - Flight testing and post-flight log analysis experience. - Interest in working closely with engineers who design and build the physical product, from electronics through assembly and flight testing. That's 10 items. Benefits list from Pay And Benefits: - Medical, dental & vision - Critical Illness, Accident, and Hospital - 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available - Life Insurance (Voluntary Life & AD&D for the employee and dependents) - Short and long-term disability - Health Spending Account (HSA) - Transportation benefits - Employee Assistance Program - Time Off/Leave (PTO, Vacation or Sick Leave) That's 9 items. Pay range: "$60.00 - $70.00/hr." Now we need to combine About the role paragraph with other info. Let's craft About the role paragraph: "The Embedded Systems Engineer will design, develop, and maintain firmware that powers small unmanned aircraft systems and associated ground equipment for demanding mission applications. You will work across flight-controller integration, battery management, motor control, lighting systems, and communication