New opportunity

Machine Learning Engineer

Crowe Advisory LLC · Chicago, United States of America

About this role

As a member of Crowe’s AI Engineering team, the Machine Learning Engineer advances AI features and solutions from proof of concept to production. The role focuses on making solutions robust, scalable and aligned with business objectives.

Responsibilities

  • Execute the technical vision for AI solutions and deliver scalable, production-ready features.
  • Refine user stories and define acceptance criteria that reflect business needs.
  • Write production-ready code, assist with code reviews, and develop testing protocols, including smoke and unit tests.
  • Support debugging and issue triage throughout development. Participate in ethical reviews and risk and security evaluations for responsible AI deployment.

Required skills:

  • Expertise in Python and experience with version control systems such as Git.
  • Ability to work independently, navigate ambiguity and use iterative testing to refine solutions.
  • Strong communication skills, including documenting and presenting technical details to nontechnical stakeholders.

Preferred skills and background:

  • Ability to align technical outputs with business requirements; knowledge of prompt engineering and retrieval-augmented generation (RAG).
  • Experience with ChatGPT Enterprise, Microsoft Copilot, Azure AI Foundry or fine-tuning large language models.
  • Experience in professional services or a similar industry.

The position is full-time at 40 hours per week. The estimated salary range is $62,000–$100,000 per year, before any applicable geographic adjustment. Crowe offers a comprehensive total rewards package and career coaching. Applicants hired must verify eligibility to work in the United States; Crowe is not sponsoring work authorization at this time. Applications are accepted on an ongoing basis.

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

Skills for this role

PythonGitAI solution developmentUnit testingSmoke testingDebuggingCode reviewPrompt engineeringRetrieval-augmented generation (RAG)ChatGPT EnterpriseMicrosoft CopilotAzure AI FoundryLarge language model fine-tuningTechnical documentationCommunication

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

  • Move AI solutions into production

    The posting centers on advancing proofs of concept into robust, scalable, production-ready features. Prepare to explain how you would assess readiness and improve a solution before release.

  • Translate business needs into acceptance criteria

    The role refines user stories and defines clear acceptance criteria for feature requests. Prepare an example of turning an ambiguous request into observable outcomes.

  • Build and maintain reliable code

    The role calls for production-ready Python code, code reviews, smoke and unit tests, debugging, and issue triage. Prepare to describe how these practices work together across development.

  • Support responsible AI deployment

    The engineer participates in ethical reviews and risk and security evaluations. Prepare to explain how you would identify a concern, document it, and bring it into a deployment decision.

  • Communicate technical decisions clearly

    The posting requires documenting and presenting technical details to nontechnical stakeholders. Prepare a concise explanation of an AI feature’s purpose, limitations, and business relevance.

Likely challenges to think through

  • Resolving ambiguity without losing momentum

    A likely difficulty is deciding what to build when a feature request is underspecified, while still working independently and iterating efficiently. Prepare a framework for clarifying the business need, recording assumptions, and testing an initial approach.

  • Balancing AI experimentation with release confidence

    Moving a proof of concept into production may require trading rapid iteration against reliability and scale. Prepare to discuss what smoke and unit tests can establish, what needs further validation, and how you would triage a failure.

  • Weighing usefulness against deployment risk

    An AI feature may satisfy its acceptance criteria yet raise ethical, security, or other risk concerns; this is a preparation hypothesis, not a stated Crowe problem. Prepare to explain how you would surface the trade-off and seek a reviewed decision rather than silently proceeding.

03

Practice your answers

Technical practice

How would you move an AI proof of concept toward production readiness?

What to coverSuggested answer focus: Explain how you would assess reliability, scalability, maintainability and alignment with the business objective before expanding use. Describe the trade-off between improving a promising prototype and narrowing its scope to deliver a dependable feature.

How would you turn an AI feature request into a user story and acceptance criteria?

What to coverSuggested answer focus: Clarify the user's need and the business outcome, then define observable criteria for success and failure. Explain how you would resolve an ambiguous request before implementation.

What makes Python code for an AI feature production-ready?

What to coverSuggested answer focus: Discuss clear interfaces, error handling and maintainable structure, alongside a Git workflow that makes changes reviewable. Explain what you would examine when assisting with a code review.

How would you design unit and smoke tests for an AI feature?

What to coverSuggested answer focus: Distinguish unit tests for isolated behavior from smoke tests that check whether a deployed feature's essential path works. Address how to test predictable components while handling variability in AI outputs.

How would you triage an AI feature that starts producing incorrect results?

What to coverSuggested answer focus: Describe how you would reproduce the issue, assess its impact, isolate the failing component and check recent changes. Explain how iterative testing would confirm a fix without introducing a regression.

What would you examine in an ethical, risk and security review of an AI feature?

What to coverSuggested answer focus: Consider inappropriate outputs, sensitive information, access controls and potential harm in the feature's intended use. Explain how you would document a risk and weigh mitigation against deployment readiness.

How would you evaluate changes to a prompt?

What to coverSuggested answer focus: Compare outputs against representative requests and the feature's acceptance criteria rather than relying on a few favorable examples. Discuss trade-offs such as consistency, usefulness and the effort needed to maintain the prompt; prompt engineering is a preferred skill in the posting.

How would you assess whether retrieval-augmented generation fits an AI feature?

