Senior Software Engineer (C++) - Sensor Pipelines
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when there is real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to extract substantive info: company description, team description, responsibilities (What You'll Do), requirements (What You'll Need To Succeed), Nice To Have, Benefits (What We Offer You), Pay (expected base salary range). Also maybe location? Not required as heading. Could embed location in About the role paragraph.
We need to preserve all substantive info, not invent or summarize away detail. So we must keep details like bullet points.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We must not include sections with filler like "commensurate with experience". Pay section: we have salary range. So include Pay heading with that info.
Schedule: not mentioned, so omit.
Benefits: we have many benefits listed; include Benefits heading with list.
Qualifications: maybe combine Requirements and Qualifications? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide which sections to include based on content. We have "What You'll Need To Succeed" which includes education, experience, skills. That's both Requirements and Qualifications. Could split into Requirements (education/experience) and Qualifications (skills). But we can also just have one Requirements section containing all. However we need to follow instruction: use those headings when appropriate. It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to use all. We should include sections that match content. We have About the role (company/team description). Responsibilities (What You'll Do). Requirements (education/experience). Qualifications (maybe technical skills). Skills (maybe specific skills like C++, network communication, RTOS). Benefits (What We Offer You). Pay (salary). We'll avoid duplication.
Let's parse content:
Company description paragraph: "Latitude AI (lat.ai) is building the future of Ford’s autonomy roadmap...". Also "Meet The Team The Embedded Software team is responsible...". That's about role/team.
Responsibilities (What You'll Do):
- Deliver safe and efficient embedded software for Radar and Lidar sensors
- Produce high-quality, maintainable code using C++
- Design, implement, and test high performance C++ code running in resource-constrained environments
- Design, implement, and test solutions in alignment with Functional Safety standards
- Work closely with suppliers and cross functional team of hardware/system engineers to ensure the success of our product
Requirements (What You'll Need To Succeed):
- Bachelor's degree in Computer Engineering, Computer Science, Electrical Engineering, Robotics or a related field and 4+ years of relevant experience (or Master's degree and 2+ years of relevant experience, or PhD)
- 4 years of strong experience developing embedded applications and systems using C++
- Proficient in network communication concepts including protocols, physical layer requirements, bandwidth characteristics, and configuration
- Strong software design, algorithm, problem-solving, and analytical skills
- Experience with multi-processor SoCs or similar embedded processors
- Familiarity with Embedded RTOS such as FreeRTOS/SafeRTOS and/or Embedded Linux desired
- Prefer candidates with experience developing software for highly complex, safety-critical sensing systems
Nice To Have:
- Strong knowledge and experience working on network-based sensors such as radar and lidar
- Track record of technical leadership in automotive or related fields taking products to production
Benefits (What We Offer You):
- Competitive compensation packages
- High-quality individual and family medical, dental, and vision insurance
- Health savings account with available employer match
- Employer-matched 401(k) retirement plan with immediate vesting
- Employer-paid group term life insurance and the option to elect voluntary life insurance
- Paid parental leave
- Paid medical leave
- Unlimited vacation
- 15 paid holidays
- Daily lunches, snacks, and beverages available in all office locations
- Pre-tax spending accounts for healthcare and dependent care expenses
- Pre-tax commuter benefits
- Monthly wellness stipend
- Adoption/Surrogacy support program
- Backup child and elder care program
- Professional development reimbursement
- Employee assistance program
- Discounted programs that include legal services, identity theft protection, pet insurance, and more
- Company and team bonding outlets: employee resource groups, quarterly team activity stipend, and wellness initiatives
Pay: "The expected base salary range for this full-time position in California is $179,200 - $268,800 USD. Actual starting pay will be based on job-related factors, including exact work location, experience, relevant training and education, and skill level. Latitude employees are also eligible to participate in Latitude’s annual bonus programs, equity compensation, and generous Company benefits program, subject to eligibility requirements."
We could include that under Pay heading.
We must not include boilerplate like "Candidates for positions with Latitude AI must be legally authorized to work in the United States on a permanent basis. Verification of employment eligibility will be required at the time of hire. Visa sponsorship is available for this position. We are an Equal Opportunity Employer..." That's EEO/legal boilerplate; remove.
Also remove "Learn more about Latitude’s team, mission and career opportunities at lat.ai!" maybe considered navigation? It's a call to action but not boilerplate; but it's like application instruction? It's not exactly application instruction but could be considered promotional. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Learn more about Latitude’s team, mission and career opportunities at lat.ai!" is not application instruction; it's more like a link. Might be okay to keep? It's not substantive job info; it's a link to learn more. Might be considered navigation. Safer to remove.
Also remove duplicated lines: none.
Now produce HTML.
Structure:
About the role
Latitude AI (lat.ai) is building the future of Ford’s autonomy roadmap to make travel safer, less stressful, and more enjoyable for everyone. Bringing this vision to scale, our fully in-house developed hands-free ADAS platform will debut on the all-new Ford Fathom in 2027. When you join the Latitude team, you’ll work alongside leading experts across machine learning and robotics, cloud platforms, mapping, sensors and compute systems, test operations, systems and safety engineering – all dedicated to redefining the relationship between people and their vehicles for millions of customers. As a Ford Motor Company subsidiary, we operate independently to develop automated driving technology at the speed of a technology startup. Latitude is headquartered in Pittsburgh with engineering centers in Dearborn, Mich., and Palo Alto, Calif. The Embedded Software team is responsible for developing the hardware drivers, hardware safety monitoring, and vehicle interfaces for the autonomy system. As a Senior Embedded Software Engineer in the Sensor firmware team, you will be responsible for developing the embedded software for radars/lidars and networking functions for these sensors. We’re looking for someone who has a passion and expertise in developing safe, efficient software for sensing systems.
Responsibilities
- Deliver safe and efficient embedded software for Radar and Lidar sensors
- Produce high-quality, maintainable code using C++
- Design, implement, and test high performance C++ code running in resource-constrained environments
- Design, implement, and test solutions in alignment with Functional Safety standards
- Work closely with suppliers and cross functional team of hardware/system engineers to ensure the success of our product
Requirements
- Bachelor's degree in Computer Engineering, Computer Science, Electrical Engineering, Robotics or a related field and 4+ years of relevant experience (or Master's degree and 2+ years of relevant experience, or PhD)
- 4 years of strong experience developing embedded applications and systems using C++
- Proficient in network communication concepts including protocols, physical layer requirements, bandwidth characteristics, and configuration
- Strong software design, algorithm, problem-solving, and analytical skills
- Experience with multi-processor SoCs or similar embedded processors
- Familiarity with Embedded RTOS such as FreeRTOS/SafeRTOS and/or Embedded Linux desired
- Prefer candidates with experience developing software for highly complex, safety-critical sensing systems
Nice to Have
- Strong knowledge and experience working on network-based sensors such as radar and lidar
- Track record of technical leadership in automotive or related fields taking products to production
But the instruction only listed certain headings; Nice to Have is not in list but could be considered Skills? Might be better to put under Skills heading. However we have "Skills" heading example. We could combine Nice to Have into Skills. But we have also technical skills in Requirements. Might be better to have Skills section for Nice to Have. Let's follow instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these. We have Requirements (education/experience). Qualifications maybe technical skills? Skills maybe specific abilities like C++, network communication, RTOS. But we already have those in Requirements. Could split: Requirements = education/experience; Qualifications = technical skills (C++, network, RTOS, SoC, safety-critical). Skills maybe Nice to Have (network sensors, leadership). However the instruction says "Prefer a few substantive sections over many thin ones." So maybe we should not over-split. Could combine Requirements and Qualifications into one Requirements section. And Skills maybe not needed. But we need to follow instruction: use those headings when appropriate. It's not mandatory to use all; we can omit if not needed. So we can have About the role, Responsibilities, Requirements, Benefits, Pay. That's sufficient. We'll omit Qualifications, Skills, Schedule.
Thus:
About the role
...
Responsibilities
...
Requirements
...
Benefits
...
Pay
The expected base salary range for this full-time position in California is $179,200 - $268,800 USD. Actual starting pay will be based on job-related factors, including exact work location, experience, relevant training and education, and skill level. Latitude employees are also eligible to participate in Latitude’s annual bonus programs, equity compensation, and generous Company benefits program, subject to eligibility requirements.
We should also include Nice to Have maybe under Requirements? Could add as a sublist? But we must preserve all substantive info. Nice to Have is substantive; we need to include it. Could add another section "Nice to Have" but not in allowed headings. However we could incorporate into Requirements or Skills. Since we are not using Skills heading, we could add a Skills
for Nice to Have. That seems appropriate: Skills heading can contain nice-to-have skills. Let's do that.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay.
Now ensure we don't repeat job title. No mention of "Senior Embedded Software Engineer" as heading; it's okay in
for prose. We must not include sections with filler like "commensurate with experience". Pay section: we have salary range. So include Pay heading with that info. Schedule: not mentioned, so omit. Benefits: we have many benefits listed; include Benefits heading with list. Qualifications: maybe combine Requirements and Qualifications? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide which sections to include based on content. We have "What You'll Need To Succeed" which includes education, experience, skills. That's both Requirements and Qualifications. Could split into Requirements (education/experience) and Qualifications (skills). But we can also just have one Requirements section containing all. However we need to follow instruction: use those headings when appropriate. It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to use all. We should include sections that match content. We have About the role (company/team description). Responsibilities (What You'll Do). Requirements (education/experience). Qualifications (maybe technical skills). Skills (maybe specific skills like C++, network communication, RTOS). Benefits (What We Offer You). Pay (salary). We'll avoid duplication.
Let's parse content:
Company description paragraph: "Latitude AI (lat.ai) is building the future of Ford’s autonomy roadmap...". Also "Meet The Team The Embedded Software team is responsible...". That's about role/team.
Responsibilities (What You'll Do):
- Deliver safe and efficient embedded software for Radar and Lidar sensors
- Produce high-quality, maintainable code using C++
- Design, implement, and test high performance C++ code running in resource-constrained environments
- Design, implement, and test solutions in alignment with Functional Safety standards
- Work closely with suppliers and cross functional team of hardware/system engineers to ensure the success of our product
Requirements (What You'll Need To Succeed):
- Bachelor's degree in Computer Engineering, Computer Science, Electrical Engineering, Robotics or a related field and 4+ years of relevant experience (or Master's degree and 2+ years of relevant experience, or PhD)
- 4 years of strong experience developing embedded applications and systems using C++
- Proficient in network communication concepts including protocols, physical layer requirements, bandwidth characteristics, and configuration
- Strong software design, algorithm, problem-solving, and analytical skills
- Experience with multi-processor SoCs or similar embedded processors
- Familiarity with Embedded RTOS such as FreeRTOS/SafeRTOS and/or Embedded Linux desired
- Prefer candidates with experience developing software for highly complex, safety-critical sensing systems
Nice To Have:
- Strong knowledge and experience working on network-based sensors such as radar and lidar
- Track record of technical leadership in automotive or related fields taking products to production
Benefits (What We Offer You):
- Competitive compensation packages
- High-quality individual and family medical, dental, and vision insurance
- Health savings account with available employer match
- Employer-matched 401(k) retirement plan with immediate vesting
- Employer-paid group term life insurance and the option to elect voluntary life insurance
- Paid parental leave
- Paid medical leave
- Unlimited vacation
- 15 paid holidays
- Daily lunches, snacks, and beverages available in all office locations
- Pre-tax spending accounts for healthcare and dependent care expenses
- Pre-tax commuter benefits
- Monthly wellness stipend
- Adoption/Surrogacy support program
- Backup child and elder care program
- Professional development reimbursement
- Employee assistance program
- Discounted programs that include legal services, identity theft protection, pet insurance, and more
- Company and team bonding outlets: employee resource groups, quarterly team activity stipend, and wellness initiatives
Pay: "The expected base salary range for this full-time position in California is $179,200 - $268,800 USD. Actual starting pay will be based on job-related factors, including exact work location, experience, relevant training and education, and skill level. Latitude employees are also eligible to participate in Latitude’s annual bonus programs, equity compensation, and generous Company benefits program, subject to eligibility requirements."
We could include that under Pay heading.
We must not include boilerplate like "Candidates for positions with Latitude AI must be legally authorized to work in the United States on a permanent basis. Verification of employment eligibility will be required at the time of hire. Visa sponsorship is available for this position. We are an Equal Opportunity Employer..." That's EEO/legal boilerplate; remove.
Also remove "Learn more about Latitude’s team, mission and career opportunities at lat.ai!" maybe considered navigation? It's a call to action but not boilerplate; but it's like application instruction? It's not exactly application instruction but could be considered promotional. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Learn more about Latitude’s team, mission and career opportunities at lat.ai!" is not application instruction; it's more like a link. Might be okay to keep? It's not substantive job info; it's a link to learn more. Might be considered navigation. Safer to remove.
Also remove duplicated lines: none.
Now produce HTML.
Structure:
About the role
Latitude AI (lat.ai) is building the future of Ford’s autonomy roadmap to make travel safer, less stressful, and more enjoyable for everyone. Bringing this vision to scale, our fully in-house developed hands-free ADAS platform will debut on the all-new Ford Fathom in 2027. When you join the Latitude team, you’ll work alongside leading experts across machine learning and robotics, cloud platforms, mapping, sensors and compute systems, test operations, systems and safety engineering – all dedicated to redefining the relationship between people and their vehicles for millions of customers. As a Ford Motor Company subsidiary, we operate independently to develop automated driving technology at the speed of a technology startup. Latitude is headquartered in Pittsburgh with engineering centers in Dearborn, Mich., and Palo Alto, Calif. The Embedded Software team is responsible for developing the hardware drivers, hardware safety monitoring, and vehicle interfaces for the autonomy system. As a Senior Embedded Software Engineer in the Sensor firmware team, you will be responsible for developing the embedded software for radars/lidars and networking functions for these sensors. We’re looking for someone who has a passion and expertise in developing safe, efficient software for sensing systems.
Responsibilities
- Deliver safe and efficient embedded software for Radar and Lidar sensors
- Produce high-quality, maintainable code using C++
- Design, implement, and test high performance C++ code running in resource-constrained environments
- Design, implement, and test solutions in alignment with Functional Safety standards
- Work closely with suppliers and cross functional team of hardware/system engineers to ensure the success of our product
Requirements
- Bachelor's degree in Computer Engineering, Computer Science, Electrical Engineering, Robotics or a related field and 4+ years of relevant experience (or Master's degree and 2+ years of relevant experience, or PhD)
- 4 years of strong experience developing embedded applications and systems using C++
- Proficient in network communication concepts including protocols, physical layer requirements, bandwidth characteristics, and configuration
- Strong software design, algorithm, problem-solving, and analytical skills
- Experience with multi-processor SoCs or similar embedded processors
- Familiarity with Embedded RTOS such as FreeRTOS/SafeRTOS and/or Embedded Linux desired
- Prefer candidates with experience developing software for highly complex, safety-critical sensing systems
Nice to Have
- Strong knowledge and experience working on network-based sensors such as radar and lidar
- Track record of technical leadership in automotive or related fields taking products to production
About the role
...
Responsibilities
- ...
Requirements
- ...
Benefits
- ...
Pay
The expected base salary range for this full-time position in California is $179,200 - $268,800 USD. Actual starting pay will be based on job-related factors, including exact work location, experience, relevant training and education, and skill level. Latitude employees are also eligible to participate in Latitude’s annual bonus programs, equity compensation, and generous Company benefits program, subject to eligibility requirements.
We should also include Nice to Have maybe under Requirements? Could add as a sublist? But we must preserve all substantive info. Nice to Have is substantive; we need to include it. Could add another section "Nice to Have" but not in allowed headings. However we could incorporate into Requirements or Skills. Since we are not using Skills heading, we could add a