B.Tech in Electronics & Communication
Amrita Vishwa Vidyapeetham. Formally studied electronics, signals, and communication theory while building software in the margins.
I build systems.
Software → products → businesses → and increasingly, things that touch the physical world.
I studied electronics. I ended up building software. Software led me into AI, products and companies. Now I’m slowly finding my way back toward machines and the physical world.
Stayin · Machynx
Engineer · Builder · Co-founder·India
Amrita Vishwa Vidyapeetham. Formally studied electronics, signals, and communication theory while building software in the margins.
Ground-level learning through production code: deployment bugs, databases, client expectations, and the work between them.
Built digital workflows for backflow and water-meter inspection across NestJS backends, web portals, and Flutter applications.
Co-authored research on detecting Atrial Fibrillation from noisy Photoplethysmography wrist signals using pulse interval dynamics.
Worked in the safety department around a transmission control unit: C, IBM Rhapsody, AEEPro, and ISO 26262 functional-safety thinking. An eye-opening first close look at how software becomes part of an automobile.
Worked on backend software for industrial machine monitoring, MQTT telemetry, PostgreSQL storage, and operator assistance tools.
Worked with global teams across Databricks, Azure, PyTorch, Qwen-VL, Transformers, and attention-map analysis. Focused on taking transformer work from local experiments through Azure production training and GitHub CI/CD.
Owning the technical surface end to end: product decisions, backend, schema design, infrastructure, DevOps, architecture trade-offs, and the work required to make an Indian metro residential rental platform useful.
Co-founder & CTO
Trying to make renting a home less painful.
View more ↓Founder · industrial systems
Trying to understand what factory machines are actually doing.
Edge telemetry, industrial protocols and a cloud conversation layer.
View more ↓The responsibility was. Stayin began as a software problem, then became a product, an operation and a team that needed clear decisions.
Build the APIs, design the database and make the first version work.
At some point my work stopped being measured only by what I personally implemented. The clarity I gave other people started mattering just as much.
Digital workflows for backflow and water-meter inspection, moving from paper records toward structured tools.
Physical pen-and-paper records filled manually during inspections.
Motors, PLCs and existing signals stay where they are.
Firmware reads, buffers and forwards telemetry.
Time-series data becomes useful context for Lynx.
Choose a machine before asking Lynx. Fleet questions add the machines together.
I entered automotive computer vision through the data side, working with multimodal models and annotation quality. The question was simple: which samples deserve a second look before a label is trusted as ground truth?
In the Bosch–CARIAD automated-driving environment, I worked with perception data covering traffic-management infrastructure and temporary road scenes: poles, bollards, hydrants, traffic cones, traffic lights, signs and construction zones.
These objects are static or slow-moving, but they still shape the vehicle’s decision-making. A useful perception system has to detect them, place them in context and distinguish a harmless roadside object from something that changes the path ahead.
Static roadside infrastructure is detected beyond the vehicle’s path.
I experimented with using a vision-language model to question existing labels. Disagreement, confidence and margin checks surface suspicious samples for human review instead of silently overwriting ground truth.
The model learned useful structure, but class imbalance and ambiguous labels made failure analysis more valuable than a single accuracy score. It pushed me to look beyond model tuning and understand the dataset that shaped every result.
A small experiment in making software feel less like a dashboard and more like a place to think.
Exploring visual language models and the practical edges of dataset quality work.
A full-stack starting point for building serious TypeScript applications.
Detection of Atrial Fibrillation using PPG Signals — published at IEEE INDICON 2024. The work combines derived and morphological PPG features, including entropy, RMSSD, onset amplitude, crest interval and pulse width.
Learning what factory floors actually need.
I care about companies almost as much as engineering, so over time I started caring less about individual technologies and more about whether something useful actually gets built.
Outside work I play badminton, read, spend time with my tarantulas, and disappear into subjects I know very little about until I understand slightly more than I did before.
I also keep tarantulas. They’re quiet, strange little creatures that I’m probably far too attached to. The tiny one wandering around this website is there because of them.
Badminton · Reading · Tarantulas · Product & startups · AI / computer vision · Software systems · Manufacturing — learning · Business
Node.js · NestJS · TypeScript · Python · API design · MatLab
PostgreSQL · MySQL · Prisma · Redis · Schema design
AWS · Azure · Docker · Nginx · Cloudflare · GitHub CI/CD
PyTorch · Transformers · Qwen-VL · Databricks · LangGraph · Computer vision · Attention maps
MQTT · RS485 / Modbus · Telemetry · Embedded direction · Manufacturing
C · ISO 26262 · IBM Rhapsody · AEEPro · Functional safety
React · React Native · Flutter
Product decisions · Architecture trade-offs · Operator workflows · Team engineering
Industrial systems · Embedded systems · Manufacturing · Product · Business / finance
Nothing to show here yet.
Work, startups, products, AI, industrial systems, collaboration—or simply something interesting.
Work, startups, products, AI, industrial systems, collaboration—or simply something interesting.
Send me a message first. I’ll share my direct details once I’ve checked the request.
Pick a real open window. I only show times that are actually available.
Times are shown in the host’s timezone.