Engineering the systems behind enterprise bill payments

Paymentus runs the bill-payments platform for US utility providers - a multi-tenant, multi-state system where billing schemas vary by every customer.

Scaling the business meant unifying that complexity without breaking any single tenant.

I owned system design for multi-tenant enterprise products - APIs, data models, and integration layers - for customers including Cisco and Kitopi.

I partnered directly with enterprise customers on scoping and rollouts, which became my bridge into product management.

Designed integration systems that scaled the US utility-payments business across multiple states.

Unified disparate billing schemas into one ingestion pipeline so new tenants could onboard without bespoke plumbing.

Scaled the utility-payments business across multiple states on a unified ingestion pipeline.

Built the customer-facing scoping muscle that defined the move from engineering into product.

Owning system design taught me to reason about trade-offs at the data-model level - depth I now bring to PM work.

The bridge into product wasn’t a title change; it was being the engineer in the room with the customer.