I build systems that have to tell the truth at the edge.

I am not a pure software founder who discovered infrastructure through a cloud dashboard. I came at it from hardware. I started with small robots and UAVs when I was 16, then found my way into nanosatellite electronics, robotics, and industrial controls. The pattern kept repeating: the interesting part of a system is not the UI that reports what happened. It is the device, controller, meter, sensor, gateway, or runtime that decides what can be trusted in the first place.

At TSC Technologies, from 2020 to 2022, I worked on CubeSat electronics in Bengaluru. OBC, EPS, RF, ADCS-support electronics, telemetry, power, board bring-up, EMI and ESD validation, documentation, the unglamorous stack that makes a small satellite more than a neat render. The work covered 0.3U, 1U, and 3U buses. I was 23 when that hardware had to be treated as flight-facing, which is a good age to learn that confidence is cheap and checklists are expensive for a reason.

After that I did my Master of Engineering in Robotics at the University of Maryland, College Park. That period gave me the autonomy side of the stack: visual odometry, path planning, SLAM, perception, tracking, simulation, and the humbling reality that a robot can make a beautiful plan and still lose to lighting, friction, latency, or a sensor mount that moved half a degree. Robotics makes you suspicious of clean diagrams. Good. Clean diagrams hide what the system has not yet been forced to admit.

Wabtec made the lesson heavier. From July 2024 to December 2025, I worked as a controls engineer in Erie, Pennsylvania on off-highway drive and liquid-cooling systems, diagnostics, validation, and high-voltage safety. Heavy industrial systems do not care that a model worked once. They care whether the system behaves under duty cycles, noise, drift, component aging, operator intervention, compliance pressure, and bad days. I left Wabtec on December 26, 2025 and moved back to India because the same edge-truth problem I had seen in satellites, UAVs, and industrial controls was sitting inside the Indian energy transition.

JouleBridge is the company I am building now. It runs at an energy site, beside chargers, meters, batteries, solar inverters, and operator systems. It canonicalizes reads and commands, signs them, applies policy gates, writes a hash-chained ledger, and exports evidence packs that another party can verify without trusting the JouleBridge server. The first wedge is EV depots and energy sites where billing, dispatch, tariffs, and AI-assisted operations create disputes that a normal dashboard cannot settle.

Other engineering work runs at the side. The throughline is the same: trusted edge systems where software touches physical work, records what happened, and survives review after the fact. JouleBridge is the focus.

I am solo by design for this stage. The first hire is a senior protocol or edge engineer after a paid pilot; the second is a utility, AMISP, or EV-depot GTM partner.