Inherited codebase
Navigate a small unfamiliar repository and identify where a reported issue lives.
C2I programs are modular. A cohort may need engineering execution, data reasoning, AI judgement, cloud thinking, interview calibration — or only some of them.
For students targeting software engineering and full-stack/backend roles.
Navigate a small unfamiliar repository and identify where a reported issue lives.
Reproduce a defect, form a hypothesis, implement a fix and add evidence that it works.
Reason across HTTP, application logic and persistence instead of solving isolated snippets.
For analyst, BI and entry-level data roles where business reasoning matters as much as tooling.
Clean, join and interrogate imperfect datasets using SQL and analytical judgement.
Move from “make a dashboard” to “what actually happened, why, and what should we do?”
Choose the right visual, separate signal from noise and defend a recommendation.
Tools will change. The capability should not.
Students practise context-setting, decomposition, verification, code/data review, hallucination detection, privacy awareness and knowing when human judgement must override model output.
Tool names are examples of current industry workflows, not vendor endorsements or permanent curriculum anchors.
Go beyond “which service should I use?” toward reliability, cost, observability and deployment reasoning.
Understand environments, configuration, CI/CD basics and what changes between laptop and production.
Read logs, reason about failure, latency and simple capacity constraints.
Make trade-offs when the “best architecture” is not the best business decision.
Communicate architecture choices in language a technical interviewer can probe.
Interview readiness is treated as evidence under questioning — not just rehearsed answers.
Start with DayOne, identify the dominant gaps, then choose the smallest intervention likely to move the cohort.