What to coverSuggested answer focus: Explain what retrieving source material could add and how you would evaluate whether the retrieved material supports the answer. Discuss failure cases such as irrelevant retrieval or an answer that goes beyond its sources; RAG knowledge is preferred, not listed as required.

When might you consider LLM fine-tuning instead of prompt changes or RAG?

What to coverSuggested answer focus: Compare the approaches in terms of the behavior needed, available examples, evaluation effort and maintenance. Frame this as a decision method rather than assuming the role uses a fine-tuned model; fine-tuning experience is preferred.

How would you evaluate an AI tool for a business feature?

What to coverSuggested answer focus: Define the feature's requirements, then compare candidate tools on suitability, integration effort, risk and ability to meet acceptance criteria. ChatGPT Enterprise, Microsoft Copilot and Azure AI Foundry appear as preferred experience in the posting; do not assume any one is used for every solution.

Behavioural practice

Tell me about a time you made progress on an ambiguous technical task while working independently.

What to coverSuggested answer focus: Use a real situation, your actions to clarify priorities and test assumptions, and the result. Connect the example to the role's stated need for independent work and iterative refinement without claiming a particular Crowe process.

Describe a time you explained a technical decision to a nontechnical stakeholder.

What to coverSuggested answer focus: Give the situation, how you documented or presented the options in terms of the stakeholder's business need, and the result. Make clear how you checked that the decision and its limitations were understood.

Tell me about a time a code review improved a solution.

What to coverSuggested answer focus: Describe the situation, the feedback you gave or received, what changed and the result. Emphasize how the interaction improved code quality while keeping the work collaborative.

Describe a time you raised an ethical, risk or security concern about a technical solution.

What to coverSuggested answer focus: State the situation, the concern, how you communicated or investigated it, and the result. Show how you balanced delivery with responsible deployment and integrity, both of which are reflected in the posting.

02

Sharpen your knowledge

Topics to prepare

  • Proof of concept to production

    The role advances AI features to robust, scalable, production-ready solutions. Revise by listing what would need to change in a hypothetical proof of concept before release, and how you would check each change.

  • Business alignment and acceptance criteria

    The posting calls for refining user stories and defining acceptance criteria that reflect business needs. Revise by turning a vague AI feature request into a user story with observable acceptance criteria and questions to resolve ambiguity.

  • Testing and issue-triage strategy

    Smoke tests, unit tests, debugging and issue triage are stated responsibilities. Revise by deciding which failures each test type should catch and how you would prioritize a reported defect.

  • Responsible AI deployment

    The role participates in ethical reviews and risk and security evaluations. Revise by drafting review questions for a hypothetical AI feature, including potential harms, security concerns and evidence needed before release.

  • Prompt engineering and RAG

    These are preferred knowledge areas, not required skills. As optional preparation, explain when retrieval-augmented generation might help a prompt-based solution and how you would check whether retrieved material supports an answer.

Skills to revise

  • Production-quality Python and Git

    Python expertise and version-control experience are required; production-ready code and code reviews are responsibilities. Practice improving a small Python feature for readability and error handling, commit the changes in Git, and write a brief review rationale.

  • Unit and smoke test implementation

    The posting explicitly calls for both test types. Practice writing unit tests for a Python function and a smoke test for its basic end-to-end behavior; explain what each test does not cover.

  • Debugging and iterative refinement

    Debugging, issue triage and iterative testing appear in the posting. Practice reproducing a failing case, narrowing its cause, testing a fix and recording the remaining uncertainty.

  • Technical communication for nontechnical stakeholders

    Documenting and presenting technical details to nontechnical stakeholders is required. Practice writing a short update that explains a feature’s purpose, test results, unresolved risks and a decision needed, without relying on specialist terminology.

04

Your preparation checklist

  • Outline a proof-of-concept-to-production walkthrough

    Prepare a concise example showing how an AI feature could become robust, scalable, and aligned with a business objective. The role explicitly focuses on that transition; distinguish work you actually did from decisions you would propose.

  • Practice refining a feature request

    Draft a sample user story with measurable acceptance criteria and note the business questions you would clarify. Refining stories to reflect business needs is a stated responsibility.

  • Prepare Python and Git evidence

    Select a code example you can explain, including version-control decisions and a code-review improvement. Python expertise, Git experience, production-ready code, and review participation are named in the posting.

  • Work through a reliability scenario

    Sketch unit and smoke tests for your sample feature, then explain how you would reproduce, triage, and debug a failure. Testing and issue triage are stated responsibilities.

  • Draft a responsible-AI review

    For the same sample feature, list plausible ethical, security, and deployment risks, plus questions needing review. The role participates in ethical reviews and risk/security evaluations; this is a preparation exercise, not a claim about Crowe’s review process.

  • Prepare an optional AI-technique comparison

    If relevant to your experience, compare prompting, RAG, and fine-tuning against a stated business need; discuss any listed tools only if you have used them. These techniques and tools are preferred, not required.

  • Rehearse a nontechnical explanation

    Create a brief written summary and spoken explanation of your example’s purpose, trade-offs, tests, and limitations. Documenting and presenting technical details to nontechnical stakeholders is required.

  • Write targeted questions for Crowe

    Bring questions about how the AI Engineering team prioritizes business needs, defines production readiness, and handles ambiguous requirements and responsible-AI reviews. These are questions to ask, not assumptions about its processes.

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…