Billing data everyone could trust.

The challenge

eDarling ran a subscription business where billing and payments sat at the heart of the company. The systems behind them had to be correct, auditable, and fast enough to keep up with the product, while finance, product, and analytics all depended on the same underlying data being right.

What I did

I started as a senior database developer and grew into the team lead for billing, leading a small group of database and backend engineers. We built and ran the billing and payment system for the subscription business, with the business logic in a PostgreSQL cluster and ETL feeding the analytics side. Much of the work was communication: translating the needs of finance, product, and business analytics into systems that produced numbers everyone could trust.

Outcomes

• Delivered a billing and payment system the subscription business ran on.
• Gave finance and analytics consistent, trustworthy numbers to work from.
• Led a small engineering team and owned the domain end to end.
• Bridged business and engineering on one of the company's most sensitive systems.