Sr Staff Software Engineer
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate: EEO, legal, application instructions, etc. Also remove cookie/navigation etc. We need to preserve all substantive information.
We need to parse content:
Company Description: paragraph about AUMOVIO.
Job Description: description of role: Sr. SW Resident Engineer. Contains responsibilities list.
Qualifications: required qualifications bullet list.
Preferred Qualifications: bullet list.
Additional Information: benefits list: "THE PERKS Immediate Benefits Robust Total Rewards Package Paid Time Off Employee Discounts Competitive Bonus Programs Employees 401k Match Diverse & Inclusive Work Environment with 20+ Employee Resource groups. Employee Assistance Program Future Growth Opportunities, including personal and professional And many more benefits that come with working for a global industry leader!"
Also there is "All your information will be kept confidential according to EEO guidelines." That's boilerplate, remove.
EEO statement etc remove.
"Ready to take your career to the next level? The future of mobility isn’t just anyone’s job. Make it yours! Join AUMOVIO. Own What’s Next." This is marketing fluff but maybe considered boilerplate? It's not EEO but could be considered promotional. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories, but it's more like a call to action. Might be considered application instruction? It's not exactly instruction to apply. Might keep? Safer to remove as it's generic fluff. But we need to preserve substantive information. This is not substantive. I'd remove.
Thus sections:
- About the role? Could use Company Description as "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content.
We have company description: could go under "About the role"? Actually "About the role" is more about the job, but we have job description separate. Could treat company description as "About the role"? Might be okay. Or we could omit About the role if not present. But we have company description; maybe we treat as "About the role". However the instruction 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 can choose which sections to include based on content.
We have:
- Responsibilities: from Job Description bullet points.
- Requirements: from Qualifications (required). Could be Requirements.
- Qualifications: maybe Preferred Qualifications as "Preferred Qualifications" but we only have headings list includes Qualifications (maybe for required) and Skills (maybe for preferred?). But we can include both Required and Preferred under Qualifications? The instruction says we can include a section only when posting has real specific content. We could have:
About the role
(company description)
Responsibilities
(list)
Requirements
(required qualifications)
Preferred Qualifications
(preferred) - but not in list; but we could use "Skills" heading for preferred qualifications? The list includes Skills as a possible heading. Could treat preferred qualifications as Skills. But better to add a heading "Preferred Qualifications" even if not in example? The instruction says use those headings as examples, not strict. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings; we shouldn't invent others. So we must stick to those headings only. So we need to map content to those headings.
Thus we need to decide which headings to use:
- About the role: could contain company description + maybe high-level role summary.
- Responsibilities: list of duties.
- Requirements: required qualifications.
- Qualifications: maybe preferred qualifications? Or we could put both required and preferred under Qualifications? But we already used Requirements for required. Qualifications could be for preferred qualifications.
- Skills: maybe technical skills? Not explicitly given; but we could put some skill items from preferred qualifications under Skills.
- Benefits: from Additional Information.
- Pay: not present, so omit.
- Schedule: not present (travel up to 10% domestic travel mentioned under qualifications? Actually travel is under Qualifications: "Up to 10% of domestic travel required". That's schedule-ish but not schedule. Could be considered Schedule? It's travel requirement. Might fit under Schedule? But schedule usually refers to work schedule (full-time, shift). Travel is not schedule. Probably omit Schedule.
Thus we will include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits.
We need to ensure we don't create sections with filler text.
Now extract content:
Company Description paragraph:
"Since its spin-off in September 2025, AUMOVIO continues the business of the former Continental group sector Automotive as an independent company. The technology and electronics company offers a wide-ranging portfolio that makes mobility safe, exciting, connected, and autonomous. This includes sensor solutions, displays, braking and comfort systems as well as comprehensive expertise in software, architecture platforms, and assistance systems for software-defined vehicles. In the fiscal year 2024 the business areas, which now belong to AUMOVIO, generated sales of 19.6 billion Euro. The company is headquartered in Frankfurt, Germany and has about 87.000 employees in more than 100 locations worldwide"
We'll put that in
.
Job Description responsibilities: list of duties:
- Act as the primary technical liaison and escalation point for customer issues, ensuring timely and effective resolution and provide On-site customer coordination of all regional technical topics.
- Analyze complex technical problems, diagnose root causes, and develop comprehensive solutions in collaboration with engineering teams
- Communicate technical concepts and solutions clearly to customers with varying levels of technical expertise
- Manage customer relationships proactively, maintaining regular contact and ensuring satisfaction
- Collaborate with manufacturing, quality, and design teams to resolve technical challenges and optimize operations
- Conduct technical training sessions and knowledge transfer activities with customers to enhance their product utilization
- Collaborate with cross-functional engineering teams to identify product improvements and implement cost reduction measures
- Support root cause analysis related to production issues, 0KM failures, and field returns, as applicable.
- Documentation of open issues related to customer development, customer meeting minutes, and support driving open issues to closure.
- Primary interface between Continental and Customer change control databases
- Coordination of prototypes including scheduling, preparation, shipping, tracking, and invoicing
We need to preserve all. We'll put each as
- under
.
Requirements (required qualifications):
List:
- Bachelor’s degree in engineering or related technical discipline required.
- 5 or more years of relevant professional automotive software experience in customer-facing technical support, engineering, customer liaison, or a related technical role
- Ability to troubleshoot complex technical issues, analyze root causes, and support practical resolution plans.
- Ability to translate complex technical information for customers and internal stakeholders with varying technical backgrounds.
- Clear written and verbal communication skills, including the ability to explain technical concepts to technical and non-technical audiences.
- Experience managing customer relationships and supporting escalated technical or customer issues professionally.
- Experience coordinating multiple technical initiatives, priorities, or workstreams across cross-functional teams.
- Ability to collaborate effectively across engineering, manufacturing, quality, design, and customer-facing teams.
- Up to 10% of domestic travel required
- Legal authorization to work in the U.S. is required. We will not sponsor individuals for employment visas now or in the future for this job posting.
- Relocation assistance is not offered for this position.
We'll put each as - .
Qualifications (preferred qualifications) list:
- 7 or more years of relevant professional automotive software experience in customer-facing technical support, engineering, customer liaison, or a related technical role
- Background in the automotive, manufacturing, or industrial engineering sectors
- Developing and automating scripts to improve efficiency and reducing time to complete tasks.
- Knowledge of quality assurance, compliance standards and regulatory requirements
- Familiarity with industry-standard diagnostic and testing tools and ethernet communications.
- Experience with process improvement methodologies and continuous quality initiatives
- Experience supporting GM or similar automotive OEM/customer accounts
- Demonstrated ability to proactively identify inefficiencies in existing workflows and develop scripted automation solutions
We'll put as
- .
Skills: maybe we could extract some skill items from preferred qualifications that are skills: e.g., "Developing and automating scripts", "Knowledge of quality assurance...", "Familiarity with industry-standard diagnostic and testing tools and ethernet communications", "Experience with process improvement methodologies", "Experience supporting GM...", "Demonstrated ability to proactively identify inefficiencies...". But we already used those under Qualifications. Perhaps we could treat Qualifications as required and Skills as preferred. But we already used Requirements for required. So we could swap: Requirements = required qualifications, Skills = preferred qualifications. Then we need a Qualifications section maybe for something else? But we have no other content. Could omit Qualifications heading if no content. But we have preferred qualifications; we could put them under Skills. Then we need a Qualifications section? Not needed if we don't have content. The instruction: include a section ONLY when the posting has real, specific content for it. So we can omit Qualifications if we don't have content for it. We have required qualifications (we put under Requirements). Preferred qualifications we can put under Skills. That seems reasonable.
Thus sections:
- About the role (company description)
- Responsibilities (duties)
- Requirements (required qualifications)
- Skills (preferred qualifications / skills)
- Benefits (perks)
We'll not include Qualifications or Pay or Schedule.
Now Benefits: list from Additional Information:
- Robust Total Rewards Package
- Paid Time Off
- Employee Discounts
- Competitive Bonus Programs
- Employees 401k Match
- Diverse & Inclusive Work Environment with 20+ Employee Resource groups.
- Employee Assistance Program
- Future Growth Opportunities, including personal and professional
- And many more benefits that come with working for a global industry leader!
We need to preserve all. The last line is vague but still a benefit statement; we keep.
We'll put each as
- .
Now ensure we don't include boilerplate like "All your information will be kept confidential according to EEO guidelines." etc. Remove.
Now produce HTML fragment:
About the role
Since its spin-off in September 2025, AUMOVIO continues the business of the former Continental group sector Automotive as an independent company. The technology and electronics company offers a wide-ranging portfolio that makes mobility safe, exciting, connected, and autonomous. This includes sensor solutions, displays, braking and comfort systems as well as comprehensive expertise in software, architecture platforms, and assistance systems for software-defined vehicles. In the fiscal year 2024 the business areas, which now belong to AUMOVIO, generated sales of 19.6 billion Euro. The company is headquartered in Frankfurt, Germany and has about 87.000 employees in more than 100 locations worldwide
Responsibilities
- Act as the primary technical liaison and escalation point for customer issues, ensuring timely and effective resolution and provide On-site customer coordination of all regional technical topics.
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate: EEO, legal, application instructions, etc. Also remove cookie/navigation etc. We need to preserve all substantive information. We need to parse content: Company Description: paragraph about AUMOVIO. Job Description: description of role: Sr. SW Resident Engineer. Contains responsibilities list. Qualifications: required qualifications bullet list. Preferred Qualifications: bullet list. Additional Information: benefits list: "THE PERKS Immediate Benefits Robust Total Rewards Package Paid Time Off Employee Discounts Competitive Bonus Programs Employees 401k Match Diverse & Inclusive Work Environment with 20+ Employee Resource groups. Employee Assistance Program Future Growth Opportunities, including personal and professional And many more benefits that come with working for a global industry leader!" Also there is "All your information will be kept confidential according to EEO guidelines." That's boilerplate, remove. EEO statement etc remove. "Ready to take your career to the next level? The future of mobility isn’t just anyone’s job. Make it yours! Join AUMOVIO. Own What’s Next." This is marketing fluff but maybe considered boilerplate? It's not EEO but could be considered promotional. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories, but it's more like a call to action. Might be considered application instruction? It's not exactly instruction to apply. Might keep? Safer to remove as it's generic fluff. But we need to preserve substantive information. This is not substantive. I'd remove. Thus sections: - About the role? Could use Company Description as "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. We have company description: could go under "About the role"? Actually "About the role" is more about the job, but we have job description separate. Could treat company description as "About the role"? Might be okay. Or we could omit About the role if not present. But we have company description; maybe we treat as "About the role". However the instruction 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 can choose which sections to include based on content.
We have:
- Responsibilities: from Job Description bullet points.
- Requirements: from Qualifications (required). Could be Requirements.
- Qualifications: maybe Preferred Qualifications as "Preferred Qualifications" but we only have headings list includes Qualifications (maybe for required) and Skills (maybe for preferred?). But we can include both Required and Preferred under Qualifications? The instruction says we can include a section only when posting has real specific content. We could have:
About the role
(company description)
Responsibilities
(list)
Requirements
(required qualifications)
Preferred Qualifications
(preferred) - but not in list; but we could use "Skills" heading for preferred qualifications? The list includes Skills as a possible heading. Could treat preferred qualifications as Skills. But better to add a heading "Preferred Qualifications" even if not in example? The instruction says use those headings as examples, not strict. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings; we shouldn't invent others. So we must stick to those headings only. So we need to map content to those headings.
Thus we need to decide which headings to use:
- About the role: could contain company description + maybe high-level role summary.
- Responsibilities: list of duties.
- Requirements: required qualifications.
- Qualifications: maybe preferred qualifications? Or we could put both required and preferred under Qualifications? But we already used Requirements for required. Qualifications could be for preferred qualifications.
- Skills: maybe technical skills? Not explicitly given; but we could put some skill items from preferred qualifications under Skills.
- Benefits: from Additional Information.
- Pay: not present, so omit.
- Schedule: not present (travel up to 10% domestic travel mentioned under qualifications? Actually travel is under Qualifications: "Up to 10% of domestic travel required". That's schedule-ish but not schedule. Could be considered Schedule? It's travel requirement. Might fit under Schedule? But schedule usually refers to work schedule (full-time, shift). Travel is not schedule. Probably omit Schedule.
Thus we will include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits.
We need to ensure we don't create sections with filler text.
Now extract content:
Company Description paragraph:
"Since its spin-off in September 2025, AUMOVIO continues the business of the former Continental group sector Automotive as an independent company. The technology and electronics company offers a wide-ranging portfolio that makes mobility safe, exciting, connected, and autonomous. This includes sensor solutions, displays, braking and comfort systems as well as comprehensive expertise in software, architecture platforms, and assistance systems for software-defined vehicles. In the fiscal year 2024 the business areas, which now belong to AUMOVIO, generated sales of 19.6 billion Euro. The company is headquartered in Frankfurt, Germany and has about 87.000 employees in more than 100 locations worldwide"
We'll put that in
. Job Description responsibilities: list of duties: - Act as the primary technical liaison and escalation point for customer issues, ensuring timely and effective resolution and provide On-site customer coordination of all regional technical topics. - Analyze complex technical problems, diagnose root causes, and develop comprehensive solutions in collaboration with engineering teams - Communicate technical concepts and solutions clearly to customers with varying levels of technical expertise - Manage customer relationships proactively, maintaining regular contact and ensuring satisfaction - Collaborate with manufacturing, quality, and design teams to resolve technical challenges and optimize operations - Conduct technical training sessions and knowledge transfer activities with customers to enhance their product utilization - Collaborate with cross-functional engineering teams to identify product improvements and implement cost reduction measures - Support root cause analysis related to production issues, 0KM failures, and field returns, as applicable. - Documentation of open issues related to customer development, customer meeting minutes, and support driving open issues to closure. - Primary interface between Continental and Customer change control databases - Coordination of prototypes including scheduling, preparation, shipping, tracking, and invoicing We need to preserve all. We'll put each as
- .
Requirements (required qualifications):
List:
- Bachelor’s degree in engineering or related technical discipline required.
- 5 or more years of relevant professional automotive software experience in customer-facing technical support, engineering, customer liaison, or a related technical role
- Ability to troubleshoot complex technical issues, analyze root causes, and support practical resolution plans.
- Ability to translate complex technical information for customers and internal stakeholders with varying technical backgrounds.
- Clear written and verbal communication skills, including the ability to explain technical concepts to technical and non-technical audiences.
- Experience managing customer relationships and supporting escalated technical or customer issues professionally.
- Experience coordinating multiple technical initiatives, priorities, or workstreams across cross-functional teams.
- Ability to collaborate effectively across engineering, manufacturing, quality, design, and customer-facing teams.
- Up to 10% of domestic travel required
- Legal authorization to work in the U.S. is required. We will not sponsor individuals for employment visas now or in the future for this job posting.
- Relocation assistance is not offered for this position.
We'll put each as
- . Qualifications (preferred qualifications) list: - 7 or more years of relevant professional automotive software experience in customer-facing technical support, engineering, customer liaison, or a related technical role - Background in the automotive, manufacturing, or industrial engineering sectors - Developing and automating scripts to improve efficiency and reducing time to complete tasks. - Knowledge of quality assurance, compliance standards and regulatory requirements - Familiarity with industry-standard diagnostic and testing tools and ethernet communications. - Experience with process improvement methodologies and continuous quality initiatives - Experience supporting GM or similar automotive OEM/customer accounts - Demonstrated ability to proactively identify inefficiencies in existing workflows and develop scripted automation solutions We'll put as
- . Skills: maybe we could extract some skill items from preferred qualifications that are skills: e.g., "Developing and automating scripts", "Knowledge of quality assurance...", "Familiarity with industry-standard diagnostic and testing tools and ethernet communications", "Experience with process improvement methodologies", "Experience supporting GM...", "Demonstrated ability to proactively identify inefficiencies...". But we already used those under Qualifications. Perhaps we could treat Qualifications as required and Skills as preferred. But we already used Requirements for required. So we could swap: Requirements = required qualifications, Skills = preferred qualifications. Then we need a Qualifications section maybe for something else? But we have no other content. Could omit Qualifications heading if no content. But we have preferred qualifications; we could put them under Skills. Then we need a Qualifications section? Not needed if we don't have content. The instruction: include a section ONLY when the posting has real, specific content for it. So we can omit Qualifications if we don't have content for it. We have required qualifications (we put under Requirements). Preferred qualifications we can put under Skills. That seems reasonable. Thus sections: - About the role (company description) - Responsibilities (duties) - Requirements (required qualifications) - Skills (preferred qualifications / skills) - Benefits (perks) We'll not include Qualifications or Pay or Schedule. Now Benefits: list from Additional Information: - Robust Total Rewards Package - Paid Time Off - Employee Discounts - Competitive Bonus Programs - Employees 401k Match - Diverse & Inclusive Work Environment with 20+ Employee Resource groups. - Employee Assistance Program - Future Growth Opportunities, including personal and professional - And many more benefits that come with working for a global industry leader! We need to preserve all. The last line is vague but still a benefit statement; we keep. We'll put each as
- .
Now ensure we don't include boilerplate like "All your information will be kept confidential according to EEO guidelines." etc. Remove.
Now produce HTML fragment:
About the role
Since its spin-off in September 2025, AUMOVIO continues the business of the former Continental group sector Automotive as an independent company. The technology and electronics company offers a wide-ranging portfolio that makes mobility safe, exciting, connected, and autonomous. This includes sensor solutions, displays, braking and comfort systems as well as comprehensive expertise in software, architecture platforms, and assistance systems for software-defined vehicles. In the fiscal year 2024 the business areas, which now belong to AUMOVIO, generated sales of 19.6 billion Euro. The company is headquartered in Frankfurt, Germany and has about 87.000 employees in more than 100 locations worldwide
Responsibilities
- Act as the primary technical liaison and escalation point for customer issues, ensuring timely and effective resolution and provide On-site customer coordination of all regional technical topics.