CAPABILITY / 01

Backend & APIs

In production

Production backends with tested routes, versioned migrations and an API contract that gates the deploy.

Updated 15 Nov 2026

01 / PROOF

The measured part

116 → 692
API routes on the Scheduler, 30 Apr → 15 Nov 2026
Source
163
operations in the Team RVM API contract
Source
3,640
Scheduler backend tests passing in CI, 15 Nov 2026
Source

02 / WHAT I DO

In practice

Design the data model, routes and service layer, then keep them behind versioned migrations.
Write the API contract first and test every reply against it.
Put the test suite in front of the deploy so a red build never ships.
Own the production surface end to end.

03 / WHERE I'VE DONE IT

The systems behind it

RVM CAD SchedulerRe-architected the service layer and grew the API from 116 to 692 routes.Team RVMWrote the OpenAPI 3.1 contract, backend, migrations and delivery pipeline.RVM CAD Job PortalInterview recording state machine: not started → live → ended → processing → available, or not recorded after 24 hours.BadaBhaiOwns the main API service.RVM CADOwner, lead and architect of the four RVM platforms.

04 / STACK

What it runs on

TypeScript
Job Portal app and API
See the system
Node.js
Self-service API service
See the system
NestJS
Main API service
See the system
FastAPI
Research API and data services
See the system
PostgreSQL
Shared relational store
See the system
OpenAPI
OpenAPI 3.1 contract, 163 operations
See the system

05 / LIMITS

What this does not claim

No claim of large-scale traffic or a public SLA.

06 / RELATED CASE STUDIES

All work

Built and testedRVM CAD Job Portal and RVM CAD Scheduler

Both connectors are merged with full test suites. Production activation and the CEO acceptance test had not been verified when this was written (20 Oct 2026).

Doors, not keys: read-only AI access to production data

Two connectors that let an AI assistant answer operational questions from live systems — without a database credential, without write access, and without ever returning a half-right number.

11 read-only tools on the job portal connector

Built and testedBadaBhai

All three phases merged with tests in October 2026. Switching production to organisation tenancy is a controlled rollout step owned by the business; its current mode was not verified when this was written.

Multi-tenancy without a migration

Invited teammates on an employer account saw zero jobs, zero credits and zero candidates. The fix re-scoped fifteen business tables to the organisation — with no new column, no backfill and no change to the API.

15 business tables moved to organisation tenancy

Built and testedRVM CAD Job Portal

Merged with 616 of 616 tests passing at 48c3cab1 (23 Jun 2026). RVM approved describing the behaviour on 15 Nov 2026; production rollout state was not independently verified.

Interviews that schedule, record and file themselves

One interview, end to end in the Job Portal: a Google Meet space and invites, a consent gate before recording, a recording state machine, and Drive filing with metadata. Built in one commit, with 616 of 616 tests passing at that commit.

70 files in the feature commit

07 / QUESTIONS

Short answers

What backend work has KP done?

He has owned production backends for BadaBhai, the RVM CAD Job Portal, the Scheduler and Team RVM. On the Scheduler the API grew from 116 to 692 routes between 30 Apr and 15 Nov 2026, with 3,640 backend tests passing in CI.

Does he write the API contract?

Yes. Team RVM uses one OpenAPI 3.1 file with 137 paths and 163 operations, linted in CI, with 1,321 contract tests that check every reply against it.

Need this on a real system?

Hiring for a role, or scoping a short engagement? The Hire page has the role families and contact; Consulting has the scoped offers.

For hiring managers Consulting