Kruthik Gowda’s Working Atlas

The interactive workbench needs JavaScript. You can still read all the work or open the engineering brief.

ATLAS / company

Shared platforms at Setu

About 7 product teams; a ~15-person platform group; technical guidance to 4 engineers.

I joined Setu full time in May 2026 after a Procedure client engagement. Within an approximately 15-person platform group, I contribute to Bridge and Admin capabilities shared by about seven product teams, and provide day-to-day technical guidance to four engineers.

My contribution: I work across architecture, implementation, code review, and cross-team delivery, 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 capabilities: Bridge is Setu’s customer dashboard and Admin its internal onboarding platform. Together, they provide capabilities and integrations used across product teams.

Open the full story →

Labs

Setting the atlas on the workbench…

FIELD DRAWING01 / 05

Concept diagram · a guide to the work, not a production topology.

My contribution

I work across architecture, implementation, code review, and cross-team delivery, 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.

Setu · Senior Software Developer · May 2026–present

Shared platforms at Setu

Capabilities product teams can build on.

Inside the work / 01

Bridge is Setu’s customer dashboard and Admin its internal onboarding platform. Together, they provide capabilities and integrations used across product teams.

Read the company story Open in the atlas

HOW THE WORK CHANGED

The work kept
widening.

Procedure and then Setu shaped my employee roles. Alongside them, I built products with my co-founders, growing from customer workflows into whole products.

01
PROCEDURE · 2022–2026
Ship the feature. Stay for production.
I moved from SDE-1 to SDE-2, carrying features from requirements and technical design through release and production support. Earlier fintech work included an account-aggregator dashboard.
Explore the experience
02
SETU · PLATFORM ENGINEERING
Make one capability useful to many teams.
I joined Setu full time in May 2026 after a client engagement while at Procedure. I now work on shared Bridge and Admin capabilities used by about seven product teams and guide four engineers day to day.
Inside the platform work
03
IN PARALLEL · KETRIUM LABS · CO-FOUNDER · 2024–PRESENT
Build the product, end to end.
With my co-founders, I take NeuralEye, CiteTrail and ClickTrail across interfaces, APIs, asynchronous workflows, and production operations.
Explore the products

LEARNING IN PUBLIC

Change one thing.
Watch the system respond.

OPEN SOURCE · CONTRIBUTION + TOOLS

Contributions and developer tools

One merged contribution and two public tools for inspecting and controlling automated workflows.

INTERACTIVE LABS · TEACHING MODELS

Explore every systems lab

Change one system choice and watch queues, retries, caches, and other trade-offs respond in a small, inspectable model.

NEURALEYE / INFERENCE SERVING

Test the batching trade-off

Group synthetic requests, bound their wait, then compare throughput with queue time. The model connects to my NeuralEye experience without claiming to reproduce its production system.

OFF THE CLOCK

Still curious
about how things work.

A little more about me

Doraemon’s gadgets made invention feel playful; Satisfactory lets me build and tune a whole factory. I still love systems that click together—and a good football match.

Opening the field notes

Finding the right page.

The workbench is getting this part of the atlas ready.

Skip to selected work

Kruthik Gowda’s Working Atlas

The interactive workbench needs JavaScript. You can still read all the work or open the engineering brief.

ATLAS / company

Shared platforms at Setu

About 7 product teams; a ~15-person platform group; technical guidance to 4 engineers.

Shared capabilities: Bridge is Setu’s customer dashboard and Admin its internal onboarding platform. Together, they provide capabilities and integrations used across product teams.

Open the full story →

Labs

Setting the atlas on the workbench…

FIELD DRAWING01 / 05

Concept diagram · a guide to the work, not a production topology.

My contribution

Setu · Senior Software Developer · May 2026–present

Shared platforms at Setu

Capabilities product teams can build on.

Inside the work / 01

Bridge is Setu’s customer dashboard and Admin its internal onboarding platform. Together, they provide capabilities and integrations used across product teams.

Read the company story Open in the atlas

HOW THE WORK CHANGED

The work kept
widening.

Procedure and then Setu shaped my employee roles. Alongside them, I built products with my co-founders, growing from customer workflows into whole products.

01
PROCEDURE · 2022–2026
Ship the feature. Stay for production.
I moved from SDE-1 to SDE-2, carrying features from requirements and technical design through release and production support. Earlier fintech work included an account-aggregator dashboard.
Explore the experience
02
SETU · PLATFORM ENGINEERING
Make one capability useful to many teams.
I joined Setu full time in May 2026 after a client engagement while at Procedure. I now work on shared Bridge and Admin capabilities used by about seven product teams and guide four engineers day to day.
Inside the platform work
03
IN PARALLEL · KETRIUM LABS · CO-FOUNDER · 2024–PRESENT
Build the product, end to end.
With my co-founders, I take NeuralEye, CiteTrail and ClickTrail across interfaces, APIs, asynchronous workflows, and production operations.
Explore the products

LEARNING IN PUBLIC

Change one thing.
Watch the system respond.

OPEN SOURCE · CONTRIBUTION + TOOLS

Still curious
about how things work.

A little more about me

Doraemon’s gadgets made invention feel playful; Satisfactory lets me build and tune a whole factory. I still love systems that click together—and a good football match.

Kruthik Gowda’s Working Atlas

Shared platforms at Setu

The decisions
behind the work.

Shared platforms at Setu

The work kept
widening.

Ship the feature. Stay for production.

Make one capability useful to many teams.

Build the product, end to end.

Change one thing.
Watch the system respond.

Contributions and developer tools

Explore every systems lab

Test the batching trade-off

Still curious
about how things work.

A little more about me

Kruthik Gowda’s Working Atlas

Shared platforms at Setu

The decisions
behind the work.

Shared platforms at Setu

The work kept
widening.

Ship the feature. Stay for production.

Make one capability useful to many teams.

Build the product, end to end.

Change one thing.
Watch the system respond.

Contributions and developer tools

Explore every systems lab

Test the batching trade-off

Still curious
about how things work.

A little more about me

Kruthik Gowda’s Working Atlas

Shared platforms at Setu

Shared platforms at Setu

The work keptwidening.

Ship the feature. Stay for production.

Make one capability useful to many teams.

Build the product, end to end.

Change one thing.Watch the system respond.

Contributions and developer tools →

Explore every systems lab

Test the batching trade-off →

Still curiousabout how things work.

A little more about me →

Kruthik Gowda’s Working Atlas

Shared platforms at Setu

Shared platforms at Setu

The work keptwidening.

Ship the feature. Stay for production.

Make one capability useful to many teams.

Build the product, end to end.

Change one thing.Watch the system respond.

Contributions and developer tools →

Explore every systems lab

Test the batching trade-off →

Still curiousabout how things work.

A little more about me →

The work kept
widening.

Change one thing.
Watch the system respond.

Contributions and developer tools

Test the batching trade-off

Still curious
about how things work.

A little more about me

The work kept
widening.

Change one thing.
Watch the system respond.

Contributions and developer tools

Test the batching trade-off

Still curious
about how things work.

A little more about me