Autonomy Systems Engineering Specialist
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no filler. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Any offer of employment is conditioned upon the successful completion of a drug screen." That's legal boilerplate; remove. Also remove "Caterpillar is an Equal Opportunity Employer..." etc. Remove "Not ready to apply? Join our Talent Community." Also remove "Posting Dates September 15, 2026 - September 29, 2026". Also remove "This position requires working onsite five days a week." That's schedule info; we can include Schedule section if we have specifics. It says "This position requires working onsite five days a week." That's schedule detail. Also "Relocation is available for this position." That's maybe benefits? Could be part of Benefits or Additional Information. "Visa Sponsorship is not available for this position." That's also info but maybe not needed; could be omitted as not a benefit? It's a condition; maybe we can include in Additional Information but we are not to create sections unless content. Could include in a paragraph under Additional Information? But we only have allowed headings; we could put that info in a
under maybe "About the role" or a generic paragraph. However instructions: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have other headings not listed? It says use for section headings (e.g. About the role, Responsibilities...). Likely we should stick to those headings only. So we need to map content to those sections.
Let's extract:
About the role: introductory paragraphs describing role, mission, etc. Could be first paragraph: "Your Work Shapes the World at Caterpillar Inc...." plus description of role contributions. We'll put that in About the role.
Responsibilities: bullet list under "What You Will Do". Those are duties.
Requirements: maybe "What You Have" includes Systems Engineering Experience etc. Could be Requirements.
Qualifications: Education Requirements etc. Could be Qualifications.
Skills: maybe the list of knowledge areas under "What You Have" after Systems Engineering Experience? Actually "What You Have" includes Systems Engineering Experience, Problem Solving, Software Development Life Cycle, Software Product Testing, Application Development Tools, Technical Troubleshooting, Education Requirements. Those could be Skills or Requirements. We need to decide.
We have also "Consideration For Top Candidates" list: many specific experiences. Could be Qualifications or Requirements.
We also have "Additional Information": onsite Tucson, relocation assistance may be available, visa sponsorship not available, travel up to 15%, Pay Range, Benefits list, schedule (onsite five days a week). So we need Pay section with the range. Benefits section with list. Schedule section with "This position requires working onsite five days a week." Also maybe mention travel up to 15% as part of Schedule? Could be separate but we only have Schedule heading; we can include both.
We must not include filler like "commensurate with experience" etc. In Education Requirements: "Bachelor’s Degree in Computer Science, Engineering, or related field – or commensurate industry experience." That includes "commensurate industry experience" which is filler? It's a phrase but it's part of the requirement; we should keep it? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It says not to create a heading followed by filler text. But having the phrase inside a paragraph is okay? It says "never emit a heading followed by filler/placeholder text". So if we have a section heading and then only filler text, that's not allowed. But if we have substantive content plus that phrase, it's okay. We'll keep.
We must not repeat job title as heading. Not needed.
We must not include Job ID/requisition numbers.
We must remove duplicated lines.
Now craft HTML.
Structure:
About the role
About the role
... paragraphs ...
Responsibilities
- Define, decompose, and manage system‑level requirements and interfaces
- Lead or support system integration and validation activities
- Ensure alignment between architecture intent, implementation, and verification
- Collaborate across software, hardware, machine, and site teams
- Communicate system readiness, technical risk, and trade‑offs to stakeholders
- Document system architecture, design decisions, and success criteria
- Apply engineering judgment to balance time, cost, quality, and risk
Requirements
Systems Engineering Experience: Demonstrated experience leading system requirements development and management across complex, multi-team or multi-product environments. Proven experience defining system architecture, interfaces, and integration strategies that scale across platforms and industries. Experience making architectural trade-offs and influencing technical direction beyond a single team or product.
Problem Solving: Knowledge of approaches, tools, techniques for recognizing, anticipating, and resolving organizational, operational or process problems; ability to apply knowledge of problem solving appropriately to diverse situations.
Software Development Life Cycle: Knowledge of software development life cycle; ability to use a structured methodology for delivering and managing new or enhanced software products to the marketplace.
Software Product Testing: Knowledge of software product testing; ability to design, plan, and execute testing strategies and tactics to ensure software product quality and adherence to stated requirements.
Application Development Tools: Knowledge of application and system development; ability to utilize a variety of specific tools and toolkits for developing applications.
Technical Troubleshooting: Knowledge of technical troubleshooting approaches, tools and techniques; ability to anticipate, recognize, and resolve technical issues on hardware, software, application or operation.
Alternatively could combine into- but each is a paragraph; but we can use
- for any list of duties/requirements/benefits, and
for prose. So for requirements we could make a list. However the content is not a simple list; it's categories with descriptions. Could treat each as list item with description inside? Might be okay to use
. We'll keep as
.
Qualifications
Education Requirements: Bachelor’s Degree in Computer Science, Engineering, or related field – or commensurate industry experience.
Consideration For Top Candidates: Proven experience as a Systems Engineer on software and/or hardware product development programs; onboard or embedded systems preferred. Experience developing system requirements and supporting integration and testing efforts; collaboration with other engineering teams. Proven experience in mentoring or influencing other systems engineers. Experience with field testing, HIL and providing ground support preferred. Experience supporting L6/L8 requirements decomposition. Domain experience with Loaders, Haul Trucks, Dozers and Shovels preferred. Experience with Site Autonomy Platforms preferred. Experience with Construction and Mining industry preferred. Experience supporting embedded / onboard development for robotics or autonomy products preferred.
We could also split into list but okay.Skills
Maybe we can combine some of the knowledge areas that are not already covered. But we already covered Systems Engineering Experience etc. Could treat those as Skills. However we already used them under Requirements. Might be duplication. Better to follow sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have used Requirements for the experience categories; Qualifications for education and top candidates; Skills maybe for the knowledge areas (Problem Solving, SDLC, Testing, Tools, Troubleshooting). But we already used those under Requirements. Let's restructure: Let's assign: - About the role: intro. - Responsibilities: What You Will Do list. - Requirements: Systems Engineering Experience (lead system requirements, architecture, trade-offs). - Qualifications: Education Requirements + Consideration For Top Candidates list. - Skills: Problem Solving, Software Development Life Cycle, Software Product Testing, Application Development Tools, Technical Troubleshooting. - Benefits: list of benefits. - Pay: Pay Range. - Schedule: onsite five days a week, travel up to 15%, relocation assistance maybe? Relocation is a benefit? Could be in Benefits but we already have benefits list; we could add relocation assistance as a benefit bullet. But the instruction: only include Benefits section if posting actually states them. It does state benefits list; we can include relocation assistance there as well. However the posting also says "Relocation assistance may be available for this position." and "Relocation is available for this position." We'll add to Benefits. Visa sponsorship not available: maybe not a benefit; we could omit as it's not a benefit; but could be included under Additional Information but we have no heading for that. Might be okay to omit as it's not a benefit, pay, schedule. Could be placed under About the role as a note? But it's not about role. Might be considered boilerplate? It's a condition; maybe we should keep it as a paragraph under About the role? Not sure. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Visa sponsorship is not exactly those; it's a condition of employment. Might be considered legal? It's about immigration. Could be considered legal boilerplate. Safer to omit. Travel up to 15%: schedule. Now craft HTML. We need to ensure no extra whitespace? Just output. Let's write:About the role
Your Work Shapes the World at Caterpillar Inc. When you join Caterpillar, you're joining a global team who cares not just about the work we do – but also about each other. We are the makers, problem solvers, and future world builders who are creating stronger, more sustainable communities. We don't just talk about progress and innovation here – we make it happen, with our customers, where we work and live. Together, we are building a better world, so we can all enjoy living in it. This role contributes to the design, integration, and implementation of system capabilities across Caterpillar technology platforms. The Senior Systems Engineer leads system‑level integration, requirements definition, and architectural alignment for autonomy and site technology solutions. Operating with a high degree of independence, this role applies systems engineering expertise to integrate software, hardware, and operational workflows across machine, site, and platform boundaries. The engineer influences technical decisions across teams while balancing product delivery constraints and long‑term system sustainability. This team supports our Command for Hauling integration for drive‑by‑wire systems. You will work as the engineering interface between L8 Autonomous Hauling Application teams and L6 base machine systems teams. You will be responsible for autonomy hardware and software solution integration with base machine systems.
Responsibilities
- Define, decompose, and manage system‑level requirements and interfaces
- Lead or support system integration and validation activities
- Ensure alignment between architecture intent, implementation, and verification
- Collaborate across software, hardware, machine, and site teams
- Communicate system readiness, technical risk, and trade‑offs to stakeholders
- Document system architecture, design decisions, and success criteria
- Apply engineering judgment to balance time, cost, quality, and risk
Requirements
Systems Engineering Experience:
for prose. The instruction: Use