Associate Motorsport Software Engineer
Bosch USA · Farmington Hills, MI · 3 wk ago
EngineeringFull-time
We need to output HTML fragment with sections: h3 headings for sections present: About the role? Actually job description includes "Company Description", "Job Description", "What You Will Do", "Qualifications", "Ideal Candidate Characteristics", "Our Motorsport Culture", "Additional Information". We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections where there is real specific content. We need to extract content accordingly.
We have company description: can be "About the role"? Actually "Company Description" could be "About the role"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use
.
Then Ideal Candidate Characteristics: could be under Skills? Or maybe under Requirements? But we have no heading for characteristics. Could we put under Skills as well? Might be okay to add another heading? Not allowed. Could we incorporate into About the role? Might be okay. But we need to preserve all substantive info; we can put them under a Skills? Actually they are characteristics not skills. But we could still use Skills heading for them? Might be misleading but allowed headings list includes Skills. We could use Skills for both technical skills and ideal candidate characteristics. However we already used Skills for preferred qualifications. Could we combine? Might be too long.
Alternative: Use
.
Now company description paragraph: "We Are Bosch. At Bosch, we shape the future by inventing high-quality technologies and services that spark enthusiasm and enrich people’s lives. Our areas of activity are every bit as diverse as our outstanding Bosch teams around the world. Their creativity is the key to innovation through connected living, mobility, or industry. Let’s grow together, enjoy more, and inspire each other. Work Reinvent yourself: At Bosch, you will evolve.Discover new directions: At Bosch, you will find your place.Balance your life: At Bosch, your job matches your lifestyle.Celebrate success: At Bosch, we celebrate you.Be yourself: At Bosch, we value values.Shape tomorrow: At Bosch, you change lives."
That's a bit weird with missing spaces after colons. We'll keep as is.
Job Description overview: "Welcome to Bosch Motorsport, a premier supplier of electronics, sensors, actuators, and engineering services to top racing series and teams worldwide. Here at Bosch Motorsport North America, you'll be part of a growing, dynamic, and entrepreneurial team, taking
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose headings that match content. For company description maybe "About the role" is appropriate. But "About the role" usually describes the role, not company. However we can still use it for company description? Might be okay. But we could also not include a heading for company description if not matching allowed headings. However we need to preserve all substantive information; we can embed company description in a
without heading? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use for section headings (e.g. ...). Likely they expect only those headings. So we should map content to those headings.
Let's map:
- About the role: could include company description and job description overview.
- Responsibilities: "What You Will Do" bullet points.
- Requirements: "Qualifications" (required and preferred). Could split into Requirements and Skills? But we have Qualifications heading allowed. Could also have Skills heading for preferred qualifications? But we can combine.
- Benefits: Additional Information includes benefits description.
- Pay: Not specified (no pay info). So we should NOT include Pay section.
- Schedule: Travel info maybe schedule? There's travel 40-60 days per year. Could be schedule? But schedule heading is for work schedule; we have travel info. Might be considered schedule? Probably not. Better to omit Schedule unless explicit schedule like full-time, shift. Not present.
- Skills: maybe we can include preferred qualifications as Skills.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove boilerplate: EEO, drug screen, etc. Remove Equal Opportunity Employer, drug-testing, background check, etc. Also remove navigation, cookie, legal. Also remove "Additional Information" maybe includes benefits and work authorization etc. We need to keep benefits but drop work authorization line? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Work authorization is substantive? It says "Indefinite U.S. work authorized individuals only. Future sponsorship for work authorization unavailable." That's substantive. Should we keep? It's under Additional Information. It's not boilerplate; it's eligibility. We can keep it maybe under a heading? Not in allowed headings. Could we put it under About the role? Might be okay to include as a paragraph after company description. But we need to keep it.
We also need to remove "Equal Opportunity Employer, including disability / veterans Bosch adheres to Federal, State, and Local laws regarding drug-testing. Employment is contingent upon the successful completion of a drug screen and background check. Candidates who have been offered the position must pass both screenings before their start date." That's boilerplate EEO and drug screen; remove.
Also remove "Our Motorsport Culture" maybe could be under About the role? But we have heading for About the role; we could include culture there. However we might also create a separate heading? Not allowed. Could we add a heading "Our Motorsport Culture"? Not in allowed list; better to avoid. So we incorporate that content into About the role or maybe under Responsibilities? Probably About the role.
We need to output only HTML fragment, no /. Use for headings, - for lists,
for prose.
We need to preserve all substantive information: company description, job description overview, responsibilities list, qualifications (required and preferred), ideal candidate characteristics, culture, benefits, work authorization.
We need to avoid duplication: some lines repeated like "Domestic and International Travel" appears both in responsibilities and qualifications? Actually travel appears in responsibilities and also repeated later. We should keep but not duplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to deduplicate identical lines. The travel line appears twice: "Domestic and International Travel Travel domestically and internationally (approximately 40–60 days per year) to provide elite technical support directly on-site at customer, track, and other development sites." and earlier "This position requires the ability to work effectively in fast-paced, dynamic environments and involves frequent domestic and international travel (approximately 40–60 days per year)." Slightly different but similar. We'll keep both? They are not identical but convey same info. Might be considered duplicated? Safer to keep both as they are slightly different phrasing. But we could combine? The instruction says remove duplicated lines, not necessarily similar meaning. We'll keep both.
Now structure:
About the role
Company description paragraph(s) + job description overview + maybe culture.
Then Responsibilities
- ... each bullet.
Then Requirements
Maybe we split required qualifications into Requirements and preferred into Skills. Let's do:
Requirements
- Bachelor’s Degree in Engineering, Computer Science, or a related technical field.
- 1+ years of experience in industry-relevant application engineering (academic or industry experience).
- 1+ years of experience working with industry-standard data acquisition and data analysis software.
- Experience in professional motorsport, significant collegiate racing (e.g., Formula SAE, EcoCAR), or equivalent high-performance environments.
Then Skills
- Preferred: Automotive Communications and Networking Knowledge of network communication frameworks, including the OSI and TCP/IP models. Experience with wired and wireless networking technologies and protocols, such as TCP, UDP, Ethernet, Wi-Fi, and cellular communications. Familiarity with hardware configuration, communication software, embedded systems, Linux or Windows command-line environments, and automotive communication protocols such as CAN and Ethernet.
... etc for each preferred bullet.
But we need to keep each preferred qualification as separate list items? The posting lists them as bullet points under Preferred Qualifications with sub-bullets. We can treat each main bullet as a list item.
Let's extract preferred qualifications list:
- Automotive Communications and Networking Knowledge of network communication frameworks, including the OSI and TCP/IP models. Experience with wired and wireless networking technologies and protocols, such as TCP, UDP, Ethernet, Wi-Fi, and cellular communications. Familiarity with hardware configuration, communication software, embedded systems, Linux or Windows command-line environments, and automotive communication protocols such as CAN and Ethernet.
- Cloud Technologies and Data Streaming Experience with Cloud-based services, containerized applications, and data-stream processing technologies, such as Microsoft Azure, AWS, Kubernetes, MQTT, and Grafana.
- Database Management and Querying Experience writing queries using SQL or similar database query languages. Experience with relational and non-relational database technologies used to manage engineering, testing, or simulation data, such as SQL Server, MongoDB, or InfluxDB.
- Programming and Scripting Experience using programming or scripting languages, such as Python, MATLAB, or C#, for data analysis, automation, testing, or software development activities.
- Diagnostic and Engineering Tools Experience using engineering, diagnostic, or test tools such as Wireshark, CANalyzer, oscilloscopes, spectrum analyzers, or similar technologies.
- Electrical and System Analysis Ability to read and interpret electrical schematics. Experience with system troubleshooting, root-cause analysis, software debugging, and vehicle-level diagnostics.
- Powertrain and Control Systems Knowledge of or experience with internal combustion, hybrid, and/or battery-electric vehicle systems, including powertrain, chassis, or controls development.
We'll put each as
for headings, - for lists,
for prose.
We need to preserve all substantive information: company description, job description overview, responsibilities list, qualifications (required and preferred), ideal candidate characteristics, culture, benefits, work authorization.
We need to avoid duplication: some lines repeated like "Domestic and International Travel" appears both in responsibilities and qualifications? Actually travel appears in responsibilities and also repeated later. We should keep but not duplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to deduplicate identical lines. The travel line appears twice: "Domestic and International Travel Travel domestically and internationally (approximately 40–60 days per year) to provide elite technical support directly on-site at customer, track, and other development sites." and earlier "This position requires the ability to work effectively in fast-paced, dynamic environments and involves frequent domestic and international travel (approximately 40–60 days per year)." Slightly different but similar. We'll keep both? They are not identical but convey same info. Might be considered duplicated? Safer to keep both as they are slightly different phrasing. But we could combine? The instruction says remove duplicated lines, not necessarily similar meaning. We'll keep both.
Now structure:
About the role
Company description paragraph(s) + job description overview + maybe culture.
Then Responsibilities
- ... each bullet.
Then Requirements
Maybe we split required qualifications into Requirements and preferred into Skills. Let's do:
Requirements
- Bachelor’s Degree in Engineering, Computer Science, or a related technical field.
- 1+ years of experience in industry-relevant application engineering (academic or industry experience).
- 1+ years of experience working with industry-standard data acquisition and data analysis software.
- Experience in professional motorsport, significant collegiate racing (e.g., Formula SAE, EcoCAR), or equivalent high-performance environments.
Then Skills
- Preferred: Automotive Communications and Networking Knowledge of network communication frameworks, including the OSI and TCP/IP models. Experience with wired and wireless networking technologies and protocols, such as TCP, UDP, Ethernet, Wi-Fi, and cellular communications. Familiarity with hardware configuration, communication software, embedded systems, Linux or Windows command-line environments, and automotive communication protocols such as CAN and Ethernet.
... etc for each preferred bullet.
But we need to keep each preferred qualification as separate list items? The posting lists them as bullet points under Preferred Qualifications with sub-bullets. We can treat each main bullet as a list item.
Let's extract preferred qualifications list:
- Automotive Communications and Networking Knowledge of network communication frameworks, including the OSI and TCP/IP models. Experience with wired and wireless networking technologies and protocols, such as TCP, UDP, Ethernet, Wi-Fi, and cellular communications. Familiarity with hardware configuration, communication software, embedded systems, Linux or Windows command-line environments, and automotive communication protocols such as CAN and Ethernet.
- Cloud Technologies and Data Streaming Experience with Cloud-based services, containerized applications, and data-stream processing technologies, such as Microsoft Azure, AWS, Kubernetes, MQTT, and Grafana.
- Database Management and Querying Experience writing queries using SQL or similar database query languages. Experience with relational and non-relational database technologies used to manage engineering, testing, or simulation data, such as SQL Server, MongoDB, or InfluxDB.
- Programming and Scripting Experience using programming or scripting languages, such as Python, MATLAB, or C#, for data analysis, automation, testing, or software development activities.
- Diagnostic and Engineering Tools Experience using engineering, diagnostic, or test tools such as Wireshark, CANalyzer, oscilloscopes, spectrum analyzers, or similar technologies.
- Electrical and System Analysis Ability to read and interpret electrical schematics. Experience with system troubleshooting, root-cause analysis, software debugging, and vehicle-level diagnostics.
- Powertrain and Control Systems Knowledge of or experience with internal combustion, hybrid, and/or battery-electric vehicle systems, including powertrain, chassis, or controls development.
We'll put each as
for prose. We need to preserve all substantive information: company description, job description overview, responsibilities list, qualifications (required and preferred), ideal candidate characteristics, culture, benefits, work authorization. We need to avoid duplication: some lines repeated like "Domestic and International Travel" appears both in responsibilities and qualifications? Actually travel appears in responsibilities and also repeated later. We should keep but not duplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to deduplicate identical lines. The travel line appears twice: "Domestic and International Travel Travel domestically and internationally (approximately 40–60 days per year) to provide elite technical support directly on-site at customer, track, and other development sites." and earlier "This position requires the ability to work effectively in fast-paced, dynamic environments and involves frequent domestic and international travel (approximately 40–60 days per year)." Slightly different but similar. We'll keep both? They are not identical but convey same info. Might be considered duplicated? Safer to keep both as they are slightly different phrasing. But we could combine? The instruction says remove duplicated lines, not necessarily similar meaning. We'll keep both. Now structure:
About the role
Company description paragraph(s) + job description overview + maybe culture.
ThenResponsibilities
- ... each bullet.
Requirements
Maybe we split required qualifications into Requirements and preferred into Skills. Let's do:Requirements
- Bachelor’s Degree in Engineering, Computer Science, or a related technical field.
- 1+ years of experience in industry-relevant application engineering (academic or industry experience).
- 1+ years of experience working with industry-standard data acquisition and data analysis software.
- Experience in professional motorsport, significant collegiate racing (e.g., Formula SAE, EcoCAR), or equivalent high-performance environments.
Skills
- Preferred: Automotive Communications and Networking Knowledge of network communication frameworks, including the OSI and TCP/IP models. Experience with wired and wireless networking technologies and protocols, such as TCP, UDP, Ethernet, Wi-Fi, and cellular communications. Familiarity with hardware configuration, communication software, embedded systems, Linux or Windows command-line environments, and automotive communication protocols such as CAN and Ethernet. ... etc for each preferred bullet.