Data pipeline and reliability for a student performance platform

Problem

A custom platform tracks every student's coaching, classroom, and community activity for the partners who support them. It depends on data flowing from the CRM, the community platform, and call attendance, and on those flows staying reliable while the product is redesigned.

What I built

• The write-back path from the platform to the community and CRM moved from a scheduled job that took a median of 21 minutes to an event-driven function that runs in seconds, and a backfill that reconciled 700+ member records the old job had never updated.
• In-app team moves with a drain job that keeps the community in sync, verified on real moves before release.
• Alerts that tag the right partner automatically when a student's renewal is near, with a fallback to the partner group when nobody is assigned.
• Reliability work: diagnosed and stopgapped a database connection-pool exhaustion, planned the durable fix, and standardized how deadlines are computed so tasks land on the right day in the right time zone.

Result

Faster, verified data everywhere the team looks, and a platform that stays healthy while its front end is rebuilt.

What it shows

Backend and data reliability in a product that other people are actively changing.