Mock interview with Ujwalendu Prakash

I run engineering at an AI-native fintech. I've sat in 150+ interview loops for backend, platform and SRE roles, and I write the debrief that decides whether you get the offer.

This is that loop, run properly, with the debrief handed to you instead of to a hiring committee.

How the 60 minutes goes

• 5 min — your target: company, level, stack, what you're worried about
• 35 min — the design problem, run at real interview pace. I push back, change requirements mid-way, and ask the follow-ups a real panel asks. I won't go easy on you; that defeats the purpose
• 20 min — I walk you through my debrief live: where you lost the room, what a Staff-level answer would have added, what to say instead

What you get after

A written scorecard within 24 hours, in the format my company actually uses: signal-by-signal ratings, the specific moments that moved each rating, and the three things to fix before your next real loop.

Problems I run

Multi-region write path. Event pipeline with ordering and replay guarantees. Kubernetes platform for N teams. Rate limiter or idempotency layer at scale. Migrating a monolith without a freeze. Tell me your target company and I'll pick the one closest to their bar.

Book this if you're interviewing for Senior/Staff backend, platform, infra or SRE, and you've either been rejected after a design round or haven't done one in years.

Don't book this if you want an introduction to system design. This assumes you've run production systems. Take the ₹1,500 review instead — I'll tell you honestly if you're ready for this.

Before the call: send your target company, JD, and current level. I'll calibrate the problem to their loop.