About Me

I'm Rawal Suthar. I build backend systems for fintech-style products, the kind where a small bug becomes a real customer problem very quickly. That's why I bias toward clear architecture, boring reliability, and shipping changes that we can actually support.

A lot of the work I enjoy is the stuff most people never see: workflows that move money, identity checks, queues, background jobs, and systems that talk to isolated environments. When those flows break, everyone feels it, and fixing them teaches you what good engineering really means.

Over the last few years, I've built production APIs for building society apps, led a project that connected a mobile app to a locked-down RPA environment, and owned end-to-end delivery (frontend, backend, and DevOps) for a client release. I'm comfortable being the person who connects the dots when multiple teams are involved.

I'm not a big-document person, but I do write things down. For most work, I start with a short note that answers: what are we building, what can go wrong, and how will we know it's working in production?

• clear API contracts (so clients don't guess)
• scalability decisions that are explained, not hidden
• logs/metrics that make incidents faster to solve
• post-release reports that turn pain into prevention

I've learned that this is what keeps a system alive when the team grows, traffic grows, or requirements change.

Even though backend is my core, I always look at how mobile/web actually consume the APIs. It changes the design, and it usually prevents the classic it-works-on-my-machine surprise later.

Clarity over cleverness. If someone can't read your code during an incident, it's not clever, it's a liability.

Reliability over more features. I'd rather ship fewer things that hold up than lots of things that fail under real traffic.

Planning over heroics. I like being calm during incidents, not dramatic. Good architecture (and good monitoring) saves more time than midnight debugging.