Embedded Software Integration Engineer

We need to output HTML fragment with headings

for sections present: About the role? Not given. Responsibilities, Qualifications, maybe Skills? The posting includes "Summary Of Applicable Skills" which could be Skills. Also "Preferred Experience" could be part of Qualifications or separate. We need to include sections only when real content. We have location, duration, interview mode etc. Those are metadata; we can put in a short

maybe under a heading? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a

for location, duration, interview mode. We must not repeat job title as heading. We need sections: maybe "About the role" not present; we can skip. "Responsibilities" present. "Qualifications" present. "Skills" maybe from "Summary Of Applicable Skills". Also "Preferred Experience" could be part of Qualifications or separate "Preferred Qualifications". But we can include a section "Preferred Experience" if we want, but we need to avoid thin sections. Could combine into Qualifications. We also have "Pay" and "Schedule" not present, so omit. We need to preserve all substantive information. So we need to include location, duration, interview mode, the scenario about state machine diagram, etc. Let's parse the posting: Title: Embedded Software Integration Engineer Location: 4 days onsite Palo Alto, CA. Fridays remote Duration: 12+ Months Contract to hire Interview Mode 2 rounds They will have to do a state machine diagram on glider and then with KCS Candidates must design and draw a state machine diagram based on a provided scenario.Ability to visually construct a state machine is a key requirement. Job Description They are open to folks who have medical devices exp it does not have to be automotive, but auto is highly preferred Summary Of Applicable Skills 10+ years of embedded software and systems engineering experience with strong C/C++ and Python development across automotive, firmware, and safety-critical platforms.Extensive automotive background from General Motors, supporting QNX and Android vehicle platforms, leading hardware/software integration, root-cause analysis, and system-level performance validation.Hands-on experience with CAN, LIN, ECU/ECM architectures, vehicle networking, embedded diagnostics, UART, SPI, I2C, and functional safety standards including ISO 26262 and ASIL-D.Proven track record translating complex system requirements into scalable test, validation, and observability solutions, supporting OTA software releases and cross-functional engineering teams.Strong troubleshooting and integration expertise across hardware and software domains, with experience debugging complex embedded systems, analyzing field data, and driving technical decisions throughout the product lifecycle. Responsibilities Drive the evolution of body controls software architecture, crafting innovative solutions and defining hardware/software interfaces. Orchestrate early-stage hardware and software integration, meticulously validating system performance against stringent requirements. Translate high-level vehicle objectives into precise software specifications for body control systems. Leverage field data insights to continuously refine and optimize the performance of body control systems. Collaborate with validation teams to architect comprehensive test strategies for body control functionalities. Diagnose and resolve intricate hardware/software interactions throughout the product lifecycle. Assess the impact of design modifications on body control systems, synthesizing implications for hardware and software components. Champion functional safety by executing DFMEA and HARA analyses for body control systems. Provide expert guidance to cross-functional teams, steering technical decisions related to electrical, software, manufacturing, and mechanical aspects of body controls. Facilitate cross-functional understanding of system interdependencies, ensuring seamless integration across vehicle domains. Qualifications A technical degree in a relevant field (e.g., Mechatronics, Electrical Engineering, Computer Engineering, Systems Engineering). Proficiency in C/C++ and familiarity with scripting languages (e.g., Python). Exceptional problem-solving abilities in complex, networked embedded systems. Demonstrated ability to interpret data for system optimization. Familiarity with hardware and software development lifecycles. Proven experience leading collaborative engineering projects. Solid understanding of electrical engineering principles and mechatronic systems. Experience with CAN and/or LIN communication protocols and associated tools. Knowledge of DFMEA, HARA, and fault tree analysis methodologies. Preferred Experience with a broad range of body control systems, including doors, trunk, frunk, windows, seating, lighting, mirrors, wipers, heaters, steering wheel controls, and other actuators and sensors. Experience with vehicle software organizations and working with cross-functional teams. Experience with overall functionality and performance of body controls systems throughout a product's lifecycle. Experience with electric vehicle systems and architectures. A passion for automotive technology and a desire to shape the future of vehicle experiences. We need to output HTML fragment. We'll have a

for metadata: location, duration, interview mode, maybe also note about state machine diagram requirement. Then

Responsibilities

with

