Jobs · Information Technology · Michigan

Agentic Software Engineer

Bosch USA · Plymouth, MI · 3 wk ago
Information TechnologyFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: Company Description (maybe not needed as heading? Could be "About the role"? Actually "Company Description" is about Bosch, not role. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content. We have sections: Job Description (Position Purpose, Key Responsibilities, etc). Could map to "Responsibilities". Also "Qualifications" section present. Also "Additional Information" includes benefits, travel, etc. Also "Core Team works on Tuesday, Wednesday and Thursday in Plymouth 5%-10% Travel Passport required". That's schedule info (days). Also "Comprehensive Benefit Offering – All benefits are effective DAY 1! ..." That's benefits. Also "Indefinite U.S. work authorized individuals only. Future sponsorship for work authorization not available." That's maybe a note but not a heading. We should not repeat job title as heading. No Job ID. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes EEO lines: "All your information will be kept confidential according to EEO guidelines. Equal Opportunity Employer, including disability / veterans." That's boilerplate; we should remove. Also "The Bosch Group is a leading global supplier..." that's company description but maybe we keep as part of "About the role"? Actually it's company description; we could include under a heading "About Bosch" but not in list of allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could treat company description as "About the role"? Not exactly. But we could include a short paragraph under "About the role" describing Bosch and the role purpose. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Probably we should stick to those headings where applicable. Thus we can have:

About the role

with content: Position Purpose description and maybe company description? The Position Purpose: "Deliver business outcomes on existing MA/BDO3 platforms by combining strong software engineering discipline with effective orchestration of AI agents." plus maybe mention Bosch context. We could also include company description as part of About the role. Then

Responsibilities

with bullet list of responsibilities from Key Responsibilities sections. Then

Qualifications

with bullet list of Required Experience and Agentic Engineering Skills and Core Competencies? Actually Qualifications section includes Required Experience, Agentic Engineering Skills, Core Competencies. Could combine. Then

Benefits

with bullet list from Comprehensive Benefit Offering. Then

Schedule

with info: Core Team works on Tuesday, Wednesday and Thursday in Plymouth 5%-10% Travel Passport required. We should not include Pay section because no pay info. We must not include filler like "commensurate with experience". Not present. We must not repeat job title. We must output only HTML fragment. Let's extract details precisely. Company Description: "Bosch provides the aftermarket and workshops worldwide with a complete range of diagnostic and repair shop equipment and a wide range of spare parts for passenger cars and commercial vehicles. Its product portfolio includes products made as Bosch original equipment, as well as aftermarket products and services developed and manufactured in-house. In its “Automotive Service Solutions” operations, Bosch supplies testing and repair-shop technology, diagnostic software, service training, and information services. In it's Automotive Aftermarket division, Bosch employs more than 17,000 associates in 150 countries. Do you want beneficial technologies being shaped by your ideas? Whether in the areas of mobility solutions, consumer goods, industrial technology or energy and building technology - with us, you will have the chance to improve quality of life all across the globe. Welcome to Bosch." Position Purpose: "Deliver business outcomes on existing MA/BDO3 platforms by combining strong software engineering discipline with effective orchestration of AI agents. The role focuses on practical delivery in brownfield environments where engineers must understand existing code, integrations, business rules, data flows, operational constraints, and architecture guardrails before making safe changes." Key Responsibilities: bullet points under Feature Delivery & Defect Resolution, Agentic Engineering Execution, Brownfield System Understanding, Quality, Security & Release Readiness, DevOps & Operational Contribution. Let's list them: Feature Delivery & Defect Resolution: - Deliver new features, enhancements, defect fixes, integrations, and operational improvements across brownfield enterprise applications. - Translate Jira stories, BDD scenarios, business rules, architecture guidance, and test cases into working software. - Use AI agents to accelerate implementation while validating every generated output against business intent and technical standards. - Own end-to-end delivery from analysis through code, tests, pull request, release readiness, and production validation. Agentic Engineering Execution: - Direct AI agents to perform codebase discovery, dependency analysis, impact analysis, refactoring, code generation, test generation, documentation, and troubleshooting. - Create and improve reusable prompts, agent instructions, workflow templates, and context packages for recurring engineering tasks. - Review, correct, and integrate AI-generated code and artifacts using engineering judgment and established review practices. - Contribute improved system knowledge back into shared repositories so future agents and engineers become more effective. Brownfield System Understanding: - Analyze existing application behavior, integration dependencies, data models, legacy business rules, configuration, logs, and operational constraints before making changes. - Preserve compatibility with existing business processes and upstream/downstream systems. - Identify technical debt, risky dependencies, test gaps, and modernization opportunities during normal delivery work. - Support incremental modernization such as framework upgrades, API enablement, cloud migration, component refactoring, and test automation. Quality, Security & Release Readiness: - Ensure delivered changes meet architecture standards, secure coding practices, performance expectations, and operational readiness requirements. - Create or update automated unit, integration, regression, API, security, and BDD-based tests where appropriate. - Validate AI-generated tests for meaningful coverage rather than accepting superficial test output. - Participate in code reviews, pull request reviews, deployment preparation, CI/CD execution, and production support. DevOps & Operational Contribution: - Use Azure DevOps, Git, CI/CD pipelines, observability tools, and deployment automation to deliver reliable software. - Use AI-assisted log analysis and root cause investigation to speed incident response and operational support. - Improve documentation, runbooks, monitoring queries, and support knowledge based on delivery and production learning. Qualifications: Required Experience: - 5+ years of professional software engineering experience. - Strong hands-on experience delivering changes in complex brownfield enterprise applications. - Experience with C#, .NET Framework/.NET Core, ASP.NET, REST APIs, SQL Server, Azure services, and integration technologies. - Experience with Git, pull requests, CI/CD pipelines, automated testing, and production release practices. - Ability to work with incomplete documentation and reverse engineer behavior from code, tests, logs, databases, and business feedback. Agentic Engineering Skills: - Effective use of GitHub Copilot, Microsoft Copilot, coding agents, test generation tools, and documentation assistants. - Prompting and agent instruction design for engineering tasks. - Use of AI for impact analysis, code comprehension, refactoring, test creation, documentation, and troubleshooting. - Ability to validate, challenge, and improve AI-generated output. - Understanding of AI usage risks including hallucination, insecure code, missing edge cases, weak tests, stale context, and hidden integration dependencies. Core Competencies: - Strong engineering discipline and quality ownership. - Practical problem solving in legacy and integration-heavy environments. - Human + AI collaboration mindset. - Attention to traceability, testability, security, and maintainability. - Ability to communicate implementation risks and tradeoffs clearly. - Continuous learning and willingness to improve agent workflows over time. Additional Information: - Indefinite U.S. work authorized individuals only. Future sponsorship for work authorization not available. - Core Team works on Tuesday, Wednesday and Thursday in Plymouth 5%-10% Travel Passport required - All your information will be kept confidential according to EEO guidelines. Equal Opportunity Employer, including disability / veterans. (remove) - Comprehensive Benefit Offering – All benefits are effective DAY 1! Medical, Dental & Vision Life and Supplement Life Long and Short Term Disability Paid Time Off & Holidays 401K – with generous company match In addition to 401K, additional retirement benefit 100% company paid Annual bonuses Tuition Assistance Paid Volunteer Time Associate Discounts on Bosch products like home appliances, power-tools, thermal products like tank-less water heaters and more Also there is more company description after benefits but that's boilerplate; we can ignore. We need to preserve all substantive information; we should not drop the "Indefinite U.S. work authorized individuals only. Future sponsorship for work authorization not available." That's substantive; maybe we can include under a short paragraph under Qualifications or Additional Info. Since we don't have a heading for work authorization, we could fold into Qualifications as a note. Similarly "Core Team works on Tuesday, Wednesday and Thursday in Plymouth 5%-10% Travel Passport required" is schedule. We need to output HTML with

headings and
  • for lists,

    for prose. We must not include any markdown fences. Let's craft:

    About the role

    Bosch provides the aftermarket and workshops worldwide with a complete range of diagnostic and repair shop equipment and a wide range of spare parts for passenger cars and commercial vehicles. Its product portfolio includes products made as Bosch original equipment, as well as aftermarket products and services developed and manufactured in-house. In its “Automotive Service Solutions” operations, Bosch supplies testing and repair-shop technology, diagnostic software, service training, and information services. In its Automotive Aftermarket division, Bosch employs more than 17,000 associates in 150 countries. Do you want beneficial technologies being shaped by your ideas? Whether in the areas of mobility solutions, consumer goods, industrial technology or energy and building technology - with us, you will have the chance to improve quality of life all across the globe. Welcome to Bosch.

    Position Purpose: Deliver business outcomes on existing MA/BDO3 platforms by combining strong software engineering discipline with effective orchestration of AI agents. The role focuses on practical delivery in brownfield environments where engineers must understand existing code, integrations, business rules, data flows, operational constraints, and architecture guardrails before making safe changes.

    Then Responsibilities: we can group all bullet points under one
      with
    • each. But we might want to keep subheadings? Not required; just list. We'll output:

      Responsibilities

      • Deliver new features, enhancements, defect fixes, integrations, and operational improvements across brownfield enterprise applications.
      • Translate Jira stories, BDD scenarios, business rules, architecture guidance, and test cases into working software.
      • Use AI agents to accelerate implementation while validating every generated output against business intent and technical standards.
      • Own end-to-end delivery from analysis through code, tests, pull request, release readiness, and production validation.
      • Direct AI agents to perform codebase discovery, dependency analysis, impact analysis, refactoring, code generation, test generation, documentation, and troubleshooting.
      • Create and improve reusable prompts, agent instructions, workflow templates, and context packages for recurring engineering tasks.
      • Review, correct, and integrate AI-generated code and artifacts using engineering judgment and

Similar jobs