Sr AI Solutions Engineer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must include sections only when posting has real specific content. So we can have sections: About the role? Actually Overview includes What We Do, Who We Are, Why You Should Join Us. Could combine into "About the company" maybe. But we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings if appropriate. We need to map content.
We have Job Summary (description of role). Could map to "About the role". Responsibilities we have. Qualifications we have. Skills maybe part of Qualifications. Benefits we have. Pay we have min/max. Schedule not mentioned, so omit.
We should not create empty sections.
Thus output:
About the role
Job Summary ...
Responsibilities
- ...
...
Qualifications
- ...
...
Maybe also Skills
but we can incorporate into Qualifications; but we could separate if we have specific skills list. The qualifications list includes many skills; we could keep as Qualifications.
Benefits: from Why You Should Join Us: total rewards package, 401k, medical insurance, free therapy visits, mental health coaching and tools, meditation resources, generous paid time off including vacation, care time, Wellness and Volunteer Time Off days.
We'll make Benefits section with .
Pay: Min USD $122,500.00/Yr. Max USD $159,170.00/Yr. We'll put in maybe.
We must not include fluff like "commensurate with experience". Not present.
We must not include duplicated lines.
We need to preserve all substantive information. So we need to include the overview paragraphs about CNXN Helix Center, Who We Are, Why You Should Join Us (benefits). Also Job Summary.
We must not include the fraud warning.
Let's craft.
First, About the role: combine Overview, What We Do, Who We Are, Why You Should Join Us? Actually Why You Should Join Us is benefits; but we could put that in Benefits section. About the role could include What We Do, Who We Are, Job Summary.
We'll put:
About the role
CNXN Helix Center at Connection Inc. is at the forefront of AI innovation, offering cutting‑edge solutions that redefine the boundaries of artificial intelligence and data management. The team is dedicated to helping clients navigate AI integration and stay ahead in a rapidly evolving technological landscape. Connection’s team is made stronger by a multitude of backgrounds, experiences, and perspectives, driving innovation and technology solutions that stand apart. The company values supportive teammates, a rewarding career, and a total rewards package that includes progressive compensation, 401k plans, medical insurance, free therapy visits, mental health coaching and tools, meditation resources, and a generous paid time off package (vacation, care time, Wellness and Volunteer Time Off days).
Help shape the future of enterprise AI by designing, building, and delivering production‑ready AI applications, copilots, and intelligent agents on the Microsoft AI platform. As a Senior AI Solutions Engineer you will serve as a hands‑on technical leader for advanced AI solutions, partnering with customers and internal stakeholders to translate business needs into scalable, secure, and production‑grade AI applications, copilots, and agents. You will guide engagements from discovery and architecture through implementation, deployment, evaluation, governance, and ongoing production support, working across the modern Microsoft AI ecosystem (Microsoft Foundry, Foundry Agent Service, Microsoft Fabric, Copilot Studio, Microsoft 365 Copilot, Agent Builder, Microsoft 365 Agents SDK, Power Platform, Azure services, GitHub Copilot capabilities). The ideal candidate combines deep technical expertise with strong communication skills, sound architectural judgment, and a passion for helping teams adopt responsible, reliable, and cost‑effective AI solutions. Applicants must be authorized to work for any employer in the U.S.; Connection cannot sponsor or take over sponsorship of an employment visa at this time.
That seems to cover overview and job summary.
Now Responsibilities: list each bullet from Responsibilities section.
We need to preserve all substantive information; we can break into multiple - items.
Let's extract bullet points:
- Lead technical discovery sessions with customers and stakeholders to understand business goals, user needs, data requirements, security considerations, operational expectations, and budget parameters.
- Design, architect, and build production-grade AI applications, copilots, agents, and appropriately scoped multi-agent solutions.
- Recommend and implement the right mix of low-code, pro-code, or hybrid approaches across Microsoft AI, Azure, Fabric, Copilot Studio, Power Platform, and Microsoft 365 technologies.
- Build Microsoft 365 agents and extensibility solutions using Agent Builder, Copilot Studio, Microsoft 365 Agents SDK and Agents Toolkit, Microsoft Graph, SharePoint, connectors, plugins, and supported Copilot extensibility patterns.
- Develop custom and hosted agents using Microsoft Foundry and Foundry Agent Service, with application backends built in Python and/or C#/.NET.
- Design grounding, retrieval, and enterprise data solutions using Microsoft Fabric, Azure AI Search, vector search, embeddings, Microsoft Graph, SharePoint, Dataverse, and structured or unstructured data sources.
- Implement secure Azure architectures using services such as Functions, Container Apps, API Management, Service Bus, Storage, Cosmos DB, Azure SQL, Key Vault, and Application Insights.
- Build tools, APIs, connectors, workflows, and integrations using secure REST, event-driven, MCP, and supported agent-interoperability patterns.
- Apply enterprise-grade identity, security, governance, data protection, auditability, Responsible AI, and compliance controls.
- Design automated testing and evaluation approaches for grounding, answer quality, hallucination risk, task completion, tool use, safety, security, and regression behavior.
- Implement monitoring and observability for agent behavior, latency, reliability, failures, business outcomes, model usage, Azure consumption, and Copilot credits.
- Estimate and optimize solution consumption and operating costs, clearly communicating tradeoffs and implementing guardrails where appropriate.
- Establish CI/CD, infrastructure-as-code, testing, code review, and reusable engineering practices using GitHub, GitHub Actions, Azure DevOps, and GitHub Copilot capabilities.
- Lead technical workshops, demonstrations, prototypes, implementation sessions, production handoffs, and troubleshooting efforts.
- Mentor engineers and delivery team members while contributing reusable reference architectures, standards, templates, and accelerators.
We'll put each as
- .
Qualifications: list bullet points.
Extract:
- Bachelor’s degree in Computer Science, Information Systems, Software Engineering, Artificial Intelligence, Data Science, a related technical field, or an equivalent combination of education and work experience.
- Minimum of 6 years of professional experience in software, cloud, data, application, solution, or AI engineering, including recent hands-on delivery of production AI applications or agents.
- At least 4–6 years of applied AI or generative AI experience, with strong evidence of designing, coding, integrating, testing, deploying, and supporting production GenAI or agentic solutions.
- Experience leading complex customer or stakeholder engagements while remaining hands-on throughout implementation.
- Practical experience with relevant Microsoft technologies such as Microsoft Foundry, Foundry Agent Service, Copilot Studio, Microsoft Fabric, Microsoft 365 Copilot, Agent Builder, Microsoft 365 Agents SDK or Agents Toolkit, Agent 365, Azure AI Search, Power Platform, and Microsoft Graph.
- Strong software engineering skills using Python and/or C#/.NET, APIs, authentication and authorization patterns, automated testing, source control, and CI/CD.
- Experience designing Azure application and integration architectures using compute, API, messaging, storage, database, identity, secret-management, and observability services.
- Knowledge of enterprise grounding and RAG patterns using search, embeddings, vector retrieval, structured data, documents, semantic models, and permission-aware data sources.
- Experience with AI and agent evaluation, tracing, monitoring, safety controls, governance, production support, and consumption optimization.
- Strong written and verbal communication skills, with the ability to explain architecture, risk, delivery, and cost tradeoffs to both technical and nontechnical audiences.
- Ability to mentor engineers, influence cross-functional teams, and promote reusable technical practices without requiring direct people-management responsibility.
Preferred Experience: we could make a section "Preferred Experience" but not in the list of headings given; but we could still include as a section maybe "Preferred Experience". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those as examples. Safer to include only those headings if we have content. Preferred Experience could go under Skills or Qualifications. But we could add a section "Skills" and put preferred experience there. However we already have Qualifications covering required; we could add a separate "Skills" section for preferred experience. Let's do that.
Thus:
Skills
- Current, relevant Microsoft certifications or Applied Skills in Azure AI, Microsoft Fabric, Copilot Studio, Power Platform, Microsoft 365 agent development, or related technologies.
- GitHub Copilot certification or demonstrated practical experience using GitHub Copilot coding agents, custom agents, reusable instructions or skills, and MCP integrations in governed engineering environments.
- Experience building Microsoft 365 declarative or custom-engine agents and extending Microsoft 365 Copilot or Copilot Cowork through supported skills, plugins, connectors, or APIs.
- Experience making agents compatible with Microsoft Agent 365 governance, identity, observability, and security controls.
- Practical experience with multiple model providers, including Microsoft-hosted models, OpenAI, and Anthropic, and selecting models based on quality, safety, latency, availability, and cost.
Benefits: we already included some in About the role but we should separate Benefits section with specifics. However we already mentioned benefits in About the role; but we can still have a Benefits section to avoid duplication? The instruction says preserve ALL substantive information; not to duplicate? It didn't forbid duplication but better to avoid. We could keep benefits only in Benefits section and not repeat in About the role. But we already included benefits in About the role; we could remove them from there and keep only in Benefits. Let's adjust: In About the role we keep overview and job summary but not benefits details. Then Benefits section will have the list.
Thus rewrite About the role to exclude benefits details.
About the role paragraph:
- CNXN Helix Center at Connection Inc. is at the forefront of AI innovation, offering cutting‑edge solutions that redefine the boundaries of artificial intelligence and data management. We are dedicated to helping our clients navigate the complexities of AI integration, ensuring they stay ahead in a rapidly evolving technological landscape. Our commitment to excellence, innovation, and strategic growth makes us an industry leader.
- Our team is made
for prose. We must include sections only when posting has real specific content. So we can have sections: About the role? Actually Overview includes What We Do, Who We Are, Why You Should Join Us. Could combine into "About the company" maybe. But we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings if appropriate. We need to map content.
We have Job Summary (description of role). Could map to "About the role". Responsibilities we have. Qualifications we have. Skills maybe part of Qualifications. Benefits we have. Pay we have min/max. Schedule not mentioned, so omit.
We should not create empty sections.
Thus output:
About the role
Job Summary ...
Responsibilities
- ... ...
Qualifications
- ... ...
Skills
but we can incorporate into Qualifications; but we could separate if we have specific skills list. The qualifications list includes many skills; we could keep as Qualifications. Benefits: from Why You Should Join Us: total rewards package, 401k, medical insurance, free therapy visits, mental health coaching and tools, meditation resources, generous paid time off including vacation, care time, Wellness and Volunteer Time Off days. We'll make Benefits section with- .
Pay: Min USD $122,500.00/Yr. Max USD $159,170.00/Yr. We'll put in
- items. Let's extract bullet points: - Lead technical discovery sessions with customers and stakeholders to understand business goals, user needs, data requirements, security considerations, operational expectations, and budget parameters. - Design, architect, and build production-grade AI applications, copilots, agents, and appropriately scoped multi-agent solutions. - Recommend and implement the right mix of low-code, pro-code, or hybrid approaches across Microsoft AI, Azure, Fabric, Copilot Studio, Power Platform, and Microsoft 365 technologies. - Build Microsoft 365 agents and extensibility solutions using Agent Builder, Copilot Studio, Microsoft 365 Agents SDK and Agents Toolkit, Microsoft Graph, SharePoint, connectors, plugins, and supported Copilot extensibility patterns. - Develop custom and hosted agents using Microsoft Foundry and Foundry Agent Service, with application backends built in Python and/or C#/.NET. - Design grounding, retrieval, and enterprise data solutions using Microsoft Fabric, Azure AI Search, vector search, embeddings, Microsoft Graph, SharePoint, Dataverse, and structured or unstructured data sources. - Implement secure Azure architectures using services such as Functions, Container Apps, API Management, Service Bus, Storage, Cosmos DB, Azure SQL, Key Vault, and Application Insights. - Build tools, APIs, connectors, workflows, and integrations using secure REST, event-driven, MCP, and supported agent-interoperability patterns. - Apply enterprise-grade identity, security, governance, data protection, auditability, Responsible AI, and compliance controls. - Design automated testing and evaluation approaches for grounding, answer quality, hallucination risk, task completion, tool use, safety, security, and regression behavior. - Implement monitoring and observability for agent behavior, latency, reliability, failures, business outcomes, model usage, Azure consumption, and Copilot credits. - Estimate and optimize solution consumption and operating costs, clearly communicating tradeoffs and implementing guardrails where appropriate. - Establish CI/CD, infrastructure-as-code, testing, code review, and reusable engineering practices using GitHub, GitHub Actions, Azure DevOps, and GitHub Copilot capabilities. - Lead technical workshops, demonstrations, prototypes, implementation sessions, production handoffs, and troubleshooting efforts. - Mentor engineers and delivery team members while contributing reusable reference architectures, standards, templates, and accelerators. We'll put each as
- .
Qualifications: list bullet points.
Extract:
- Bachelor’s degree in Computer Science, Information Systems, Software Engineering, Artificial Intelligence, Data Science, a related technical field, or an equivalent combination of education and work experience.
- Minimum of 6 years of professional experience in software, cloud, data, application, solution, or AI engineering, including recent hands-on delivery of production AI applications or agents.
- At least 4–6 years of applied AI or generative AI experience, with strong evidence of designing, coding, integrating, testing, deploying, and supporting production GenAI or agentic solutions.
- Experience leading complex customer or stakeholder engagements while remaining hands-on throughout implementation.
- Practical experience with relevant Microsoft technologies such as Microsoft Foundry, Foundry Agent Service, Copilot Studio, Microsoft Fabric, Microsoft 365 Copilot, Agent Builder, Microsoft 365 Agents SDK or Agents Toolkit, Agent 365, Azure AI Search, Power Platform, and Microsoft Graph.
- Strong software engineering skills using Python and/or C#/.NET, APIs, authentication and authorization patterns, automated testing, source control, and CI/CD.
- Experience designing Azure application and integration architectures using compute, API, messaging, storage, database, identity, secret-management, and observability services.
- Knowledge of enterprise grounding and RAG patterns using search, embeddings, vector retrieval, structured data, documents, semantic models, and permission-aware data sources.
- Experience with AI and agent evaluation, tracing, monitoring, safety controls, governance, production support, and consumption optimization.
- Strong written and verbal communication skills, with the ability to explain architecture, risk, delivery, and cost tradeoffs to both technical and nontechnical audiences.
- Ability to mentor engineers, influence cross-functional teams, and promote reusable technical practices without requiring direct people-management responsibility.
Preferred Experience: we could make a section "Preferred Experience" but not in the list of headings given; but we could still include as a section maybe "Preferred Experience". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those as examples. Safer to include only those headings if we have content. Preferred Experience could go under Skills or Qualifications. But we could add a section "Skills" and put preferred experience there. However we already have Qualifications covering required; we could add a separate "Skills" section for preferred experience. Let's do that. Thus:
Skills
- Current, relevant Microsoft certifications or Applied Skills in Azure AI, Microsoft Fabric, Copilot Studio, Power Platform, Microsoft 365 agent development, or related technologies.
- GitHub Copilot certification or demonstrated practical experience using GitHub Copilot coding agents, custom agents, reusable instructions or skills, and MCP integrations in governed engineering environments.
- Experience building Microsoft 365 declarative or custom-engine agents and extending Microsoft 365 Copilot or Copilot Cowork through supported skills, plugins, connectors, or APIs.
- Experience making agents compatible with Microsoft Agent 365 governance, identity, observability, and security controls.
- Practical experience with multiple model providers, including Microsoft-hosted models, OpenAI, and Anthropic, and selecting models based on quality, safety, latency, availability, and cost.
maybe. We must not include fluff like "commensurate with experience". Not present. We must not include duplicated lines. We need to preserve all substantive information. So we need to include the overview paragraphs about CNXN Helix Center, Who We Are, Why You Should Join Us (benefits). Also Job Summary. We must not include the fraud warning. Let's craft. First, About the role: combine Overview, What We Do, Who We Are, Why You Should Join Us? Actually Why You Should Join Us is benefits; but we could put that in Benefits section. About the role could include What We Do, Who We Are, Job Summary. We'll put:
About the role
CNXN Helix Center at Connection Inc. is at the forefront of AI innovation, offering cutting‑edge solutions that redefine the boundaries of artificial intelligence and data management. The team is dedicated to helping clients navigate AI integration and stay ahead in a rapidly evolving technological landscape. Connection’s team is made stronger by a multitude of backgrounds, experiences, and perspectives, driving innovation and technology solutions that stand apart. The company values supportive teammates, a rewarding career, and a total rewards package that includes progressive compensation, 401k plans, medical insurance, free therapy visits, mental health coaching and tools, meditation resources, and a generous paid time off package (vacation, care time, Wellness and Volunteer Time Off days).
Help shape the future of enterprise AI by designing, building, and delivering production‑ready AI applications, copilots, and intelligent agents on the Microsoft AI platform. As a Senior AI Solutions Engineer you will serve as a hands‑on technical leader for advanced AI solutions, partnering with customers and internal stakeholders to translate business needs into scalable, secure, and production‑grade AI applications, copilots, and agents. You will guide engagements from discovery and architecture through implementation, deployment, evaluation, governance, and ongoing production support, working across the modern Microsoft AI ecosystem (Microsoft Foundry, Foundry Agent Service, Microsoft Fabric, Copilot Studio, Microsoft 365 Copilot, Agent Builder, Microsoft 365 Agents SDK, Power Platform, Azure services, GitHub Copilot capabilities). The ideal candidate combines deep technical expertise with strong communication skills, sound architectural judgment, and a passion for helping teams adopt responsible, reliable, and cost‑effective AI solutions. Applicants must be authorized to work for any employer in the U.S.; Connection cannot sponsor or take over sponsorship of an employment visa at this time.
That seems to cover overview and job summary. Now Responsibilities: list each bullet from Responsibilities section. We need to preserve all substantive information; we can break into multiple