I keep the interface still.
Frontend engineer. Four years in the trade. I build real-time systems — trading terminals that breathe, yards that watch themselves, maps that move with the people on them. Every interface is a koan: the answer is in the question.
"The craftsman does not rush the grain of the wood. He listens to it. Then he cuts — once, and clean."
Descend
On the discipline
of the craft.
I did not choose code because it was fast. I chose it because it was patient. It rewards the one who returns to the same small problem the next morning — sits down, and begins again. My practice: take the complex system, the one that updates twenty times a second, the one people depend on at 3am — and make it feel calm. That is the whole work. Everything else is decoration. And decoration, as any monk will tell you, is where the ego hides.
Sahil Dhingra · disciple of clean interfaces
written at the desk, Bengaluru
The garden of works.
The precepts I keep.
A monk keeps vows. Not because they are rules — but because they are a frame for attention. These are the five I return to every time I open an editor.
Prefer less, not more.
The smallest change that solves the problem is almost always the right one. Every line you don't add is a line someone won't have to read at 2am.
— Because code is read far more often than it is written.
Move slowly, ship deliberately.
Speed in the editor is not the same as speed to the user. I'd rather take a day longer than fix a rushed interface for a month.
— Because the rush you feel is not the user's rush.
Name things truly.
If a function is hard to name, it is doing too much. If a component resists a name, the boundary is wrong. Naming is design work.
— Because a good name is half the documentation.
Make the quiet version.
Interfaces should not shout. No gratuitous animation, no gratuitous colour, no ornament that doesn't earn its place. The best UI is forgotten.
— Because attention is the user's scarcest resource.
Accept critique without flinching.
Every code review is a gift from someone who owes you nothing. The ego wants to defend. The craftsman wants to learn.
— Because a defended mistake is a doubled mistake.
Disciplines practised.
React.js
Next.js
TypeScript
JavaScript ES6+
Redux
Jotai
SSR
WebRTC
CSS3
HTML5
SCSS
Tailwind
Bootstrap
Styled Components
Shadcn UI
Chakra UI
Ant Design
Node.js
Express.js
FastAPI
GraphQL
MongoDB
SQL
Python
PHP
Git
GitHub
Docker
Vercel
Netlify
Figma
Postman
Jest
CI/CD
Swagger
The path walked.
Frontend Developer · KoiReader
- Architected a real-time yard management dashboard for a renowned German automotive brand, WebSocket-syncing dual applications across parallel lanes.
- Built data-visualisation dashboards for a multinational beverage enterprise.
- Engineered a self-service kiosk UI with a custom glassmorphism virtual keyboard.
- Delivered low-latency WebRTC streaming via FastAPI + Next.js — 40% latency reduction.
SDE I · Wealthy
- Spearheaded an insurance portal across 5 verticals — +25% conversions, −30% drop-off.
- Built a trading terminal with complex REST integrations, cutting render latency by 35%.
- Built an automated email template generator cutting campaign build time by 60%.
SDE Intern · Wealthy
- Shipped a dynamic stock screener SPA serving 10,000+ MAU.
- Refactored blog architecture with SSR & SEO — +40% Lighthouse.
Web Designer · Toxsl
- Engineered scalable UI modules across 4+ enterprise ERP / HR platforms.
- Converted Figma prototypes to production — 15% faster delivery, 30% fewer UI bugs.
Web Developer · Freelance
- Delivered 10+ high-converting landing pages — +25% client engagement.
- Shipped SEO-optimised apps — +30% average organic traffic.
The four practices.
Listen to the problem
Before one line of code, I want the shape of what success looks like. What hurts today. What we're deliberately not doing. Most projects fail here, not in execution.
Prototype in the real thing
Figma is where we agree. Production is where we learn. I prototype in Next.js early so we can feel the actual latency, hit real APIs, and make honest tradeoffs.
Sweat the milliseconds
Bundle budgets, render timing, skeleton states, error boundaries, animation easing. The unglamorous work that makes a product feel expensive. It compounds.
Hand it over well
Readable code, honest docs, a working demo. I'd rather ship something a team can extend than something only I understand — the mark of a true craftsman.
Come sit for tea.
I'm open to senior frontend roles, contract work, and thoughtful freelance projects. I usually reply within a day — even if it's just to say "not now, but here's someone who might fit."
Whether you need a senior engineer to own a frontend, a craftsman to fix the details that got skipped, or a partner to build something new — let's talk.
sahildhingra221@gmail.com