Software Integration Engineer, Self-Driving

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. The posting includes: - Intro about company (maybe not needed as heading? It's not a section heading; we can include as

before sections? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short paragraph about company as intro. - Then "About The Role" heading: we should use

About The Role

and then content. - Then bullet list of responsibilities: after "At Applied Intuition, You Will" there is a list of responsibilities (platform integration, end to end, etc). Those are bullet points. - Then "We're Looking For Someone Who Has" list of requirements/qualifications: bullet list. - Then "Nice To Have" list: could be considered "Preferred Qualifications" or "Skills". We could put under Skills or Qualifications. The instruction: Use sections like Skills, Benefits, Pay, Schedule. We have Pay: "Compensation Range: $180K - $220K". That's pay. So we need a Pay section with that. - Benefits: Not mentioned explicitly. There's mention of in-office expectation, flexibility, occasional remote work. That's more about schedule/work arrangement. Could be Schedule? The posting says: "We are an in-office company, and our expectation is that full-time employees primarily work from their Applied Intuition office 5 days a week. However, we also recognize the importance of flexibility and trust our employees to manage their schedules responsibly. This may include occasional remote work, starting the day with morning meetings from home before heading to the office, or leaving earlier when needed to accommodate family commitments. This in-office expectation does not apply to contractor positions". That's schedule/work arrangement. So we can put a Schedule section with that description. - Benefits: Not mentioned; we should not create a Benefits section unless posting actually states them. There's no explicit benefits like health insurance etc. So omit Benefits. - Skills: Could be derived from the "Nice To Have" list. Those are skills/experience. We could put a Skills section with those bullet points. Or we could incorporate them into Qualifications. But we have already a Requirements/Qualifications section for the "We're Looking For Someone Who Has". The Nice To Have could be separate "Preferred Qualifications" but we don't have that heading; we could put under Skills. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Skills section for nice-to-have. - Requirements: maybe we separate Requirements (hard requirements) and Qualifications (education). But we can combine. The instruction says we can have both Requirements and Qualifications sections if content exists. We have bullet list of requirements (5+ years experience, BS/MS, strong C/C++, etc). That's both requirements and qualifications. Could split: Requirements: experience, hands-on, etc. Qualifications: education degree. But we can also just have one section. However we need to follow instruction: "Prefer a few substantive sections over many thin ones." So maybe combine into one section called Requirements (or Qualifications). But we have both headings available; we could use Requirements for experience/skills, and Qualifications for education. That's two sections but still substantive. Let's decide: - About The Role: description paragraph. - Responsibilities: bullet list from "At Applied Intuition, You Will". - Requirements: bullet list from "We're Looking For Someone Who Has" (the hard requirements). Could include experience, degree, C/C++, automotive networks, Linux, ownership of platform integration, comfort working on vehicles, track record, willingness to participate. - Qualifications: maybe education (BS/MS in CS, CE, EE, Robotics, Mechatronics, or related). But that's already in the list. Could move degree to Qualifications. - Skills: bullet list from "Nice To Have". - Pay: paragraph with compensation range. - Schedule: paragraph about in-office expectation and flexibility. We must not include boilerplate like EEO, accommodation, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as they appear (maybe rephrase slightly but keep meaning). We must not add filler. Let's extract the bullet points. From "At Applied Intuition, You Will": - Platform integration, end to end - Lead the integration of autonomy software onto new vehicle platforms, from system architecture and interface definition through first engaged drive and handoff - System architecture - Design the on-vehicle compute topology, network segmentation, power and data paths, and the interfaces between autonomy compute, safety controllers, and vehicle ECUs - Actuation and sensing - Build and validate the drive-by-wire interface, whether from an OEM network specification or by integrating a third-party system, and bring up the sensor suite (lidar, radar, camera) including drivers, time sync, and calibration - Compute and real-time execution - Own the Linux software baseline and configuration management that make a vehicle reproducible, and port control software to real-time embedded targets where the platform requires it - Validation and scale - Build bench setups, on-vehicle test procedures, and automation that catch regressions early and let the team grow the fleet without growing the headcount to match - Technical leadership - Debug across the full software-to-actuator boundary, set direction on which interfaces and tools become standard, mentor engineers, and own the documentation and specs that other teams integrate against These are bullet points; each line seems to have a heading and description separated by " - ". We'll keep as

with the full text. From "We're Looking For Someone Who Has": - 5+ years of experience integrating software and hardware onto vehicles, robots, or other physical systems with real actuators and sensors - BS or MS in Computer Science, Computer Engineering, Electrical Engineering, Robotics, Mechatronics, or a related field - Strong C or C++, plus working Python, with experience writing and debugging code that runs on Linux and talks to hardware - Hands-on experience with automotive networks (CAN, CAN-FD, automotive Ethernet) and the tooling around them - Working knowledge of Linux systems and networking: building or maintaining machine images, configuring network interfaces, and automating setup with configuration management tools - Demonstrated ownership of at least one full platform integration from architecture and interface definition through on-vehicle validation and handoff - Comfort working on vehicles and test benches - Track record of driving integration problems to closure across team boundaries - A willingness to participate in on-vehicle and test-track testing From "Nice To Have": - System architecture and networking: compute and network topology design for vehicles, VLAN and switch configuration, PTP/gPTP and time-sync debugging, DDS or similar middleware - Drive-by-wire and control: building DBW interfaces from OEM network specs, integrating third-party DBW systems, motion control, vehicle dynamics - Sensors: lidar, radar, and camera bring-up, SerDes camera pipelines, calibration, GNSS/INS and IMU integration - Embedded and real-time: RTOS on automotive-grade MCUs, timing analysis, safety-oriented embedded C or C++ - Platform and automation: Yocto, Ubuntu image customization, Ansible or equivalent at fleet scale, CI for on-vehicle software - Domain: functional safety practice (ISO 26262 or similar) or working within a safety case; heavy or off-highway vehicles Now Pay: "Compensation Range: $180K - $220K" Schedule: The paragraph about in-office expectation. We also have introductory paragraph about company: "Applied Intuition, Inc. is powering the future of physical AI. Founded in 2017 and now valued at $15 billion, the Silicon Valley company is creating the digital infrastructure needed to bring intelligence to every moving machine on the planet. Applied Intuition services the automotive, defense, trucking, construction, mining and agriculture industries in three core areas: tools and infrastructure, operating systems, and autonomy. Eighteen of the top 20 global automakers, as well as the United States military and its allies, trust the company’s solutions to deliver physical intelligence. Applied Intuition is headquartered in Sunnyvale, California, with offices in Washington, D.C.; San Diego; Ft. Walton Beach, Florida; Ann Arbor, Michigan; London; Stuttgart; Munich; Stockholm; Bangalore; Seoul; and Tokyo. Learn more at applied.co. We are an in-office company, and our expectation is that full-time employees primarily work from their Applied Intuition office 5 days a week. However, we also recognize the importance of flexibility and trust our employees to manage their schedules responsibly. This may include occasional remote work, starting the day with morning meetings from home before heading to the office, or leaving earlier when needed to accommodate family commitments. This in-office expectation does not apply to contractor positions" But we already used the schedule paragraph; the intro includes some of that. To avoid duplication, we could keep the intro as a brief company overview before the About The Role heading, and then the schedule section separate (maybe just the flexibility part). However the instruction says: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short paragraph about company as intro. But we must not duplicate content. The schedule paragraph is essentially same as the later part about in-office expectation. We could keep the schedule section with that description, and not repeat it in intro. So intro should be company overview only (first part up to "Learn more at applied.co.") Then we have About The Role heading, responsibilities, requirements, qualifications, skills, pay, schedule. Let's craft:

Applied Intuition, Inc. is powering the future of physical AI. Founded in 2017 and now valued at $15 billion, the Silicon Valley company is creating the digital infrastructure needed to bring intelligence to every moving machine on the planet. Applied Intuition services the automotive, defense, trucking, construction, mining and agriculture industries in three core areas: tools and infrastructure, operating systems, and autonomy. Eighteen of the top 20 global automakers, as well as the United States military and its allies, trust the company’s solutions to deliver physical intelligence. Applied Intuition is headquartered in Sunnyvale, California, with offices in Washington, D.C.; San Diego; Ft. Walton Beach, Florida; Ann Arbor, Michigan; London; Stuttgart; Munich; Stockholm; Bangalore; Seoul; and Tokyo. Learn more at applied.co.

Then

About The Role

with a paragraph describing the team: "The Autonomy Integration team bridges Applied Intuition’s autonomy software with real vehicles, owning compute, networking, sensors, actuation, embedded execution, and platform automation across passenger and industrial vehicles. The team works across 0-to-1 bring-up and 1-to-many scalable deployment, with hands-on vehicle and test-track work and ~10% travel." Then Responsibilities

Responsibilities

with

list of the six bullet points. Then Requirements

Requirements

with
list of the hard requirements (excluding degree maybe). But we need to decide what goes where. Let's put all the "We're Looking For Someone Who Has" bullet points under Requirements. That includes the degree bullet as well. That's fine. Then Skills

Skills

with Nice To Have list. Then Pay

Pay

with

Compensation Range: $180K - $220K

Then Schedule

Schedule

with