Local time in MUMBAI · UTC+5:30 ·
Senior engineerMumbaiworking your hoursavailable
02 · Pressure
1.6M+
Total users of the voting platform over the campaign, not concurrent sessions.
22 days
Length of the live voting campaign, from the opening to the close of voting.
99.99%
Availability over the campaign, from the Google Cloud load balancer's health checks: no failed check and no outage was seen during the campaign.
03 · Proof
Case studies in platforms that had to hold: a real-time voting platform, a CMS migration to the cloud, an AI image pipeline, a B2B SaaS and more.
Exhibit Magazine India Pvt. Ltd. · Real-time voting platform · 2024
A voting platform that stayed fast for all 22 days of a campaign.
Every vote had to be accepted and counted within a fixed campaign window of 22 days. Downtime or a lost vote would have been a public failure, and the budget ruled out simply buying more servers.
Exhibit Magazine India Pvt. Ltd. · CMS migration and modernization · 2024
A magazine CMS moved from CodeIgniter on shared hosting to Laravel on Google Cloud: page loads from 1–3 min → 3 s.
The legacy CodeIgniter code on shared hosting was slowest exactly when it mattered, during traffic spikes. The modernization had to happen while the newsroom kept publishing every day.
Exhibit Magazine India Pvt. Ltd. · AI pipeline · 2025
A pipeline that turns a phone photo of clothing into a clean, e-commerce-style product image in 3–8 s.
Analyze clothing photos, remove backgrounds and recommend outfits quickly enough for a phone user, within a strict cloud budget.
Exhibit Magazine India Pvt. Ltd. · B2B SaaS platform · 2024
A B2B influencer-marketing platform built from zero: 10,000+ influencers indexed and 30+ brand campaigns run on it.
Discovery, real-time analytics, automated data collection and a collaboration workflow, all built from nothing, on top of third-party APIs with strict rate limits.
04 · Practice
Measure before you guess.
With measurement, not guesses: real-user data where it exists, then profiling of the slowest pages and endpoints down to individual queries and code paths. The fix list follows the numbers.
Ship the smallest true thing first.
A small, bounded piece of work with a written outcome: an audit, an assessment or a scoping sprint. You see how I work before committing to more.
Write it down so the team can carry on without me.
I often join existing teams: I set up the foundations, review code, pair with your developers, and leave documentation behind so the team can carry on without me.
Your repo, your cloud, your IP, from day one.
You do. Intellectual property is assigned to you on payment, and the code lives in your repository from the first day.
Weekly updates, your hours.
A written update every week, a demo whenever there's something to see, and calls scheduled in your working hours.
Five lines of work, each with a small, fixed-price first step, so you can see how I work before committing to more.
05 · Reach
Clients in the United States, the United Kingdom and the rest of Europe, the UAE and Saudi Arabia, Japan and South Korea. I work in English, with written documentation for everything that matters.
I plan my day around my clients' hours.
| Market | TimeTheir time | Overlap today |
|---|---|---|
| US New York | --:-- | — |
| UK London | --:-- | — |
| EU Berlin | --:-- | — |
| UAE Dubai | --:-- | — |
| KSA Riyadh | --:-- | — |
| JP Tokyo | --:-- | — |
| KR Seoul | --:-- | — |
06 · Signal
I read every brief myself and reply within one business day, in your working hours.
If it looks like a fit, I suggest a short call and, usually, a small fixed-price first step.
If it isn't a fit, I say so and, where I can, point you to someone who is.