Senior Embedded Software Engineer

We need to output only HTML fragment, using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We need to parse the job posting. Let's extract sections: - Job Summary: "Responsible for requirements generation, simulation, design, development and integration of complex military combat vehicle software-based systems. We are looking for a Sr. Embedded Software Engineer to work for our Auburn Hills MI office. If you have at least 15 years of experience in Software Engineering and have a bachelor’s degree in engineering or a related field, we invite you to click the Apply button to learn more and share your qualifications with us." We can treat that as "About the role" maybe. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we must only include sections when posting has real specific content. So we need to decide which sections have content. Let's map: - About the role: The job summary content fits. - Responsibilities: The "Essential Function" list includes many responsibilities: "Develop vehicle software", etc. So we can create Responsibilities section with list items. - Requirements: Could be "Minimum Qualifications" and "Education", "Experience". Might be considered Requirements. But we also have "Qualifications" separate. The instruction says we can have both Requirements and Qualifications sections. We need to decide what to put where. Typically Requirements are mandatory; Qualifications could be preferred. The posting includes "Minimum Qualifications" (knowledge, skills, abilities) and "Education", "Experience". Also "Preferred Qualifications". So we could have: - Requirements: Minimum Qualifications (knowledge, skills, abilities) + Education + Experience (maybe as list). Or we could split: Requirements = Minimum Qualifications; Qualifications = Preferred Qualifications. But we also have Education and Experience sections maybe separate? The instruction only lists those headings; we can also add other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings if appropriate. It doesn't forbid other headings, but suggests using those. Probably best to stick to those. Thus we need to map content to these headings. We have: - About the role: job summary. - Responsibilities: essential function list. - Requirements: maybe the "Minimum Qualifications" (knowledge, skills, abilities) plus maybe "Education" and "Experience"? But Education and Experience could be separate sections but not in list; we could include them under Requirements as subpoints? However the instruction says use

