AI Agent Engineer

We need to output only HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also must not create sections with filler like "commensurate with experience". So we need to parse the job description and extract sections. The posting includes: - Job Description (title) - The Role (intro paragraph) - What You’ll Do (list of responsibilities) - Your Skills & Abilities (Required Qualifications) (list of required qualifications) - What Will Give You a Competitive Edge (Preferred Qualifications) (list of preferred) - GM does not provide immigration-related sponsorship... (this is a note, maybe not needed) - This role is categorized as hybrid... (Schedule? maybe schedule info) - This job may be eligible for relocation benefits. (maybe Benefits? but not explicit benefits) - About GM (company description) - Why Join Us (maybe not needed) - Benefits Overview (some generic) - Non-Discrimination and Equal Employment Opportunities (EEO) (boilerplate) - Accommodations (boilerplate) We need to include sections only when posting has real specific content. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have: - About the role: could be the intro paragraph under "The Role". That is a description of the role. So we can put that in

About the role

with

content. - Responsibilities: the "What You’ll Do" section includes bullet points (multiple sub-sections). We can extract the bullet points as list items under

• . The content includes multiple paragraphs with headings like "Strategic architecture and standards alignment", "Integration delivery and pipeline engineering", etc. Those are subheadings within responsibilities. We could treat each as a list item? The instruction: Use
  • for any list of duties/requirements/benefits. So we can treat each duty as a list item. The subheadings could be part of the list item text. We'll need to preserve all substantive info. - Requirements: maybe the "Your Skills & Abilities (Required Qualifications)" includes core experience and education, integration and software engineering proficiency, LLM prompting..., security..., etc. That's required qualifications. Could be considered Requirements. We'll put that under

    Requirements

    with list items. - Qualifications: maybe the "What Will Give You a Competitive Edge (Preferred Qualifications)" is Qualifications (preferred). Could be separate section Qualifications. We'll put that under

    Qualifications

    with list items. - Skills: maybe we could combine skills within Requirements? But we have a separate Skills section possible. The posting includes "Your Skills & Abilities (Required Qualifications)" which is essentially skills. But we already used that for Requirements. However we need to follow the instruction: Use sections only when posting has real specific content. We have content for Skills maybe under "Your Skills & Abilities". Could treat that as Skills section. But we also have Requirements (maybe core experience and education). The posting lumps them together. We need to decide how to split. We have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content maps to which. Potential mapping: - About the role: intro paragraph under "The Role". - Responsibilities: "What You’ll Do" (the detailed duties). - Requirements: "Core experience and education" (the required qualifications: 7+ years, degree, etc.) maybe also "Integration and software engineering proficiency", "LLM prompting and intelligent automation", "Security, identity, and cross-functional delivery". Those are all required qualifications. Could be considered Requirements. - Qualifications: "What Will Give You a Competitive Edge (Preferred Qualifications)" (preferred qualifications). - Skills: maybe we could extract specific skills like "Python", "REST APIs", etc. But those are already in required qualifications. Could be redundant. Perhaps we can treat Skills as a subsection of Requirements? But we need to follow instruction: include a section ONLY when posting has real specific content for it. If we don't have distinct skills beyond what's in Requirements, we could omit Skills section. However we have a Skills heading in the list; we could still omit if no specific content. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Skills if not distinct. - Benefits: The posting includes "Benefits Overview" generic but not specific benefits. It says "From day one, we're looking out for your well-being–at work and at home–so you can focus on realizing your ambitions. Learn how GM supports a rewarding career that rewards you personally by visiting Total Rewards resources." That's vague, not specific benefits like health insurance, 401k, etc. According to instruction: never create Benefits section unless posting actually states them. It does not state specific benefits, just a generic overview. So we should omit Benefits. - Pay: No pay info mentioned. Omit. - Schedule: The posting includes "This role is categorized as hybrid. This means the selected candidate is expected to report to a specific location at least 3 times a week {or other frequency dictated by their manager}. This job may be eligible for relocation benefits." That's schedule info (hybrid, expected to report 3 times a week). So we can include Schedule section with that content. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Schedule. We must not include Benefits, Pay, Skills if no specific content. Now we need to extract content precisely, preserving all substantive info, not inventing or summarizing away detail. We need to format as HTML fragment: use

    for section headings,

    • for any list of duties/requirements/benefits, and

      for prose. We need to avoid repeating job title as heading. The job title is "AI Agent Engineer". Not to be used as heading. We need to remove boilerplate: immigration note, EEO, accommodations, etc. We need to preserve all substantive info: that includes the hybrid schedule note, relocation benefits note. We need to ensure we don't include duplicated lines. Let's extract each section. **About the role**: The paragraph under "The Role": "The Role As an AI Agent Engineer, you will design, build, and scale enterprise integrations and data pipelines that modernize how systems work together across General Motors. From the software and core IT side of the transformation, you will focus on connecting Serval integrations, SaaS platforms, enterprise AI tools, and GM’s core business systems through secure, reusable, and scalable integration patterns. This role is a strong fit for an experienced engineer who can independently deliver complex integration solutions, translate business and technical requirements into practical system designs, and build supportable, production-ready pipelines that align with enterprise standards. You will partner closely with product, engineering, technical program management, security, and business stakeholders to enable reliable data flow, workflow continuity, and platform interoperability across GM, while contributing reusable patterns that can be adopted broadly across the enterprise." We need to put that in

      . Possibly we could split into multiple paragraphs but it's okay as one. **Responsibilities**: Under "What You’ll Do". It contains several subsections each with a bold heading and description. We need to capture all duties. Let's extract each bullet: - Strategic architecture and standards alignment - Build reusable services, accelerators, and reference integration templates so transformation teams can solve repeatable connectivity needs more consistently. - Apply enterprise platform guardrails by aligning integration designs with data standards, identity guidelines, security policies, and operational requirements. - Partner with Security, Privacy, Identity, Information Lifecycle Management (ILM), and Retention teams to support workflows that process sensitive or regulated data. - Evaluate incoming integration requests and recommend the appropriate technical path using approved platform capabilities, configuration options, or custom engineering. - Define integration architectures that account for system boundaries, data ownership, reliability, observability, failure handling, and long-term sustainment. - Integration delivery and pipeline engineering - Design, build, and maintain robust, resilient, and observable integrations using APIs, webhooks, scripts, connectors, middleware services, and orchestration logic. - Define source-to-destination data mappings, transformation logic, exception-handling patterns, validation rules, and monitoring approaches that support reliable day-to-day operations. - Modernize legacy interfaces, manually routed workflows, platform-specific automations, and older integrations into scalable, API-driven, and event-based integration patterns. - Connect Serval integrations with core GM platforms, including identity services, reporting environments, asset repositories, enterprise applications, and approved AI platforms. - Support end-to-end workflows that move data and trigger actions across enterprise systems. - Troubleshoot integration failures across multi-system environments and improve performance, reliability, and supportability. - LLM prompting and AI-enabled integration - Design, test, and refine prompts for large language models used within enterprise workflows and integration solutions. - Develop prompt templates, context strategies, grounding approaches, structured outputs, guardrails, and validation steps that improve accuracy, consistency, and reliability. - Integrate LLM capabilities with enterprise applications, APIs, data sources, identity services, and downstream systems while addressing security, privacy, latency, and failure-handling requirements. - Support tool calling, workflow orchestration, human-in-the-loop controls, and exception handling for AI-enabled processes. - Apply practical evaluation and monitoring approaches to assess prompt performance, workflow outcomes, and production behavior. - Migration and coexistence engineering - Design and support coexistence models that allow legacy, modern, and internal platforms to interoperate effectively during phased transformation waves. - Preserve workflow continuity where historical data, inactive-user content, or core systems must remain on legacy platforms during transition. - Support cutover sequencing, permissions validation, metadata mapping, data validation, and post-deployment stabilization to reduce operational disruption. - Identify integration risks and dependencies early and coordinate mitigation across technical and business stakeholders. - Transformation pod engagement and sustainment - Partner directly with transformation Product Leads and Technical Program Managers within business units to integrate Serval capabilities and enterprise platforms into real-world operational processes. - Provide technical leadership through design reviews, implementation guidance, troubleshooting, and engineering best practices across the program. - Author technical designs, dependency maps, data mappings, interface specifications, operational runbooks, and handover materials that support long-term sustainment of integrated solutions. - Support validation, troubleshooting, hypercare, incident resolution, and early-adoption activities during rollout. - Contribute practical feedback that improves integration governance, support models, reusable patterns, and future delivery approaches. We need to put these as list items. Could each bullet be a

    • . The subheadings could be part of the li text. We'll just output each bullet as
    • with the text. We must ensure we don't lose any detail. **Requirements**: Under "Your Skills & Abilities (Required Qualifications)". It has subsections: - Core experience and education - 7+ years of hands-on experience in integration engineering, systems engineering, software engineering, platform architecture, or enterprise application integration within complex enterprise environments. - Strong systems-thinking capability, with proven experience mapping dependencies across applications, data layers, identity services, integrations, and business processes. - Proven ability to independently lead complex integration initiatives and manage competing priorities across a highly matrixed organization. - Bachelor’s degree in Computer Science, Information Technology, Engineering, Information Systems, or a related technical field, or equivalent practical experience. - Integration and software engineering proficiency - Strong production-level proficiency in Python and core scripting or automation frameworks. - Extensive experience building and supporting enterprise-grade integrations using REST APIs, webhooks, middleware solutions, connectors, event-driven services, and ETL or data-transformation logic. - Strong understanding of