Self-directed project
AI-Assisted Code Modernization with IBM
Junior Software Engineer · Software Engineering · August 2026
Based on a public IBM case study · not affiliated with IBM
Built and verified a full legacy-service repair for a car-maintenance repo: fixed the wear calculation with true division, handled missing service readings safely, corrected the nightly report’s average, and preserved the 15,000 km / 80% rules. Also added the missing regression test, documented the review process in NOTES.md, and produced a data-driven breakdown-risk analysis that ranks cars by the factors the fleet history actually supports.
Graded against
- Fix and extend the repo with the agent35%
- Diagnose the bug20%
- Direct and audit the AI agent25%
- Explain it like an engineer20%
Passed · pass mark 60/100
What stood out6
- Correctly identified the floor-division bug on the wear line and explained why it produced 0% for a nearly worn car.
- Caught the agent’s planted mistakes: reintroduced rounding, changed the threshold, and omitted a proving test.
- Wrote NOTES.md with concrete verification steps and a clear explanation of what the data actually showed.
- Built an analysis that follows the dataset instead of the tempting but wrong mileage/age narrative.
- Leakage-Free Bug Diagnosis
- Bounded AI Prompting and Review
The deliverable
The work I submitted18 tasks
10 tasks · 1.7k characters · Python · 8 written answers · 163 words
- Diagnose Line130 characters
- Diagnose Why82 characters
- Scope Prompt66 characters
- Audit Findings158 characters
- Audit Why190 characters
- Acceptance ChecklistPython · 233 characters
- Bob Ready60 characters
- Exec Pitch507 characters
- Bob Bonus223 characters
- Repo URL64 characters
- Diagnose Line10 words
- Diagnose Why16 words
- Scope Prompt1 word
- Audit Findings1 word
- Audit Why25 words
- Acceptance Checklist37 words
- Bob Ready1 word
- Exec Pitch72 words
Summarised on purpose — the submitted code and writing stay private so this page cannot be reused as an answer key. The full submission sits behind the verified certificate.