• each responsibility sentence. Then

  Qualifications

  with
  • each qualification. Then maybe

    Skills

    from Summary Of Applicable Skills. Could be a list. We must not repeat job title. We must not include boilerplate. Let's craft. Metadata paragraph: "Location: 4 days onsite Palo Alto, CA (Fridays remote). Duration: 12+ months contract‑to‑hire. Interview process: 2 rounds, including a state‑machine diagram exercise on a glider scenario with KCS." Also note about medical devices exp optional but automotive preferred. We could include that in metadata or as a separate note. Better to include in metadata paragraph. Now Responsibilities: list each sentence. Responsibilities sentences: - Drive the evolution of body controls software architecture, crafting innovative solutions and defining hardware/software interfaces. - Orchestrate early-stage hardware and software integration, meticulously validating system performance against stringent requirements. - Translate high-level vehicle objectives into precise software specifications for body control systems. - Leverage field data insights to continuously refine and optimize the performance of body control systems. - Collaborate with validation teams to architect comprehensive test strategies for body control functionalities. - Diagnose and resolve intricate hardware/software interactions throughout the product lifecycle. - Assess the impact of design modifications on body control systems, synthesizing implications for hardware and software components. - Champion functional safety by executing DFMEA and HARA analyses for body control systems. - Provide expert guidance to cross-functional teams, steering technical decisions related to electrical, software, manufacturing, and mechanical aspects of body controls. - Facilitate cross-functional understanding of system interdependencies, ensuring seamless integration across vehicle domains. Now Qualifications: list each. Qualifications sentences: - A technical degree in a relevant field (e.g., Mechatronics, Electrical Engineering, Computer Engineering, Systems Engineering). - Proficiency in C/C++ and familiarity with scripting languages (e.g., Python). - Exceptional problem-solving abilities in complex, networked embedded systems. - Demonstrated ability to interpret data for system optimization. - Familiarity with hardware and software development lifecycles. - Proven experience leading collaborative engineering projects. - Solid understanding of electrical engineering principles and mechatronic systems. - Experience with CAN and/or LIN communication protocols and associated tools. - Knowledge of DFMEA, HARA, and fault tree analysis methodologies. Preferred Experience sentences (could be part of Qualifications or separate). We'll include as part of Qualifications maybe as a sublist? But we can just add them as additional items. Preferred Experience: - Experience with a broad range of body control systems, including doors, trunk, frunk, windows, seating, lighting, mirrors, wipers, heaters, steering wheel controls, and other actuators and sensors. - Experience with vehicle software organizations and working with cross-functional teams. - Experience with overall functionality and performance of body controls systems throughout a product's lifecycle. - Experience with electric vehicle systems and architectures. - A passion for automotive technology and a desire to shape the future of vehicle experiences. Now Skills from Summary Of Applicable Skills: we can break into bullet points. Summary Of Applicable Skills sentences (it's a long paragraph). We need to extract bullet points. Let's parse: "10+ years of embedded software and systems engineering experience with strong C/C++ and Python development across automotive, firmware, and safety-critical platforms." "Extensive automotive background from General Motors, supporting QNX and Android vehicle platforms, leading hardware/software integration, root-cause analysis, and system-level performance validation." "Hands-on experience with CAN, LIN, ECU/ECM architectures, vehicle networking, embedded diagnostics, UART, SPI, I2C, and functional safety standards including ISO 26262 and ASIL-D." "Proven track record translating complex system requirements into scalable test, validation, and observability solutions, supporting OTA software releases and cross-functional engineering teams." "Strong troubleshooting and integration expertise across hardware and software domains, with experience debugging complex embedded systems, analyzing field data, and driving technical decisions throughout the product lifecycle." We can make each as a bullet. Now produce HTML. We'll wrap sections in maybe not required. Just output fragment. Let's craft:

    Location: 4 days onsite Palo Alto, CA (Fridays remote). Duration: 12+ months contract‑to‑hire. Interview process: 2 rounds, including a state‑machine diagram exercise on a glider scenario with KCS. The role is open to candidates with medical‑device experience; automotive background is highly preferred.

    Responsibilities

    • Drive the evolution of body controls software architecture, crafting innovative solutions and defining hardware/software interfaces.
    • Orchestrate early-stage hardware and software integration, meticulously validating system performance against stringent requirements.
    • Translate high-level vehicle objectives into precise software specifications for body control systems.
    • Leverage field data insights to continuously refine and optimize the performance of body control systems.
    • Collaborate with validation teams to architect comprehensive test strategies for body control functionalities.
    • Diagnose and resolve intricate hardware/software interactions throughout the product lifecycle.
    • Assess the impact of design modifications on body control systems, synthesizing implications for hardware and software components.
    • Champion functional safety by executing DFMEA and HARA analyses for body control systems.
    • Provide expert guidance to cross-functional teams, steering technical decisions related to electrical, software, manufacturing, and mechanical aspects of body controls.
    • Facilitate cross-functional understanding of system interdependencies, ensuring seamless integration across vehicle domains.

    Qualifications

    • A technical degree in a relevant field (e.g., Mechatronics, Electrical Engineering, Computer Engineering, Systems Engineering).
    • Proficiency in C/C++ and familiarity with scripting languages (e.g., Python).
    • Exceptional problem-solving abilities in complex, networked embedded systems.
    • Demonstrated ability to interpret data for system optimization.
    • Familiarity with hardware and software development lifecycles.
    • Proven experience leading collaborative engineering projects.
    • Solid understanding of electrical engineering principles and mechatronic systems.
    • Experience with CAN and/or LIN communication protocols and associated tools.
    • Knowledge of DFMEA, HARA, and fault tree analysis methodologies.
    • Experience with a broad range of body control systems, including doors, trunk, frunk, windows, seating, lighting, mirrors, wipers, heaters, steering wheel controls, and other actuators and sensors.
    • Experience with vehicle software organizations and working with cross-functional teams.
    • Experience with overall functionality and performance of body controls systems throughout a product's lifecycle.
    • Experience with electric vehicle systems and architectures.
    • A passion for automotive technology and a desire to shape the future of vehicle experiences.

    Skills

    • 10+ years of embedded software and systems engineering experience with strong C/C++ and Python development across automotive, firmware, and safety‑critical platforms.
    • Extensive automotive background from General Motors,