Control Systems Engineering Specialist

We need to output HTML fragment with sections: About the role? The description includes intro paragraphs. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real content. We need to parse the posting. Content: - Intro: "Career Area Engineering Job Description 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 position within Integrated Machine Systems supports the design and development of Tech Platform 1.0 electronic systems used on Telehandler applications within Building Construction products (BCP). This individual ensures the application software is released to production in a manner that ensures superior performance, durability, quality, and serviceability. The position will function as both an individual contributor and a member of a cross-functional project team supporting Telehandler machine products. Success in this role requires a deep understanding of telehandler applications, machine electronics, display electronics, and their integration on the machines. The Telehandler System Coordinator serves as the primary technical liaison between product groups and engineering teams, helping to define requirements, coordinate system integration activities, and ensure the successful delivery of the machine electronics systems." That's about the role. Could be "About the role" heading. Then "What You Will Do" list of duties. That's responsibilities. Then "What You Will Have" list of competencies/skills. That could be "Skills" or "Qualifications"? Actually "What You Will Have" includes analytical thinking, communicating complex concepts, problem solving, technology advising, conceptual thinking, embedded systems, requirements analysis, product development in manufacturing. Those are skills/competencies. Could be "Skills". Then "Basic Qualifications" list: Bachelor's degree, solid experience, demonstrated technical leadership, strong analytical and problem-solving capabilities, proven ability to effectively communicate technical information. That's qualifications. Then "Top Candidates Will Also Have Experience with:" list of specific technologies: Git, MATLAB/Simulink, C, CANape, CANalyzer, Cat ET Service Tool, Ethernet-based communication systems, CAN / SAE J1939 networks, experience troubleshooting electrical and electronic control systems, experience with machines, engine, or embedded control system development, knowledge of Caterpillar diagnostic and event systems, knowledge of service tools, SuperCom II, and Vector-based development tools, experience with safety-critical systems and functional safety concepts, experience coordinating cross-functional NPI activities. That could be "Preferred Qualifications" or "Additional Skills". We could put under "Qualifications" or "Skills". But we have separate sections: Requirements, Qualifications, Skills. We need to decide. We have "Basic Qualifications" and "Top Candidates Will Also Have Experience with". Could combine into "Qualifications" (basic) and maybe "Preferred Qualifications". But we only have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map: - About the role: intro paragraph(s) - Responsibilities: "What You Will Do" list - Qualifications: Basic Qualifications + Top Candidates Will Also Have Experience with (maybe as combined) - Skills: "What You Will Have" list (competencies) - Benefits: list of benefits - Pay: summary pay range - Schedule: "This position requires working onsite five days a week." Also relocation info maybe not schedule. But schedule is about work schedule: onsite five days a week. Also maybe travel 10%? That's not schedule but could be included. However schedule section only if posting actually states them. It does state "This position requires working onsite five days a week." So we can include schedule. We also have location, relocation assistance, sponsorship not available, travel 10%, posting dates, drug screen, EEO etc. Those are minor metadata; we can fold into a short

or drop. According to instructions: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short paragraph for location, relocation, travel, posting dates maybe. But we should avoid boilerplate like EEO, equal-opportunity, scam-warning. Remove those. We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all substantive content: intro, responsibilities list, qualifications list, skills list, benefits list, pay range, schedule (onsite five days a week), location, relocation assistance, travel 10%, posting dates maybe? The posting dates are substantive? Might be considered metadata but could be kept. However instructions: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Posting dates are not those; they could be kept. But we need to decide if we should include them. The instruction says "fold minor metadata into a short

