CSC-210 case studies
CSC-210 · Put your knowledge to work in context.
CSC-210 is a software engineering certification exam whose blueprint spans the full development lifecycle rather than a single language or tool. It is aimed at practitioners who already write code and now need to reason about process: how requirements become designs, how designs become tested and versioned artifacts, and how projects are planned and delivered responsibly. The CSC-210 case studies are 5 cases and about 5,943 words.
1The Word Real-Time in a Clinical Scheduling Contract
Meridian Health Partners has contracted a 14-person vendor to build an appointment-scheduling module for three hospitals and 40 outpatient clinics staffed by 900 clinicians. The pilot must go live in 11 weeks, and the contract ties 15% of the vendor fee to that milestone.
1,142 words, about 6 min2The Two-Quarter Microservices Mandate
Cartwheel Retail runs order management on a 900,000-line Java monolith deployed to four application servers. Twenty-two engineers in six teams ship once a week through a four-hour Saturday window; the median change lead time is 19 days, and two releases were rolled back last quarter.
1,299 words, about 6 min3The 82% Coverage That Ships Bugs
Ledgerly is a B2B invoicing SaaS with 31 engineers on a single monorepo. CI runs 1,400 unit tests and 210 integration tests in 52 minutes; the quality gate requires 80% line coverage, and the build sits at 82%.
1,128 words, about 6 min4Adding Four Contractors to a Late Payroll Replacement
A 16-week project to replace a payroll engine for a 4,000-employee client is at the end of week 10. The plan had eight integration points with the client's HR, timekeeping, and banking systems; three have not been started because the client's middleware vendor delivered its API documentation five weeks late.
1,172 words, about 6 min5The Debug Log That Recorded Session Tokens
Vaultly is a five-year-old payments-adjacent startup processing card-on-file transactions for 1,200 small merchants. On a Tuesday, a contractor investigating log volume discovers that for 23 days the production API gateway has written full request headers - including the Authorization bearer token and the customer's full bank account number on a legacy ACH endpoint - to a third-party log-analytics SaaS at DEBUG level.
1,202 words, about 6 min