Copilot Developer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. The posting includes description (About the role), Responsibilities (Key Responsibilities), Qualifications (Required, Preferred, Required Certifications, Preferred Certifications). Also mentions "Success Measures" and "Ideal Candidate". Those could be part of Requirements or Qualifications? Probably we can treat "Qualifications" as required and preferred qualifications. "Skills" maybe from communication etc. But we need to avoid filler sections like Benefits, Pay, Schedule if not present. The posting does not mention benefits, pay, schedule. So we omit those sections. We need headings

for each section. Use

• for lists. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. We need to include sections: About the role, Responsibilities, Requirements, Qualifications, Skills? The posting includes "Qualifications Required" and "Preferred". Also "Required Certifications" and "Preferred Certifications". Also "Success Measures" and "Ideal Candidate". Could be part of Requirements or Qualifications. Let's decide: - About the role: first paragraph describing role. - Responsibilities: list under Key Responsibilities (with sub-bullets maybe). We'll flatten into

  • items. - Requirements: maybe combine required experience, certifications? But we have separate Qualifications. Could treat "Requirements" as required experience and skills, and "Qualifications" as certifications? However instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Requirements and Qualifications both if content. We need to decide what goes where. The posting has: - "Qualifications Required" bullet list (5+ years experience, hands-on experience, working knowledge, strong requirements-gathering, familiarity with generative AI concepts, excellent communication, must hold Microsoft associate-level certification). That's qualifications. - "Preferred" bullet list (experience in financial services, experience running structured POC, familiarity with broader M365, prior experience training citizen developers). That's also qualifications (preferred). - "Required Certifications" list (specific certs). That could be under Qualifications as well, but we could make a separate "Certifications" section but not in allowed headings. Since only allowed headings are those list, we could put certifications under Qualifications or Requirements. Probably Qualifications. - "Preferred Certifications" list (Power Platform Fundamentals, Agentic AI Business Solutions Architect). Also under Qualifications. - Then after that: "Strong understanding of Generative AI, Agentic AI, AI SDLC, cloud platforms, developer productivity tools, and enterprise architecture concepts. Experience working with cross-functional stakeholders including Engineering, Cyber, Risk, Compliance, and Legal. Strong analytical, communication and executive presentation skills. Preferred Experience with GitHub Copilot, Azure Foundry, Claude Code or similar enterprise AI solutions. Experience leading enterprise technology adoption and/or change management initiatives. Familiarity with AI governance frameworks, software development practices, cloud platforms." This seems like additional skills/experience. - Then "Preferred Certifications The following certifications are highly desirable: Project Management Professional (PMP) or equivalent. Generative AI Certification from Microsoft, AWS, Google, Databricks, or equivalent, covering LLMs, AI agents, retrieval-augmented generation (RAG), prompt engineering, enterprise AI architecture, security, and responsible AI." That's more preferred certifications. - Then "Success Measures Time-to-onboard new AI capabilities and use cases Growth in active AI users and platform adoption Productivity and efficiency gains achieved through AI Successful implementation of cyber, legal, compliance and risk requirements Demonstrated business value, cost savings, and ROI from AI investments". This could be under Requirements? Or maybe a separate section but not allowed. Could be part of Requirements (what they measure). But maybe we can incorporate into Qualifications? Not ideal. - Then "Ideal Candidate A technically credible project manager who can confidently engage with developers, architects, infrastructure teams, cybersecurity, control functions and senior executives. The successful candidate will combine project management, AI technology knowledge, stakeholder management, and change leadership to drive enterprise-scale adoption of AI". This is more description. We need to preserve all substantive info. We could create sections: About the role, Responsibilities, Requirements, Qualifications, Skills. For Skills we can include communication, analytical, presentation, stakeholder management, etc. For Requirements we can include experience years, hands-on experience, knowledge, etc. For Qualifications we can include certifications and preferred experience. But we must not invent or summarize away detail. We need to keep specifics like certification IDs (AB-610 etc). Must preserve them. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment. Let's structure:

    About the role

    Our client is seeking an AI Solutioning Consultant to join the AI Office Enablement group as an expert builder for the Microsoft Copilot Studio platform. This role combines hands-on, low-code build expertise with a consulting mindset, partnering directly with business stakeholders to scope, design, and deliver Copilot-based agents and proofs of concept. The individual will translate business problems into working agent solutions, guide business-based developers and teams through the art of the possible and help the AI Office scale adoption of the Microsoft Copilot platform across a governed, secure, and repeatable way.

    Responsibilities

    • Act as an expert on Microsoft Copilot Studio, advising business and technology partners on capabilities, limitations, and best practices for agent design.
    • Attend discovery sessions with business stakeholders to help scope use cases, gather requirements, and assess feasibility for Copilot-based solutions.
    • Design, build, and test low-code agents, topics, flows, and connectors in Copilot Studio, including grounding agents with enterprise knowledge sources.
    • Apply creative problem-solving to deliver effective agent solutions within approved access, functionality, and governance parameters.
    • Own delivery of Copilot Studio Agent end-to-end, from initial scoping through demo, stakeholder review and testing, through production and maintenance.
    • Build reusable templates, patterns, and playbooks to accelerate future Copilot Studio engagements.
    • Serve as a trusted advisor to business teams and the AI Office, helping them understand where Copilot Studio fits versus other build paths available.
    • Coach and upskill other Systems builders and business users on building their agents within approved guardrails.
    • Deliver clear, plain-language walkthroughs and documentation so non-technical stakeholders can evaluate and adopt Copilot Studio solutions with confidence.
    • Work directly from defined requirements to configure, iterate, troubleshoot, and refine Copilot Studio agents, escalating scope, timeline, or platform constraints as needed.
    • Ensure all Copilot Studio agents comply with AI Agent governance framework, data protection standards, and responsible AI principles throughout all stages of development.
    • Partner with Power Platform administrators, Copilot administrators, and governance teams on environment policies, security roles, and application lifecycle management.
    • Identify potential scope or platform limitations during build work and flag them to the team lead for review and escalation.
    • Stay current on relevant Copilot Studio and Power Platform features, licensing basics, and certification requirements that affect hands-on solution build work, and flag notable changes to the team lead.
    • Work with business teams to define success criteria and KPIs for each Copilot Studio use case.
    • Assist business team to track adoption, usage, and business impact of delivered agents, where appropriate.
    • Contribute to AI Office reporting and dashboards on Copilot pipeline status and outcomes.
    • Opine on which POCs should scale, be optimized, or be retired based on demonstrated value.
    Now Requirements: we could include required experience, hands-on experience, working knowledge, strong requirements-gathering, familiarity with generative AI concepts, excellent communication, must hold Microsoft associate-level certification. Let's list:

    Requirements

    • 5+ years of experience in a technical consulting, solutions engineering, business analyst, or low-code development role.
    • Hands-on experience building agents, bots, or workflows in Microsoft Copilot Studio (or Power Virtual Agents).
    • Working knowledge of the Microsoft Power Platform, including Power Automate and Dataverse.
    • Strong requirements-gathering and stakeholder management skills, with the ability to translate business needs into technical solutions.
    • Familiarity with generative AI concepts such as prompt engineering, retrieval-augmented generation (RAG), and grounding agents with enterprise data sources.
    • Excellent verbal and written communication skills, comfortable presenting to both technical and non-technical audiences.
    • Must hold a Microsoft associate-level (intermediate) certification in a related field.
    Qualifications: include preferred experience, preferred certifications, required certifications, plus other statements like strong understanding of Generative AI, cross-functional stakeholder experience, analytical skills, experience with GitHub Copilot, etc., experience leading enterprise technology adoption, familiarity with AI governance frameworks, etc., plus Success Measures and Ideal Candidate? Might be better to put those under Qualifications as they are additional desired attributes. But we need to avoid too thin sections. We'll combine all remaining specifics into Qualifications. Let's list:

    Qualifications

    • Preferred: Experience working in financial services, asset management, or another regulated industry.
    • Preferred: Experience running structured POC or pilot programs, including defining success criteria and reporting outcomes to leadership.
    • Preferred: Familiarity with the broader Microsoft 365 landscape, including how Copilot Studio agents can connect with Teams, SharePoint, OneDrive, Power Platform, Graph connectors, and enterprise knowledge sources.
    • Preferred: Prior experience training or supporting citizen developers.
    • Required Certifications: Candidates must hold one of the following Microsoft associate-level (intermediate) certifications and provide Credential ID numbers with their application:
      • Microsoft Certified: Copilot Studio Agent Maker Associate (AB-610)
      • Microsoft Certified: AI Agent Builder Associate (AB-620)
      • Microsoft Certified: Intelligent Applications Builder Associate (AB-410)
    • Preferred Certifications:
      • Microsoft Certified: Microsoft Power Platform Fundamentals (PL-900)
      • Microsoft Certified: Agentic AI Business Solutions Architect (AB-100)
    • Strong understanding of Generative AI, Agentic AI, AI SDLC, cloud platforms, developer productivity tools, and enterprise architecture concepts.
    • Experience working with cross-functional stakeholders including Engineering, Cyber, Risk, Compliance, and Legal.
    • Strong analytical, communication and executive presentation skills.
    • Preferred Experience with GitHub Copilot, Azure Foundry, Claude Code or similar enterprise AI solutions.
    • Experience leading enterprise technology adoption and/or change management initiatives.
    • Familiarity with AI governance frameworks, software development practices, cloud platforms.
    • Success Measures: Time-to-onboard new AI capabilities and use cases; Growth in active AI users and platform adoption; Productivity and efficiency gains achieved through AI; Successful implementation of cyber, legal, compliance and risk requirements; Demonstrated business value, cost savings, and ROI from AI investments.
    • Ideal Candidate: A technically credible project manager who can confidently engage with developers, architects, infrastructure teams, cybersecurity, control functions and senior executives. The successful candidate will combine project management, AI technology knowledge, stakeholder management, and change leadership to drive enterprise-scale adoption of AI.
    We need to ensure we didn't miss any content