or drop it." Posting dates could be considered minor metadata. Might be okay to include in a short p. We also have "Any offer of employment is conditioned upon the successful completion of a drug screen." That's also minor metadata; could be included. We must not repeat the job title as a heading. The job title is not given explicitly but we can ignore. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state pay range, benefits list, schedule (onsite five days a week). So we include those. We must not emit a heading followed by filler/placeholder text. Ensure we have real content. Now produce HTML fragment: use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide which sections to include: - About the role: prose (maybe multiple paragraphs). We'll combine intro paragraphs into one

  maybe multiple

  s. - Responsibilities:

  Responsibilities

  then
  with each duty from "What You Will Do". Need to capture each bullet. List of duties: - Coordinate Integrated Machine Systems support for product group activities. - Document requirements and supporting information required for regulatory compliance. - Support software verification activities on test benches and machines. - Configure and maintain test bench hardware and software environments. - Develop, execute, and document verification and validation test plans. - Evaluate and support the development of new machine safety features. - Gather, document, and manage feature requirements and specifications. - Provide technical support for machine development programs. - Lead or support troubleshooting and resolution of software and system defects. - Coordinate integration activities between electronic control modules, sensors, displays, and third-party components. - Communicate technical information effectively to clients, team members, suppliers, process partners, and leadership. - Support product releases through system verification, issue resolution, and production implementation activities. That's 12 items. - Qualifications: we have Basic Qualifications and Top Candidates Will Also Have Experience with. Could combine into one
  with all items. But we might separate into "Qualifications" (basic) and maybe "Preferred Qualifications" but we don't have that heading. We could still include both under Qualifications heading, maybe separate with a note? But we must not invent headings not allowed. So we can just list all under Qualifications. Basic Qualifications items: - Bachelor’s degree in electrical engineering, Computer Engineering, or a related engineering field. - Solid experience in software development, embedded controls, machine systems, or related engineering disciplines. - Demonstrated technical leadership and project coordination skills. - Strong analytical and problem-solving capabilities. - Proven ability to effectively communicate technical information to diverse audiences including team members, leadership, customers, and suppliers. Top Candidates Will Also Have Experience with items: - Experience with: Git - MATLAB/Simulink, C - CANape - CANalyzer - Cat ET Service Tool - Ethernet-based communication systems - CAN / SAE J1939 networks - Experience troubleshooting electrical and electronic control systems. - Experience with machines, engine, or embedded control system development. - Knowledge of Caterpillar diagnostic and event systems. - Knowledge of service tools, SuperCom II, and Vector-based development tools. - Experience with safety-critical systems and functional safety concepts. - Experience coordinating cross-functional NPI (New Product Introduction) activities. We need to preserve the exact phrasing. Some items are combined like "Experience with: Git MATLAB/Simulink, C". Might need to split? The original says "Experience with: Git MATLAB/Simulink, C CANape CANalyzer Cat ET Service Tool Ethernet-based communication systems CAN / SAE J1939 networks". Actually it's a sentence: "Experience with: Git MATLAB/Simulink, C CANape CANalyzer Cat ET Service Tool Ethernet-based communication systems CAN / SAE J1939 networks". That's ambiguous. Better to keep as one bullet: "Experience with: Git, MATLAB/Simulink, C, CANape, CANalyzer, Cat ET Service Tool, Ethernet-based communication systems, CAN / SAE J1939 networks". But we must not invent or summarize away detail. We can keep as is: "Experience with: Git MATLAB/Simulink, C CANape CANalyzer Cat ET Service Tool Ethernet-based communication systems CAN / SAE J1939 networks". That's a bit messy but it's the original. However we can split into separate bullets for clarity but that might be summarizing? It's still preserving detail but splitting may be okay as it's not inventing. However we risk altering the original grouping. Safer to keep as one bullet as originally written. Then the rest are separate sentences. Thus Qualifications list will be a mix of bullet points. - Skills: from "What You Will Have" list: Analytical Thinking: Knowledge of techniques and tools that promote effective analysis; ability to determine the root cause of organizational problems and create alternative solutions that resolve these problems. Communicating Complex Concepts: Knowledge of effective presentation tools and techniques to ensure clear understanding; ability to use summarization and simplification techniques to explain complex technical concepts in simple, clear language appropriate to the audience. 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. Technology Advising: Knowledge of effective advisory methods and ability to provide valued information and advice to clients regarding products, technologies, services and solutions for a specific technology domain. Conceptual Thinking: Knowledge of thinking and reasoning at a conceptual level; ability to identify the critical ideas and interdependencies among system elements that impact performance. Embedded Systems: Knowledge of embedded systems and their applications; ability to develop embedded systems with varying levels of complexity to control the operations of the machine it is embedded within. Requirements Analysis: Knowledge of tools, methods, and techniques of requirement analysis; ability to elicit, analyze and record required business functionality and non-functionality requirements to ensure the success of a system or software development project. Product Development in Manufacturing: Knowledge of methodologies, tools and techniques of product development; ability to design, build and manage manufacturing of new products. We'll make each as
  • with the full sentence. - Benefits: list from "Benefits Subject to plan eligibility, terms, and guidelines. This is a summary list of benefits." Then bullet list: Medical, dental, and vision benefits* Paid time off plan (Vacation, Holidays, Volunteer, etc.)* 401(k) savings plans* Health Savings Account (HSA)* Flexible Spending Accounts (FSAs)* Health Lifestyle Programs* Employee Assistance Program* Voluntary Benefits and Employee Discounts* Career Development* Incentive bonus* Disability benefits Life Insurance Parental leave Adoption benefits Tuition Reimbursement These benefits also apply to part-time employees We need to keep