New opportunity

Engineer Artificial Intelligence Application

Academy Sports · Katy, United States of America

About this role

Build AI agents, copilots and assistant experiences for Academy Sports using Microsoft Copilot Studio, Azure AI Studio, Power Platform and related Microsoft tools. This full-time role is based at Headquarters in Katy, Texas, requires regular office attendance and has a 40-hour workweek.

Responsibilities

  • Design agent instructions, conversation flows, prompts, knowledge grounding, actions and escalation paths. Configure approved sources including SharePoint, Dataverse, SQL, ServiceNow, internal documents and enterprise data.
  • Work with business stakeholders to turn use cases into prototypes. Test agents for accuracy, completeness, hallucination risk, usability and business fit; improve them through prompt refinement, knowledge tuning, evaluation frameworks and user feedback.
  • Run pilots and iterate toward production readiness. Turn successful prototypes into reusable templates, starter prompts and build patterns, and document configurations, data sources, limitations, support models and adoption guidance.

Required qualifications

  • Bachelor’s degree in Computer Science, Information Technology, Data, Engineering or a related field, or equivalent practical experience; at least 4 years in AI solution development, automation, application development, data platforms or enterprise technology.
  • Hands-on experience building AI agents, copilots, chatbots, workflow automations or advanced digital assistants; experience with Microsoft Copilot Studio, Power Automate, Power Apps, SharePoint, Teams, Dataverse or Azure AI. Ability to translate business needs into practical solutions, design and test grounded agent experiences, and solve problems in ambiguous environments.

Preferred qualifications include relevant Microsoft certifications; training or practical experience in prompt design, AI evaluation, knowledge grounding or responsible AI; experience building internal tools for business teams or working in retail or multi-site enterprises; and familiarity with RAG, Azure OpenAI, Microsoft Graph, APIs, enterprise search, AI safety, access controls and data privacy.

For full details about this role, click “Apply on company site” to view the employer’s original posting.

Skills for this role

AI agentsMicrosoft Copilot StudioAzure AI StudioPower PlatformPower AutomatePower AppsSharePointMicrosoft TeamsDataverseSQLServiceNowPrompt designKnowledge groundingConversation designAI evaluationRetrieval-Augmented GenerationAzure OpenAIMicrosoft GraphAPIsEnterprise searchAI safetyAccess controlsData privacyStakeholder collaboration

Your skill match

Checking your profile…

YOUR NEXT STEP

Get interview-ready for this role

A focused preparation guide, built around this job’s responsibilities and requirements.

✦ AI-generated guide
Preparation suggestions, not the employer’s actual interview questions. Always check the original posting for current requirements.
01

Understand the role

What matters most

  • Build Microsoft-based AI assistants

    The role builds agents, copilots and assistant experiences using Copilot Studio, Azure AI Studio, Power Platform, SharePoint, Teams and related tools.

  • Design grounded agent behavior

    Responsibilities include instructions, conversation flows, prompts, actions and escalation paths, with grounding in approved sources such as SharePoint, Dataverse, SQL, ServiceNow and internal documents.

  • Turn business needs into prototypes

    The engineer works directly with stakeholders to clarify requirements and convert use cases into working AI solutions.

  • Evaluate and improve agent quality

    The posting calls for testing accuracy, completeness, hallucination risk, usability and business fit, then refining prompts and knowledge using evaluation frameworks and user feedback.

  • Move pilots toward reusable production patterns

    The role supports pilots, iterates toward production readiness, packages successful work into templates and build patterns, and documents limitations, data sources, support models and adoption guidance.

Likely challenges to think through

  • Balancing useful answers with source boundaries

    Likely preparation challenge, not a stated employer problem: drawing on several enterprise sources may improve coverage while making grounding and access boundaries harder to manage. Prepare to explain how you would select approved sources, check answer provenance and handle information an agent should not provide.

  • Balancing fast pilots with dependable behavior

    Likely preparation challenge: rapid iteration can conflict with the testing needed before wider use. Prepare a concrete approach for evaluating representative tasks, hallucinations and escalation behavior, then using feedback to decide what needs refinement.

  • Reusing patterns without flattening business needs

    Likely preparation challenge: templates can speed delivery, but different teams may need different actions, sources and support guidance. Prepare to distinguish what you would standardize from what you would tailor after clarifying a stakeholder’s use case.

