I build the whole thing,
then I have to live with it.
solder to typeI'm a Senior UX Architect and UX Engineer. I work on enterprise telemetry, IoT hardware interfaces, and the full-stack applications that sit on top of them — usually the kind of system where the hardware and the software argue with each other, and somebody has to own both sides of the argument.
- 9
- Systems shipped
- 5
- Layers I work across
- 1
- Needed all five
the registry in full — nothing here is a concept
hardware, firmware, data, interface, design system
Farm OS
Background
Where the work happened.
2 countries, 4 audiences, 8 years. Rows with a case study behind them link through; the rest don't — a history where most entries dead-end costs more trust than a short honest one.
Spectrum
Senior User Experience Designer
Leading end-to-end UX architecture for enterprise products and scaling the design system.
2026 —Enterprise SaaSSavannah College of Art and Design
UX Designer
B2C student portal for schedules, financial aid and assignment tracking — research through to documented design-system components.
2019 — 2022Higher-Ed PlatformMahindra Logistics
UX Designer
Real-time tracking dashboards; 25% improvement in operational visibility.
2019Fleet & Warehouse
How I got here
I started on a logistics floor in India, building real-time tracking dashboards for a fleet that could not afford to guess where anything was. That is where the habit formed: if a system can't tell you its own state, everything downstream of it is speculation.
Six years in the US followed, on two products that could not have had less in common: a student portal for eighteen-year-olds opening a financial-aid statement for the first time, then a purchasing platform for people who knew the catalogue better than the software did.
Then back to India, and out of the IDE entirely. Farm OS meant Hyderabad summers and 22,000-bird sheds, where the specific panic of a 40°C afternoon is not something you can understand over a call.
The through-line is not the stack, it is the range. Warehouse supervisors, undergraduates, trade buyers, poultry farmers — they share no vocabulary and no assumption about what software is even for, and each breaks a system in a way the others never would. That is what taught me to design for the state a system is actually in, rather than the one a happy path assumes.
Working together
Three shapes this usually takes.
Audit
You have a system that works and an interface that argues with it.
A read of the whole stack — data model, states, failure modes, and the screens sitting on top. What comes back is what is actually wrong and in which order, not a redesign.
Embedded
You have a team and a gap where the systems thinking should be.
Inside your process and your repo, design and front-end both. Specs handed across a wall are where the seams appear, so I don't hand them across a wall.
Full build
You have a problem and there is no system yet.
Solder to type: hardware if it needs hardware, the data model, the interface, and the design system that stops the whole thing forking six months in.
What I'm good for
Systems with real operational consequences, where the interface is one layer of a stack that includes firmware, data and a physical environment. I'm least useful on work that is purely visual and has no state to reason about.
Questions
What people ask before they email.
- Where are you based, and do you work with clients outside India?
- I'm based in Hyderabad, India, and I work remotely with clients anywhere. The record is already cross-border: three years on a US distributor's purchasing platform, three before that on an American art school's student portal, and the current enterprise role is US software run from here.
- Do you build hardware, or only design interfaces for it?
- Both, on the same system. Farm OS is custom ESP32 edge nodes in printed PETG enclosures with an MQTT path to a phone, and 222 was an enclosure, its firmware and the app together. Of nine systems on this site, one required all five layers — hardware, firmware, data, interface and design system — and that one is Farm OS. Farm OS
- Do you write production code, or hand designs over to a team?
- I implement what I design. The Winsupply engagement was design and front-end both, including theming the PrimeNG component library the platform is built on; Poultry Ledger is a Flutter app in daily use that I wrote. Specs handed across a wall are where the seams appear, so I try not to hand them across a wall. Poultry Ledger
- What do you mean by "design system"? Everyone means something different.
- Tokens the build actually reads, not a palette sitting in a design file. QRsocial is 72 semantic token slots under one contract, filled five ways across a CSS-variable web pipeline and a native ThemeColors interface; Winsupply was a sampled-and-corrected token set with a density scale and a platform information architecture attached. QRsocial
- Have you worked on enterprise or internal software, or only your own products?
- Both. Winsupply's internal purchasing platform, which around 600 independently-owned local companies buy through, was three years of design and front-end; before that, three years on a student portal running on Ellucian Banner 9. Both of those case studies are password-protected because they carry a former employer's internal screens — ask and I'll send access.
- Why are two of the case studies locked?
- Because they contain a former employer's internal screens — purchase orders, customer names, live registration flows — and publishing those would be a decision that is not mine to make. Winsupply and MySCAD open with a password, and I hand it out per project rather than as one key to both. Email me and I'll send the one you want.
- Which industries have you actually shipped in?
- Fleet logistics and warehousing, higher education, industrial distribution, poultry and agriculture, direct-to-consumer food retail, hospitality venues, and rideshare transport. The through-line is not the sector — it's that in every one of them the person at the other end had no shared vocabulary with the last one, and each broke the system in a way the others never would.
- Do you do research, or start from a brief?
- I start where the work happens. Most of Farm OS was decided standing in a 40°C shed rather than on a spec sheet; Node ran 111 survey responses, 20 user interviews and 9 expert interviews, and what came out of it cut the feature list from five to three. Testing here is what removes features, not what confirms them. Node
- What happens when the network isn't there?
- Offline-first is a data decision long before it is a UI one — the interface can only show a conflict the model bothered to keep. Poultry Ledger queues a photograph on the phone when neither the local model nor the hosted one is reachable, and Node is a mesh radio built for the days after a disaster takes the cell network with it. Poultry Ledger
If any of this sounds like your problem.
Tell me what the system does, what it does wrong, and who it hurts when it does. That is enough to start from.