Lead Firmware Engineer

We need to output HTML fragment with sections: About the role? The posting includes description. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We have: - About the role: description of role, hybrid, location, relocation assistance, opportunity to work with team, design firmware for electronic trip units, etc. So we can put that in About the role. - Responsibilities: bullet list under "What You’ll Do". So we can put that as Responsibilities. - Requirements: maybe "Qualifications Required (Basic)" includes required qualifications. Could be Requirements or Qualifications. The instruction says we can have sections Requirements, Qualifications, Skills. We need to decide mapping. Usually Requirements = basic qualifications. Qualifications = maybe preferred? But we have both Required and Preferred. Could treat Required as Requirements, Preferred as Qualifications, and Skills as separate? However we also have a Skills section later listing many skills. So we can map: - Requirements: Basic qualifications (Bachelor's degree, 3 years leading, 7 years hands-on, etc.) - Qualifications: Preferred qualifications (Master's degree, etc.) - Skills: The list under Skills (technical guidance, Agile, etc.) plus maybe also soft skills? The posting includes a "Skills" section then "Soft Skills". Could combine into Skills section. - Benefits: The posting mentions relocation assistance, health and welfare benefits, retirement benefits, programs for paid/unpaid time away, link to Eaton Benefits Overview. So we have some benefits content. So we can include Benefits section. - Pay: The posting includes expected annual salary range $97000 - $143000 a year. So we include Pay section. - Schedule: Not mentioned (hybrid role but no schedule details). So we omit Schedule. We must not include boilerplate like EEO, legal, accommodation, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove application instructions like "Please note the salary information shown above is a general guideline only." That's part of Pay but we can keep? It's not boilerplate; it's about salary. Might keep but it's somewhat generic. However we should preserve all substantive information; that line is about salary being guideline; it's substantive? It's not invented. We can keep. We must not repeat job title as heading. So no heading for Lead Firmware Engineer. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment, no /, no markdown fences. We need to use

for each section heading, then content:

for prose,

• for lists. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract content. About the role: "Eaton’s ES AMER PCS division is currently seeking a Lead Firmware Engineer. This is a hybrid role that will take place out of our office in Moon Township, PA (Pittsburgh). We are able to offer relocation assistance for qualified candidates within the United States. The Lead Firmware Engineer is an innovative problem-solver that will design firmware for electronic trip units used in circuit breakers for the Power Components Division. You will have the opportunity to work with a dynamic global team to design and improve trip units and their capabilities. You will work with a team of dedicated engineers and experience the excitement of bringing new products to life from design concept through to production launch. You will be responsible for the design and development of embedded software for Eaton’s family of circuit breakers. This includes creating functionality related to hardware drivers, protection, metering, communication, power electronics, and user interface." We can put that as prose in

  . Responsibilities: list under "What You’ll Do". Items: - Lead the design, development, integration, and testing of embedded firmware for microcontroller-based products. - Contribute to firmware architecture and design decisions while providing technical leadership within project teams. - Plan and coordinate firmware development tasks, creating robust and trackable execution plans aligned with project objectives. - Review own work and participate in formal design, code, and quality reviews while providing constructive feedback to peers. - Mentor and support other engineers in firmware design, development, debugging, and testing activities. - Develop reliable, maintainable, and reusable firmware components using C/C++, RTOS, and embedded communication protocols. - Perform technical investigations and root cause analysis to resolve product, customer, manufacturing, and field issues. - Collaborate with hardware, systems, quality, cybersecurity, manufacturing, and test engineering teams throughout product development. - Support firmware verification, validation, and system-level testing activities to meet quality and reliability objectives. - Develop and maintain automated test tools, verification suites, and stress-testing capabilities. We'll put each as