03

Practice your answers

Technical practice

How would you choose the Microsoft tools for an internal AI assistant?

What to coverThe role involves Copilot Studio, Azure AI Studio, Power Platform, SharePoint and Teams. Suggested preparation: explain how the use case, data sources and required actions would shape your choice of tools, without assuming every assistant needs every tool.

How would you design an agent’s instructions and conversation flow?

What to coverThe posting calls for agent instructions, prompts, conversation flows and escalation paths. Suggested preparation: describe how you would define the agent’s scope, handle unclear requests and decide when to escalate rather than answer.

How would you connect an agent to approved enterprise knowledge?

What to coverThe role names SharePoint, Dataverse, SQL, ServiceNow and internal documents as potential approved sources. Suggested preparation: discuss source selection, content quality and how you would verify that answers reflect the right information.

When would a retrieval-augmented generation pattern help?

What to coverFamiliarity with RAG and enterprise search is preferred in the posting. Suggested preparation: explain how retrieval can ground an answer in relevant content, and where poor retrieval or outdated content could still produce a misleading response.

How would you design an agent action and its escalation path?

What to coverThe role includes designing actions and escalation paths for agents. Suggested preparation: distinguish answering a question from taking an action, and explain how you would handle missing information, an unsuccessful action or a request outside the agent’s scope.

How would you evaluate a prototype before a pilot?

What to coverThe posting specifies accuracy, completeness, hallucination risk, usability and business fit as testing concerns. Suggested preparation: outline representative test cases, what you would record for each concern and how the results would inform a pilot decision.

How would you diagnose an agent that gives incomplete or unsupported answers?

What to coverThe role calls for improvement through prompt refinement, knowledge tuning, evaluation frameworks and user feedback. Suggested preparation: explain how you would isolate whether the problem lies in the instructions, retrieved knowledge or the use case, then retest the change.

How would you account for access controls and data privacy?

What to coverAI safety, access controls and data privacy are listed as preferred areas of familiarity. Suggested preparation: discuss how you would check that an agent uses approved sources and does not expose information beyond a user’s permitted access.

How would you move a stakeholder use case from prototype to production readiness?

What to coverThe role involves clarifying requirements, building prototypes, supporting pilots and iterating toward production readiness. Suggested preparation: describe how you would narrow the initial use case, gather pilot feedback and decide what still needs improvement.

What would you preserve when turning a successful prototype into a reusable pattern?

What to coverThe posting calls for templates, starter prompts and build patterns, plus documentation of configuration, sources, limitations, support and adoption guidance. Suggested preparation: explain what another team would need to reuse the approach safely and where customization would remain necessary.

Behavioural practice

Tell me about a time you clarified an ambiguous business request.

What to coverSuggested preparation: use a real situation, your actions with stakeholders and the resulting shared understanding or prototype scope. This is relevant to the role’s responsibility for turning business use cases into practical solutions.

Describe a time user feedback changed a solution you were building.

What to coverSuggested preparation: give the situation, how you collected and weighed feedback, what you changed and the result. The posting emphasizes pilots, user feedback and iteration.

Tell me about a time you raised a quality or safety concern before a release.

What to coverSuggested preparation: describe the issue, how you communicated its impact, the action you took and the outcome. Keep the example grounded in your own experience; the role calls for attention to agent accuracy, hallucination risk and business fit.

Describe a time you worked through uncertainty in a fast-moving project.

What to coverSuggested preparation: explain the situation, how you set priorities or tested assumptions and what resulted. The posting explicitly values problem-solving in ambiguous environments.

Tell me about a time you made a solution easier for others to adopt or support.

What to coverSuggested preparation: give a real situation, the documentation or reusable guidance you created and its result. This connects to the role’s emphasis on reusable patterns, known limitations, support models and adoption guidance.