• for any list of duties/requirements/benefits. So we can have lists under Requirements. - Qualifications: maybe "Preferred Qualifications". - Skills: maybe we can extract skills from the Minimum Qualifications and Preferred Qualifications (like familiarity with tools, protocols). Could create a Skills section. - Benefits: Not mentioned. No benefits info. So we should NOT include Benefits section. - Pay: Not mentioned. So no Pay section. - Schedule: Not mentioned. So no Schedule section. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills. We must ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them as lists. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is an Equal Employment Opportunity Statement; we must remove that. Also "Background Prerequisites" maybe not boilerplate? It's about background check, etc. That's substantive? It's about prerequisites; we could include under Requirements maybe. But it's not a list of duties; it's a condition. We could include as a paragraph under Requirements. Also "WORKING CONDITIONS AND PHYSICAL DEMANDS" is substantive; we could include under Requirements or maybe a separate section? Not in allowed headings. Could include under Requirements as a paragraph. We must not repeat job title as heading. So no heading for Sr. Embedded Software Engineer. We must not put Job ID/requisition numbers as headings; none present. We need to output only HTML fragment, no /, no markdown fences. Let's extract content precisely. Job Summary paragraph: "Responsible for requirements generation, simulation, design, development and integration of complex military combat vehicle software-based systems. We are looking for a Sr. Embedded Software Engineer to work for our Auburn Hills MI office. If you have at least 15 years of experience in Software Engineering and have a bachelor’s degree in engineering or a related field, we invite you to click the Apply button to learn more and share your qualifications with us." We will keep that as About the role. Location: "Location: Auburn Hills, MI" - could be included in About the role as a sentence? It's location info. Could add after summary: "Location: Auburn Hills, MI". Since it's substantive, we should preserve. We'll add as a sentence. Essential Function list: many items. Let's list them as bullet points. Essential Function items (as per text): - Develop vehicle software - Develop vehicle software and cybersecurity employing rapid prototyping, agile development, DevSecOps - Develop software requirement specifications, algorithms, logic flow-charts / activity diagrams, leverage SysML Modeling and Simulation input - Research, simulate and analyze software solutions to evaluate system performance to meet customer requirements - Perform trade studies to compare alternative approaches - Familiarity with software life-cycle development, verification, configuration and integration tools (Git, Jira, Confluence, Kubernetes, CANoe, MATLAB/Simulink, …) - Familiarity with development and integration of drivers, apps, kernels, containers and VMs - Familiarity with safety criticality - Integration of military lethality, survivability, and C5ISR systems - Support of CPU, GPU, and FPGA integration using design tools - Interact with external customers and suppliers - Component/Vehicle test support - Understand and review test plans for compliance with customer’s requirements and functions - Employ test / scan software tools - Support prototype development and test - Support system-integration-lab (SIL) and hardware-in-the-loop (HIL) activities - Monitor/analyze test results - Troubleshoot issues and perform corrective action Note there is duplication: first two items both about develop vehicle software; but we keep as given. Minimum Qualifications (Knowledge, Skills and Abilities) list: - Currently holds or has the ability to obtain SECRET US Defense clearance - Applied working knowledge in the domain of software engineering development and systems integration, with a proven track record of product development throughout the entire product lifecycle - Knowledge of Systems based design and related Standards/Processes - Ability to present technical solutions to clients and internal stakeholders - Detailed knowledge of mechanical and electrical engineering and vehicle principles - Must be able to communicate effectively in a variety of settings, possess the ability to explain complex concepts in a way that makes sense and be able to assimilate complex instructions easily with all levels of management and staff to establish productive relationships - Must demonstrate an enthusiasm to engage with and support overseas colleagues to ensure all staff have the information and opportunity to perform to the best of their abilities - Must promote collaboration and facilitate teamwork across the organization and its external service providers. - Must be tactful, diplomatic, and work with integrity, honesty, and respect for others. - Must display exceptional listening and analytical skills in order to understand customer concerns and needs with the ability to respond promptly and effectively to those needs - High level of self-motivation and standards with the ability to multi-task; balancing "analysis" with "doing". Must be adaptable and able to prioritize and work under pressure to meet deadlines. - Willing and able to travel internationally for technology transfer Education: - BSc Engineering (e.g. Electrical, Computer Science, Software, Systems, Aerospace, Automotive) - MSc Engineering desired (e.g. Electrical, Computer Science, Software, Systems, Aerospace, Automotive, Management) Experience: - 15+ years’ experience software engineering - Experience with Real-Time OS (RTOS), Linux, Embedded C/C++ - Experience with UML/SysML Model-based SW Dev - Experience with Confluence, Cameo, MS Office - Experience with standard bus protocols (J1939 CAN Bus, RS422/485, 802.3 Ethernet) - Experience with TCP/IP/UDP, DDS, Multicast, DisplayPort, HDMI, HD-SDI protocols - Experience with x86, ARM, GPU, FPGA - Working knowledge with digital, analog, power and RF electronics - Understanding of vehicle power distribution systems and automotive power management. Knowledge of the fundamental functions and characteristics of Power Distribution Modules (PDMs), as well as how they integrate into automotive systems - Hands-on experience with lab equipment such as oscilloscopes, multi-meters, logic analyzers, function generators, network analyzers, and spectrum analyzers - Practical ‘hands on’ attitude with the ability to operate independently - Experience with engineering management in a highly regulated industry - Experience of working in a multi-national, multi-organizational and corporate environment - Experience with proposal activities, bid capture, contract negotiations and delivery planning Background Prerequisites: - Must undergo and meet company standards for background check, employment verification, reference checks and controlled substance testing - All employment at ARV is contingent upon the ability to obtain and maintain a government security clearance if the position requires it Preferred Qualifications: - Experience in delivering large complex US Defense programs - Familiarity with the US DoD ground vehicle requirements - Knowledge of the US DoD process and procedures for vehicle development and acquisition - Familiarity with the US Army TACOM / TARDEC / GVSC organizations - Experience with military Command, Control, Communications, Computers, Cyber, Intelligence - Experience with fire control systems, stabilization, coordinating transformation and algorithms - Experience with VICTORY, FACE, GCIA & MOSA standards - Detailed knowledge of Military Standards and regulations Working Conditions and Physical Demands: - With or without reasonable accommodations, requires the physical and mental capacity to perform effectively all essential functions. In addition to other demands, the demands of the job include: - Ability to lift up to 25 pounds occasionally - Ability to stand for long periods Supervisory Responsibility: None (maybe not needed). EEO statement to remove. Now we need to map to sections. About the role: job summary + location. Responsibilities: essential function list. Requirements: maybe Minimum Qualifications + Education + Experience + Background Prerequisites + Working Conditions? But that's a lot. Could split: Requirements = Minimum Qualifications; Qualifications = Preferred Qualifications; Skills = maybe a combined list of technical skills from Experience and Minimum Qualifications? But we need to avoid duplication. Better: Use Requirements for mandatory qualifications (Minimum Qualifications, Education, Experience, Background Prerequisites, Working Conditions). Use Qualifications for Preferred Qualifications. Use Skills for technical skills list (like familiarity with tools, protocols, etc.) but that may duplicate with Experience. However we can still list them under Skills as a subset. But we must preserve all substantive information; we can include them in multiple sections? That would be duplication, which we should avoid. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid repeating same info. We can organize logically. Let's think: The posting already has sections: Minimum Qualifications (knowledge, skills, abilities), Education,