Ewance
← All challenges MLOps Engineer

Build an MLOps Platform Slice for a Fintech Risk Team

Duration
6 weeks
Level
Expert
Type
Code
Team
1 to 5 people

The situation

The fintech (around 250 staff, around 5 models in production across credit and fraud) has been losing 3 to 5 engineer-weeks per quarter to bespoke deploys; a v0 platform that compresses that to days is the team's stated OKR.

Your task

Ship a v0 MLOps platform slice (tracking, registry, training pipeline, monitoring) for a fintech risk team's next model deployment.

The brief

What you do

  1. Across a 5-person team, ship (1) experiment tracking integrated into a sample model training job; (2) a model registry that promotes-by-tag; (3) a training pipeline orchestrated by a workflow tool (Prefect / Dagster / Argo); (4) a monitoring dashboard for one deployed model showing input drift and a target accuracy proxy; (5) a runbook describing the daily and weekly operations.
  2. Use a sample fraud-detection model on a public dataset as the test customer.
  3. Deploy to a small cloud sandbox.
  4. CI gates merges.
  5. Produce a 6-page architecture document plus a 30-minute risk-team handover.

What you will practice

  • Architect a small but real MLOps platform across multiple components
  • Operate an experiment-tracking + model-registry workflow end-to-end
  • Implement input-drift and accuracy-proxy monitoring
  • Hand a platform off to a domain team with a usable runbook

A suggested way in

  1. MLflow + Prefect is a low-friction combo for the v0; document the why
  2. Drift detection: start with a Population Stability Index on top features
  3. Runbook beats README — write what operators do at 9 AM Monday

Skills you will practice

Mlops design, Experiment tracking, Model registry, Monitoring, CI CD, Team collaboration

Where it leads

MLOps Engineer, Machine Learning Engineer, AI Solutions Architect

How it is assessed

  • Platform completeness30%

    All five components work and connect cleanly.

  • Monitoring rigor25%

    Drift and accuracy-proxy metrics are sound and dashboards are readable.

  • Handover quality25%

    Risk team can run the platform from the runbook unsupervised.

  • Team engineering20%

    Git history shows code review, CI, branching discipline.

Resources

  • PythonTool

    Glue across pipeline, registry, monitoring.

  • MLflowTool

    Battle-tested experiment tracking + model registry.

  • PrefectTool

    Orchestrate the training pipeline.

  • StreamlitTool

    Quick monitoring dashboard.

  • GitHubTool

    Pull requests, CI, and code review hygiene.

  • NotionTool

    Author the runbook and architecture document.

  • LinearTool

    Track the 6-week capstone backlog and ownership.

Sample Ewance certificate of completion, verified by LearnCoin
Sample certificate
Your proof

Finish it. Earn this.

A verified certificate with your name. Anyone can check it.

Time to practice.

Solve this challenge
Related challenges

More like this.