02

Sharpen your knowledge

Topics to prepare

  • Agent behavior and escalation

    The posting calls for agent instructions, conversation flows, actions, and escalation paths. Revision exercise: map a sample internal-support request from user question through action or escalation, and explain where instructions constrain the agent’s response.

  • Knowledge grounding

    The role involves configuring approved sources including SharePoint, Dataverse, SQL, ServiceNow, and internal documents. Revision exercise: explain how an agent should handle a question when its approved sources are incomplete or conflicting. RAG and enterprise search are listed as preferred familiarity, not required tools.

  • Agent evaluation

    The posting specifies accuracy, completeness, hallucination risk, usability, and business fit. Revision exercise: define a small set of test questions, expected grounded answers, and failure criteria for each measure.

  • Pilot and production readiness

    The role supports pilots and documents limitations, support models, and adoption guidance. Revision exercise: outline what evidence and documentation you would review before advancing a sample prototype beyond a pilot. This is preparation, not a stated company approval process.

Skills to revise

  • Build a Microsoft-based agent prototype

    The role builds assistants with Microsoft Copilot Studio, Azure AI Studio, Power Platform, SharePoint, and Teams. Practice creating a small sample agent with instructions, a conversation path, and an escalation response; be ready to explain your configuration choices.

  • Configure an approved knowledge source

    The posting explicitly calls for configuring approved enterprise sources. Practice connecting a permitted sample source, then check whether answers stay within its content. Use sample data rather than assuming access to Academy systems.

  • Test and refine responses

    The role improves agents through prompt refinement, knowledge tuning, evaluation frameworks, and user feedback. Run a short test set against a sample agent, record inaccurate or unsupported answers, make one change, and compare results.

  • Turn a business use case into a documented prototype

    The posting calls for stakeholder collaboration, working prototypes, and reusable build patterns. Practice turning a hypothetical business request into a concise use-case definition, prototype plan, starter prompt, and notes on data sources and known limitations.

04

Your preparation checklist

  • Map your evidence to the role

    Prepare a one-page evidence sheet with specific examples of agent or automation builds, Microsoft tools used, and work with business users. The posting asks for hands-on experience and 4+ years in relevant technology work; note where you would need to explain an equivalent experience path.

  • Prepare an agent project walkthrough

    Select a project you can discuss and outline the user need, your design decisions, tools, knowledge sources, actions, escalation path, testing, and what changed after feedback. Distinguish your own contributions from the team’s.

  • Sketch a grounded assistant

    Practice a design exercise using a hypothetical internal IT or store-team request—not an asserted Academy project. Produce a simple conversation flow showing instructions, approved-source retrieval, an action, a fallback, and human escalation using relevant Microsoft tools.

  • Explain source access and safety choices

    Prepare a short diagram or notes on how you would select approved sources such as SharePoint, Dataverse, SQL, or ServiceNow, respect access controls and data privacy, and handle missing or conflicting information. These sources and concerns appear in the posting.

  • Build a compact evaluation plan

    Draft sample test questions, expected grounded answers, and checks for accuracy, completeness, hallucination risk, usability, and business fit. Show how prompt changes, knowledge tuning, and user feedback would inform a second test round.

  • Outline a pilot-to-production handoff

    Prepare a sample pilot plan with feedback collection and a handoff checklist covering configuration, data sources, known limitations, support model, adoption guidance, and reusable prompts or templates—all deliverables named in the posting.

  • Bring targeted employer questions

    Write questions about initial business use cases, which knowledge sources are approved, how pilots are evaluated, and who owns support after launch. Ask how regular office attendance at the Katy headquarters works in practice.

AI-generated from the job information · Prepared Sep 30, 2026 (UTC)Useful preparation, not a guarantee of eligibility or an offer.

Availability last checked: Nov 4, 2026. Status can change after a check; confirm on the employer’s website. Report an issue · Our checking policy

KEEP EXPLORING

Similar AI jobs

Related skills and specializations in United States of America. Matched to this role, not your profile.

Explore more jobs
Finding similar opportunities…