SETU · PLATFORM ENGINEERING · MAY 2026—NOW
Shared onboarding for product teams.
Bridge is Setu’s customer dashboard; Admin supports internal onboarding. I contribute to capabilities shared across product teams, including work on a centralized know-your-customer (KYC) transition flow that consolidated fragmented product-specific journeys so participating products could consume verified customer identity.
- Shared reach
- About 7 teams
- Platform group
- About 15 people
- Day-to-day guidance
- 4 engineers
THE REPORTED CHANGE
From separate journeys to one KYC transition.
- 01
Separate product journeys
Before this shared transition, each product followed its own KYC journey.
- 02
Centralized KYC flow
The shared flow brought those journeys together and enabled participating products to consume verified customer identity.
- 03
Boundary to consider
Which KYC steps belong in the shared flow, and which should stay product-specific?
Where I contributed
My work spans delivery ownership, reusable platform pieces, engineering workflows, and partner configuration.
- 01
Own delivery through production
I take complex initiatives from requirements and technical planning through implementation, review, release, and production support, coordinating product, design, backend, QA, and infrastructure.
- 02
Build for reuse
I’ve built reusable packages and component abstractions, and worked on dependency, bundle, build, and CI/CD improvements.
- 03
Make a repository easier to work in
Across multiple repositories, I added architecture decision records, engineering rules, structured context, planning conventions, and repository guides so engineers and coding assistants can understand the project before changing it.
- 04
Adapt for enterprise partners
I design white-label configuration so partner-specific needs can vary without requiring a separate version of the shared core.
Explore the platform trade-offs
Try a separate synthetic exercise about shared capabilities, local extension points, and the coordination that comes with platform changes. It is a general design lesson, not a model of Setu’s implementation.
Continue the story
Follow the path from fintech product delivery into shared platform engineering.