You Are the Engineer

The situation

Code Nexus wants a safe multilingual creator-support feature for its next launch. There is no ticket and no runbook for this exact thing. The engineering recommendation, and whether it ships, are yours.

What you'll learn

• Owning an engineering recommendation end to end: clarifying a brief into constraints, gaps and assumptions; building and testing a safe core; securing and staging a release through the gates; diagnosing an unfamiliar fault; and defending a release decision language by language with evidence, a tested rollback and an operational handover.
• The 16-item programme checkpoint reinforces build and release concepts; its score and coverage do not certify AZ-400 readiness or predict an exam result.

Who you work with

• 

  Maya Chen

  Senior AI Engineer · Your mentor

• 

  Kabelo Mokoena

  Platform and DevOps Engineer

• 

  Amara Okafor

  ML and Data Engineer

• 

  Lydia Roe

  Security Engineer

• 

  Priya Naidoo

  Cloud Architect

• 

  Jax Rivera

  Creator Partnerships Lead

• 

  Leo Martins

  Product Manager

• 8-BIT

  Code Nexus Internal AI Assistant

Scenes

1. 1.Your name is on this one
2. 2.What is the request actually asking?
3. 3.Build the triage core
4. 4.Secure it, stage it
5. 5.The fault nobody planted on purpose
6. 6.Release, or don't: defend it
7. 7.AZ-400 readiness gate and final review

What you leave with

You developed a recommendation from an open brief: constraints, questions and assumptions; the ordered keyword-triage exercise; synthetic release gates; routing diagnosis; and a per-language decision with recovery and handover. The triage code has limited keyword coverage and the evaluation thresholds are fixture rules. The final checkpoint checks authored concepts, not external exam equivalence or production readiness.