RVM CAD
BACKEND LIVE / PILOT NEXTTeam RVM
RVM CAD’s employee self-service Android app: attendance with location, requests and approvals, an inbox, a staff wall, a helpdesk, documents, an ID card and My Team. Its backend has been live since 16 Oct 2026.
- ROLE
- Owner, lead and architect
- PERIOD
- Oct 2026 – present
- Attendance
- Requests & approvals
- Inbox
- Staff wall
- Helpdesk
- ID card
- 24
- production deploys, 16–27 Oct 2026, all green
- 2,727
- tests passing in CI
- 155
- operations in the API contract
- 21
- architecture decision records
WHAT THIS PROVES
This shows how I lead a build end to end without writing every line: I turned the brief into recorded product decisions and 21 architecture decision records, wrote the API contract, and built the backend, migrations and delivery pipeline, while our mobile developer builds the Flutter app against that contract.
- Contract-first API
- Decisions on record
- Gated delivery
System detail
WHAT I BUILT
- Product decisions and 21 architecture decision records, turned from the company’s brief.
- Contract-first API: one OpenAPI 3.1 file (130 paths, 155 operations), linted in CI, with 1,320 contract tests that check every reply against it.
- A separate Node and Express service with its own process and subdomain. It shares the Scheduler’s database and adds only its own tables; its writes to Scheduler data are limited to six sanctioned, audited cases.
- 36 additive migrations that never touch a Scheduler table, with rollback scripts for 34 of them; until a migration is applied, its endpoints answer a clear 503.
- A merge to main deploys behind an on/off switch once the tests and Nginx checks pass, and the deploy waits until the health check reports the new commit.
- I made the first commit; 76 of its 122 commits are mine, including every commit to the API contract and the database migrations.
STACK
- Node.js
- Express
- OpenAPI 3.1
- Postgres / Supabase
- GitHub Actions
- Nginx
- Flutter app (mobile developer)
Not yet rolled out to employees. Push notifications are built and write to the log until the company’s push-notification project is set up. Next, once RVM’s Google Play organisation account is approved: a closed-testing pilot with one branch for two weeks.