Finish this page first, then move straight into the Aquaman kata to build a production-shaped solution using screaming architecture, onion architecture, unit tests, and integration tests.
Your first week is a discovery sprint and a capability assessment. We are assessing your ability to network across the company, ask the right questions, frame problems clearly, and show creativity in how you discover answers.
You have company email accounts and will be added to the company WhatsApp groups so you can quickly identify and contact the people you need during week one.
Treat this week like an easter egg hunt: every useful contact, system detail, and business constraint is a clue that helps you build the full picture.
"Whatever it takes." - Avengers: Endgame
"I can do this all day." - Captain America
Arrive with written questions, validate assumptions, and update docs the same day.
Focus on what improves delivery quality: clarity, risk reduction, and measurable impact.
Be calm, precise, and evidence-led. If you don’t know, say so and propose the next step.
By Friday, you should be able to explain what Engineers-OnCall does, how we deliver, and what "success" looks like for Siwe Group.
Your mission: collect the right clues, connect the dots, and present a clear story with evidence.
Company positioning and what good looks like.
Siwe Group context and stakeholder expectations.
Delivery workflow, tooling, architecture standards, and engineering best practices.
Security focus and control hygiene.
Human Capital support for onboarding and people-related questions.
Document what we do, how we deliver, and how we measure success. Keep it simple and enterprise-ready.
Capture goals, constraints, systems, risks, and priorities. Include a glossary and open questions list.
Every claim should have a source: interview note, system screenshot, config snippet, or a confirmed assumption.
Prepare questions, speak to people, write things down, and publish a cleaned-up version the same day.
09:00–10:00: prep and plan
10:00–11:00: interview + immediate write-up
11:00–13:00: convert notes into deliverables
14:00–16:00: self-research and gap closing
16:00–16:30: end-of-day log + next questions
Use short interviews to remove uncertainty. Bring questions. Take structured notes. Confirm assumptions.
Company positioning, standards, and what "good" looks like.
Siwe context, stakeholder expectations, and client success criteria.
Delivery workflow, tooling, architecture preferences, and engineering best practices.
Thursday guidance for security posture and controls.
For any Human Capital related questions, contact Veronica Mgiba.
Engineers On Call discovery
Interview Nkosinathi Mfeka. Draft the Engineers On Call one-pager and services map.
Siwe discovery
Interview Lebogang Machaba. Start the Siwe onboarding pack (goals, systems, risks, priorities).
Delivery expectations
Interview Kgang Moloke. Capture delivery workflow, tooling, operational standards, and engineering best practices.
Security posture and controls
Interview Sibonelo Maphumulo. Close gaps in security controls, hardening steps, and risk response readiness.
Finalize and present
Submit the final discovery pack and do a 10-minute internal readout with next steps.
Keep them concise, usable, and evidence-led.
Engineers On Call one-pager (who, what, how, success)
Services and delivery map (simple diagram)
Interview notes (Nkosinathi Mfeka, Lebogang Machaba, Kgang Moloke, Sibonelo Maphumulo)
Siwe onboarding pack v1 (systems, risks, priorities)
Glossary + open questions list
Next 30/60/90 day recommendations
Office Block B, Ground Floor, Capital Park, Central Lane, Riverglen, Johannesburg, Steyn City
support@engineers-oncall.co.za
+27 87 265 4965
Office Block B, Ground Floor, Capital Park, Central Lane, Riverglen, Johannesburg, Steyn City
© 2026 Engineers-OnCall - All rights reserved.