Agentic AI Engineer - AI Native Software Engineering

We need to output HTML fragment with sections: About the role? Actually the posting includes description: "In Capgemini Engineering..." then "IL TUO RUOLO" etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to parse the posting. Let's extract content: - About the role: The introductory paragraph about Capgemini Engineering and the role description: "In Capgemini Engineering, leader mondiale nei servizi di ingegneria, uniamo un team globale di talenti dell’ingegneria, scienza e tecnologia per aiutare le aziende più innovative del mondo a liberare il loro potenziale. ... Unisciti a noi per una carriera ricca di opportunità, dove potrai fare la differenza, in un ambiente in cui ogni giorno è unico." Then "IL TUO RUOLO Come Agentic AI Engineer – AI Native Software Engineering entrerai a far parte del nostro Software Engineering Center of Excellence. Lavorerai alla progettazione e allo sviluppo di piattaforme e framework basati su Generative AI, Multi-Agent Systems e tecnologie emergenti per creare capacità autonome applicate all'intero Software Development Lifecycle. Immagina di utilizzare l'AI non solo per scrivere codice, ma per contribuire alla progettazione della prossima generazione di veicoli, satelliti, sistemi di difesa, dispositivi medicali e prodotti industriali intelligenti. Questo è il tipo di sfida che ti aspetta, sarai protagonista della trasformazione verso un modello di AI-Native Engineering in cui agenti intelligenti e professionisti collaborano per accelerare la progettazione, lo sviluppo e la validazione di software, sistemi embedded e prodotti complessi." That's about the role. So we can put that in

About the role

with

paragraphs. - Responsibilities: The bullet list under "In Particolare Ti Occuperai Di" includes many items. Those are responsibilities. So we can have

Responsibilities

with

