MC-4934

**Outlook Message ID:** `AAkALgAAAAAAHYQDEapmEc2byACqAC-EWg0A79prnwa9QEuY4jHjnpAstQAFI5GGLwAA` **Open in Outlook:** https://outlook.office365.com/owa/?ItemID=AAkALgAAAAAAHYQDEapmEc2byACqAC%2FEWg0A79prnwa9QEuY4jHjnpAstQAFI5GGLwAA&exvsurl=1&viewmodel=ReadMessageItem **From:** Pieter Richards <prichards@safair.co.za> **To:** Elmar Conradie **Subject:** FW: Hilary Smit - Machine Learning Engineer **Received:** 2026-06-10 15:40 SAST **Attachments:** Yes (organigram — see path below) --- **Body:** Pieter: "Hi kan jy asb approve – dis nie met my bespreek nie. Ons het AI engineers goedgekeur weet ek." Thread (Charity Brown, Senior Manager: Talent): IT requested a Machine Learning (ML) Engineer vacancy within Steven's team (organigram attached). Requesting approval from Pieter's side before HR actions it. Motivation (from Rohini): org expanding data-driven decision-making; ML Engineer needed to move from descriptive analytics to predictive/prescriptive — forecasting, optimisation, risk management, operational efficiency; bridges data science and business ops. This is an INTERNAL candidate placement — currently a Junior Data Analyst. Note (Erina Grobler): flagged that the prior approval trail shows AI Engineer approval from Pieter, NOT ML Engineer — and Pieter previously stated IT shouldn't add additional vacancies. So there is an ML-vs-AI-Engineer discrepancy to resolve before approving. --- **Action required:** APPROVE (or decline) the ML Engineer vacancy. Pieter has forwarded for Elmar's call since it wasn't discussed with him. Watch-out: confirm whether this is the same headcount as the already-approved AI Engineer, or an additional vacancy (Erina + Pieter both flagged that distinction). Review the attached organigram before deciding. *** **Correct me:** open this ticket in MC and use the Life Manager feedback buttons (Not important / Noisy sender / Noisy subject / Always surface / Wrong class / Done), or Telegram Luci: 'ignore like MC-XXXX', 'always surface MC-XXXX', 'noisy sender MC-XXXX', 'noisy subject MC-XXXX', or 'wrong MC-XXXX'. Rules write to ~/workspace/data/life-manager/config.yaml; safety keywords (safety/incident/urgent/safair/casa/sacaa/legal/d4h/etc.) block silence rules unless --force.