• . Requirements (Basic Qualifications): - Bachelor’s degree in Electrical Engineering, Computer Engineering, or related engineering discipline from an accredited institution. - Minimum of 3 years of experience leading firmware development activities and contributing to firmware architecture and design decisions for embedded products. - Minimum 7 years of hands-on experience in embedded firmware/software development, including multi-controller systems utilizing C/C++. These experiences must include: - Demonstrated proficiency in architecting and implementing embedded firmware solutions across RTOS-based and bare-metal environments. - Strong capabilities with embedded peripherals and interfaces including ADC, PWM, UART, SPI, I2C, DMA, GPIO, and interrupt-driven systems. - Proven experience debugging and resolving complex hardware-software integration and system-level issues. Also note: "Eaton will not consider applicants for employment, immigration sponsorship or support for this position. This means that Eaton will not support any CPT, OPT, or STEM OPT plans, F-1 to H-1B, H-1B cap registration, O-1, E-3, TN status, I-485 job portability, etc." This is a restriction; it's substantive. Should we include? It's about immigration sponsorship. It's not boilerplate; it's a specific condition. We could include under Requirements or maybe a separate note. But we have no section for immigration; we could include as a paragraph under Requirements. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly EEO; it's about immigration sponsorship. It's a specific condition. I'd keep it as part of Requirements (maybe as a note). But we need to decide if it's considered boilerplate. It's a specific restriction; likely they want to keep it. I'll include as a

  under Requirements. Qualifications (Preferred): - Master's degree in Electrical Engineering, Computer Engineering, or related engineering discipline from an accredited institution. Skills: The list under Skills (many bullet points) plus Soft Skills. Let's extract Skills bullet points: - Experience providing technical guidance and mentoring engineers within project teams. - Experience with Agile development methodologies, CI/CD pipelines, automated testing frameworks, and DevOps practices. - Strong understanding of software architecture, design patterns, and maintainable embedded software frameworks. - Experience with source control systems and collaborative development workflows. - Hands-on experience with unit testing, white-box testing, black-box testing, integration testing, and automated regression testing. - Working knowledge of embedded cybersecurity principles, secure development practices, and functional safety requirements. - Experience investigating and resolving complex system-level issues while collaborating with multidisciplinary engineering teams. - Familiarity with multitasking firmware concepts, preferably using Zephyr RTOS or similar real-time operating systems. - Experience with safety-critical product development and compliance standards such as UL and IEC. - Experience developing automation and test tools using Python, Bash, or similar scripting languages. - Proven experience debugging embedded systems using JTAG, SWD, In-Circuit Emulators (ICE), oscilloscopes, logic analyzers, and protocol analyzers. - Experience developing firmware for power distribution, circuit protection, or industrial control products. - Familiarity with current sensing technologies including Rogowski coils, current transformers (CTs), shunt-based current sensing, and associated signal conditioning techniques. - Experience implementing protection algorithms and real-time monitoring functions such as overcurrent, short-circuit, ground fault, and thermal protection. Soft Skills bullet points: - Excellent interpersonal, collaboration, and verbal/written communication skills. - Ability to provide technical guidance, mentor peers, and support team development. - Strong problem-solving skills and a data-driven approach to engineering decisions. - Ability to read and interpret electrical schematics and hardware designs. - Proficiency with digital oscilloscopes, logic analyzers, protocol analyzers, and embedded debugging tools. - Strong understanding of embedded software architecture, modular design, and software quality principles. - Proficiency in technical documentation, requirements management, and documentation tools such as Atlassian Confluence and Jira. - Ability to collaborate effectively across multidisciplinary teams and contribute to technical decision-making. We could combine Skills and Soft Skills into one Skills section, but we have a separate Skills heading allowed. We could put all under Skills. Benefits: - Relocation assistance for qualified candidates within the United States. - Eaton provides various Health and Welfare benefits as well as Retirement benefits, and several programs that provide for paid and unpaid time away from work. - Click here for more detail: Eaton Benefits Overview. (We can keep as a link? But we cannot output markdown; we can output but we don't have URL. The text says "Click here for more detail: Eaton Benefits Overview." We could keep as plain text. Pay: - Expected annual salary range for this role is $97000 - $143000 a year. - Please note the salary information shown above is a general guideline only. Salaries are based upon candidate skills, experience, and qualifications, as well as market and business considerations. Schedule: none. We must not include boilerplate like "All positions may require participation in video and in-person interviews as part of the hiring process." That's generic; maybe we should remove as it's not specific to role? It's generic hiring process. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The interview process line could be considered application instructions? It's about hiring process; maybe remove. Also lines about privacy rights, equal employment opportunities, second chance employment, accommodation request phone number, etc. Remove those. Also remove "We know that good benefit programs are important to employees and their families." That's generic but still about benefits; we already have benefits specifics. Might keep? It's somewhat generic but still about benefits. Could keep as part of benefits. We need to ensure we don't create sections with filler like "commensurate with experience". We have specific salary range, so Pay section is valid. Now construct HTML. We'll start with

  About the role

  then

  ...

  Then

  Responsibilities

  • ...
  ...
  Then

  Requirements

  for the basic qualifications, plus maybe a paragraph for immigration restriction. We could do:

  Requirements

  • Bachelor’s degree ...
  • Minimum of 3 years ...
  • Minimum 7 years of hands-on experience ...
  then a nested list for the sub-items? The spec says use
  • for any list of duties/requirements/benefits. For the sub-items under the 7 years experience, we could also use
    • . So we can embed. Then after the list, a

      for the immigration restriction: "Eaton will not consider applicants for employment, immigration sponsorship or support for this position. This means that Eaton will not support any CPT, OPT, or STEM OPT plans, F-1 to H-1B, H-1B cap registration, O-1, E-3, TN status, I-485 job portability, etc." Then

      Qualifications

      • Master's degree ...
      Then <