Who is Gautam Suthar?

Gautam Suthar is a software engineer from India who has the increasingly rare habit of finishing things. He works across the whole stack (schema design, backend services, the API in the middle, and the interface people actually touch), and he treats the boundaries between those as an implementation detail rather than a job description.

Professionally he is a Software Engineer at Pixerfect, where he ships features end to end across client applications and the company's core product, builds backend systems in NestJS and Node.js, and spends a meaningful share of his time on the unglamorous work that decides whether software is any good: chasing production bugs across the full stack and making slow things fast. He is not only an in-house engineer there: he works directly with clients, including one in South Africa whose product he builds and keeps running in production, and he guides the interns and junior engineers on the team through review, architecture calls and the debugging sessions where the actual learning happens.

Before that he was at Untitledlabs, on the backend of an AI image generation platform in Node.js, Express and Go, building REST APIs and wiring up AWS S3 and Lambda for media processing at scale. That role was fully remote for a US company, done from India across a 10-12 hour time difference, and he led four interns through it. Remote is worth stating plainly rather than as a footnote: async by default, decisions written down instead of said out loud, and most of the working day spent shipping against a team that was asleep. He is very good at it because the job gave him no other option.

Before that, two years of freelance work with international clients, which is where most of the end-to-end ownership instinct comes from: scoping, building, deploying and answering for it yourself, because when you freelance there is nobody else to hand the hard part to.

The part that tells you the most about him is what he builds when nobody has asked. Atarashi is a scaffolding CLI he wrote, shipped, and then publicly wrote up the architectural dead end he had designed himself into. Flux is a package manager he started because his college is surrounded by forest and the internet was bad enough to make `npm install` a spectator sport. Expressentials is the four files he kept copying between Express projects, published so he could stop. Treegen is a Go tool for pasting folder trees into READMEs that quietly turned into a tool for reading them back out. None of these were career moves. They are all real, all installable, and all documented with the failures left in.

He also keeps a graveyard page on his own portfolio: a public list of the projects he abandoned, each with one honest sentence about why. A text editor in C he finished and never opened again. A job-application bot that worked, which is precisely when he realised he did not want a job he could get without reading the posting. That page is voluntary, and it is the most credible thing on the site.

He writes, mostly about databases and how systems come apart under load: read replicas, sharding, the trade-offs nobody puts in the marketing page. He runs The Basement, a Discord community for developers. His site publishes its own uptime, including its own outages, and answers `curl` with an ANSI card instead of HTML, because he thinks the terminal deserves a front door too.

The through-line, if you want one, is the word he put in his own footer: kaizen. Continuous improvement. Ship it, use it, notice what's wrong with it, fix that. It is a slower way to get good and it is the only one that seems to work.