• each item. - Requirements/Qualifications/Skills: The posting has "LE TUE CARATTERISTICHE" describing sought professionals, then "Hai Probabilmente Molte Delle Seguenti Competenze" list of competencies, then "Costituiscono Titolo Preferenziale" list of preferred qualifications. We need to decide how to split into sections: Requirements, Qualifications, Skills. The instruction: Use headings for those categories. We need to map content appropriately. Typically "Requirements" are mandatory, "Qualifications" maybe preferred, "Skills" maybe technical skills. But we can combine. However we must not create empty sections. We have content for all three: we can put mandatory competencies under Requirements, preferred under Qualifications, and maybe skills under Skills (but overlapping). Could also put all competencies under Skills and leave Requirements/Qualifications empty? But we must not emit heading with filler. So we need to allocate real content to each heading. We have: - Mandatory competencies list (Hai Probabilmente Molte Delle Seguenti Competenze): includes experience in software dev using Python, Java, C++, TypeScript; experience in embedded systems; knowledge of modern SE, Systems Engineering, DevOps; experience designing distributed architectures; experience or strong interest in Generative AI, LLMs, AI-native; understanding of ML, Prompt Engineering, RAG, Agentic Workflow, Autonomous Systems; familiarity with API, microservices, distributed systems, cloud-native; knowledge of development and validation processes; ability to collaborate with multidisciplinary teams; attitude problem solving, experimentation, technical leadership; interest to transform product design via AI. - Preferred qualifications list (Costituiscono Titolo Preferenziale): experience with agentic frameworks (LangGraph, Semantic Kernel, AutoGen, CrewAI, OpenAI Agents SDK); knowledge of Multi-Agent Systems, Agent Orchestration, Autonomous Decision Making; experience with cloud platforms AWS, Azure, GCP; familiarity with GitHub Copilot, Claude Code, Codex, AI-assisted dev tools; experience with Vector DB, Knowledge Graph, knowledge management; experience designing AI enterprise workflows and intelligent scalable platforms; knowledge of AI Governance, Security, Responsible AI; experience in high-tech contexts (Automotive, Aerospace, Defence, Railway, Manufacturing, Life Sciences). We could map: - Requirements: the mandatory competencies list. - Qualifications: the preferred qualifications list. - Skills: maybe we can extract a subset like technical skills (programming languages, tools) but that overlaps. Could also combine mandatory and preferred into Skills and leave Requirements/Qualifications empty? But we need to avoid empty headings. Perhaps we can treat "Skills" as the technical skills (programming languages, frameworks, tools) from both lists, while Requirements are the experience/expertise statements, and Qualifications are the preferred/experience in domains. However the instruction says "Prefer a few substantive sections over many thin ones." So maybe we just have About the role, Responsibilities, Requirements (covering both mandatory and preferred), and maybe Benefits/Pay/Schedule if present. We have Pay: "Retribuzione annua lorda (RAL): da € 35.057 a € 57.475". That's specific pay range. So we need a Pay section. We have Schedule: "Location: Bologna, Milano, Torino e Roma – modalità di lavoro ibrida." Also "Tipo di contratto: contratto a tempo indeterminato." That's schedule? Actually schedule refers to work arrangement (hybrid). So we can put Schedule section with location and hybrid work. Benefits: The posting includes "PERCHÉ TI PIACERÀ LAVORARE CON NOI" which lists benefits: flexible work arrangements, career growth, social responsibility, inclusive environment, opportunity to work on cutting-edge projects. That's benefits. So we need Benefits section. Thus we have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly Qualifications and Skills could be omitted if we incorporate into Requirements. But we have separate lists for mandatory and preferred; we could treat Requirements as mandatory, Qualifications as preferred, and Skills maybe not needed. But we have to avoid empty headings. We could put Skills as empty? Not allowed. So we need to decide to include Skills with some content, maybe summarizing technical skills from both lists (programming languages, frameworks, tools). But we must not invent or summarize away detail; we can list them as they appear. Could extract technical skills: Python, Java, C++, TypeScript; experience with agentic frameworks; cloud platforms; AI-assisted dev tools; Vector DB, Knowledge Graph; etc. That's still from the lists, not invented. So we can create Skills section with those items. Thus we will have: - About the role: intro paragraphs. - Responsibilities: list of items from "In Particolare Ti Occuperai Di". - Requirements: mandatory competencies list (Hai Probabilmente Molte Delle Seguenti Competenze). - Qualifications: preferred qualifications list (Costituiscono Titolo Preferenziale). - Skills: technical skills list (maybe combine programming languages, frameworks, tools). But we risk duplication. However we can still include; it's not invented. It's okay if some overlap. - Benefits: list from "PERCHÉ TI PIACERÀ LAVORARE CON NOI". - Pay: the salary range. - Schedule: location and hybrid work, contract type. We must not include boilerplate like EEO, legal, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the final paragraphs about Capgemini description, "Make it real | www.capgemini.com", "Candidati ora!", EEO statements, data protection, etc. Also remove "Location: Bologna, Milano, Torino e Roma – modalità di lavoro ibrida. Tipo di contratto: contratto a tempo indeterminato. Inquadramento: CCNL Commercio 1° livello Mansione: Senior Software Engineer". That's schedule info; we keep location and hybrid, contract type maybe part of schedule. We must not repeat the job title as a heading. The job title is "Agentic AI Engineer – AI Native Software Engineering". We must not use that as heading. We must not put Job ID/requisition numbers as headings; none present. Now produce HTML fragment: only the HTML, no or . Use

  for each section heading. Use

  • for lists. Use

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we must keep the exact wording? We can keep the substance but we can rephrase slightly? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can keep them as is. We can copy sentences. Let's extract each piece. About the role: Combine the introductory paragraphs and the "IL TUO RUOLO" paragraph. Original Italian: "In Capgemini Engineering, leader mondiale nei servizi di ingegneria, uniamo un team globale di talenti dell’ingegneria, scienza e tecnologia per aiutare le aziende più innovative del mondo a liberare il loro potenziale. Dai veicoli autonomi ai robot salva-vita, le nostre persone esperte in tecnologia digitale e software pensano fuori dagli schemi, offrendo servizi unici di ricerca e sviluppo e ingegneria in tutti i settori. Unisciti a noi per una carriera ricca di opportunità, dove potrai fare la differenza, in un ambiente in cui ogni giorno è unico. IL TUO RUOLO Come Agentic AI Engineer – AI Native Software Engineering entrerai a far parte del nostro Software Engineering Center of Excellence. Lavorerai alla progettazione e allo sviluppo di piattaforme e framework basati su Generative AI, Multi-Agent Systems e tecnologie emergenti per creare capacità autonome applicate all'intero Software Development Lifecycle. Immagina di utilizzare l'AI non solo per scrivere codice, ma per contribuire alla progettazione della prossima generazione di veicoli, satelliti, sistemi di difesa, dispositivi medicali e prodotti industriali intelligenti. Questo è il tipo di sfida che ti aspetta, sarai protagonista della trasformazione verso un modello di AI-Native Engineering in cui agenti intelligenti e professionisti collaborano per accelerare la progettazione, lo sviluppo e la validazione di software, sistemi embedded e prodotti complessi." We'll put that in

    maybe two paragraphs. Responsibilities: list items from "In Particolare Ti Occuperai Di". Let's extract each line: - Applicare tecnologie Agentic AI e Generative AI ai processi di sviluppo di sistemi embedded, prodotti cyber-fisici e piattaforme software-intensive in diversi domini industrial; - Collaborare con esperti di dominio provenienti da Automotive, Aerospace, Defence, Railway, Manufacturing e Life Sciences per creare nuovi modelli di AI-Augmented Engineering; - Progettare e sviluppare sistemi agentici distribuiti e architetture Multi-Agent per supportare l'intero ciclo di vita del software; - Realizzare framework di orchestrazione intelligente capaci di coordinare agenti, strumenti, dati e workflow complessi; - Integrare Large Language Models, Generative AI e Reasoning Systems all'interno di processi di sviluppo, testing e DevOps; - Realizzare capability autonome per requirements analysis, software design, code generation, testing, quality assurance e deployment; - Sperimentare nuove tecniche di Agentic AI, AI-Augmented Engineering e Autonomous Software Development; - Collaborare con architetti, sviluppatori, domain expert, data scientist e stakeholder di business per industrializzare nuove soluzioni; - Contribuire alla creazione di acceleratori, asset riutilizzabili e piattaforme enterprise destinati a essere adottati da clienti globali; - Partecipare a iniziative di innovazione, ricerca applicata e pre-sales contribuendo alla definizione della visione futura dell'AI-N