
What a capstone should prove: how every Obrix course ends.
Obrix Academy
03 October, 2026
00 Comments
A certificate says you attended. A capstone says you can build. That is why every Engineering course at Obrix ends with a project the student has to stand behind in front of people who will ask hard questions about it.
The brief is realistic rather than academic. On Full-Stack Web Development it might be a clinic appointment and records system or a multi-vendor inventory and orders platform. On Python Backend Development it could be a microfinance loan management API. On Mobile App Development it could be a field data collection app that works offline in rural areas.
The standard every capstone has to meet
Whatever the domain, the bar is the same, and it is written down before the course starts:
- It runs from a clean clone, with no hidden setup on the author's machine.
- Its tests pass in CI.
- It is deployed and reachable at a working URL.
- The README explains the architecture and the trade-offs behind it.
- The commit history shows work built up step by step, not pasted in at the end.
- The student can defend every design decision under technical questioning.
“A capstone has to run from a clean clone, pass its tests in CI, sit at a live URL, and be defended by the student under questioning.”
Proof builds every week, not just at the end
The capstone is the last step, not the only one. On Engineering courses each week ends with a merged pull request, a working increment and a three-minute demo. Students review each other's code throughout, and code review participation counts towards the grade.
On most Engineering courses the grade splits like this:
| Component | Weight | What it rewards |
|---|---|---|
| Weekly labs and mini-projects | 30% | Steady progress |
| Code review participation | 20% | Giving and taking feedback |
| Capstone | 35% | A finished, deployable project |
| Demo Day presentation and questioning | 15% | Explaining your work under pressure |
A few courses adjust the weights slightly; each course page lists its own.
Demo Day and the employability sprint
The final session is Demo Day, held with hiring partners and alumni. Each student gives a five-minute live demo and then answers technical questions. Design students deliver a portfolio pitch instead.
On Engineering courses the last two weeks also run an employability sprint covering the portfolio and README, the resume, a mock technical interview and professional communication, so the project turns into something a hiring manager can actually read.
Why it matters
Employers hire people who can show finished work and explain it. A project that runs, ships and survives questioning does that better than a list of topics covered. If you are choosing a course, read its capstone requirements first: they describe exactly what you will be able to show at the end.
Leave a comment