Mechanical graduate to backend engineer
A year of applications with no callbacks after a mechanical engineering degree. Sixteen weeks on the Java track, a deployed capstone, then three interviews in one week.
Placement percentages are easy to inflate by choosing a flattering base. Here is how ours are calculated, followed by the people behind the numbers.
How we count. The denominator is every candidate who completed certification in the reporting period, including those who later declined offers or stopped responding. We do not exclude "not placement eligible" candidates, and we do not count an internship or an unpaid trial as a placement. Candidates who withdrew before certification are reported separately in the counselling call. Figures on this page are placeholders for design review.
Cloud and DevOps takes longer because employers expect some prior IT exposure. Business Analysis depends heavily on the domain experience a candidate brings.
| Track | Certified | Placed in 6 months | Median days to offer | Retention at 12 months |
|---|---|---|---|---|
| Full-Stack Java | 1,420 | 94% | 32 | 90% |
| Data Engineering | 980 | 93% | 35 | 91% |
| QA & Test Automation | 1,105 | 95% | 27 | 86% |
| Cloud & DevOps | 640 | 86% | 49 | 92% |
| Business Analysis | 655 | 88% | 44 | 88% |
Placeholder profiles written to show the range we work with. Replace with consented candidate stories and photographs.
A year of applications with no callbacks after a mechanical engineering degree. Sixteen weeks on the Java track, a deployed capstone, then three interviews in one week.
Five years reconciling transactions manually. Already understood the data better than most applicants; needed SQL depth, Python, and a pipeline she could point at.
Returned after a career break with an older tech background. The weekend batch fit around family, and the mock rounds rebuilt the interview confidence that had gone.
Three years on a service desk with a ceiling in sight. Linux fundamentals were already there, so the twelve weeks went into Terraform, Kubernetes, and pipeline design.
Six years of store operations translated directly into requirements work. The gap was documentation discipline, SQL, and learning to run a stakeholder conversation.
Cleared certification but lost the first four interviews on communication rather than code. Re-entered the cycle at no cost, took the communication clinic, and converted the sixth.
No stories published for this track yet. Try another filter, or ask us for references from that cohort.
“We needed eleven data engineers in a quarter and our own funnel could not deliver it. They ran a cohort on our stack. Nine of the eleven are still on the team two years later.”
“The scorecard is the part I value. I can see where a candidate is weak before the interview, so the panel spends its time on the right questions instead of discovering it live.”
“Two hires didn't work out in the first year. Both were replaced without an argument and without an invoice. That's the reason we're still working with them.”
Roughly one in twelve certified candidates is not placed within six months. The reasons cluster into three groups, and we handle each differently rather than quietly dropping the candidate from the report.
Included, not sold. If the first cycle ends without an offer you re-enter with:
A second cycle costs you nothing extra. The 10% only ever applies once you're actually placed, so the delay costs you time rather than money.