Electronics Engineer & Senior Software Developer building systems where hardware meets software.
I build robust software and hardware systems, from full-stack applications and mobile experiences to embedded systems and high-performance engineering solutions.
An engineer who is equally comfortable reading a datasheet and refactoring an application layer — and who thinks the two are the same job seen from different heights.
Kathmandu, Nepal
27.7°N 85.3°E
I am an Electronics Engineer and Senior Software Developer driven by a passion for building robust systems that bridge the gap between hardware and software. From designing complex full-stack architectures to prototyping embedded devices, I thrive on solving technical challenges and bringing innovative ideas to life.
My training is in electronics, which means my instinct is to ask what is physically happening before asking what the code says. A dropped packet, a mistimed interrupt and an inconsistent database write are, structurally, the same class of problem: state that stopped agreeing with itself. That habit follows me up the stack.
Day to day I build applications — backends, APIs, mobile interfaces and the business logic underneath them. But the work I find most interesting sits at the seams, where a calculation engine written in C++ has to serve a React Native screen, or where a sensor reading has to survive the trip into a product someone actually uses.
I still prototype hardware because it keeps me honest. Software forgives; hardware does not. Between the two I have settled into a way of working that is curious, methodical and unfinished — there is always another layer worth understanding properly.
// Expogenius is based in Copenhagen, Denmark. Subarna works remotely from Kathmandu.
Three domains that are not really separate. Most of the work I care about happens where they overlap — a calculation engine that has to feel instant on a phone, or a sensor reading that has to survive the trip into a product.
I engineer full-stack applications and digital products with a focus on scalable architecture, reliable business logic, maintainable systems, and practical user experiences.
My Electronics Engineering background allows me to work beyond application-level software and understand the systems underneath it.
I enjoy working across the boundaries between technologies and designing complete systems that connect software, hardware, data, and business logic.
Six things I keep coming back to. None of them are original — they are just the ones that have cost me enough time to become habits.
HardwareLogicSoftwareInterface
A bug is rarely where it appears. Before writing code I want to see the whole path — where the signal starts, what transforms it, and what finally consumes it. Most hard problems dissolve once that path is drawn honestly.
It is easy to patch a symptom and call it shipped. I would rather spend the extra hour finding the condition that produced it, because the same condition will come back under a different name.
Clear boundaries, predictable data flow and one obvious place for every decision. When the structure is right, correctness is cheap to maintain; when it is wrong, no amount of defensive code rescues it.
Hardware taught me this. A radar signal, a dropped connection, a rounding error in a financial condition — the edge case is not an exception to the system, it is the system on a bad day.
Every dependency, abstraction and configuration flag is something a future engineer has to carry. Complexity should have to justify itself before it is allowed in.
Shipping is the start of the feedback loop, not the end of it. I keep reading, measuring and refactoring, in software and in the way I work.
Three projects that sit at different heights of the same stack: one mobile application with real calculation underneath it, one embedded system, and one piece of business-critical infrastructure.
Schematic representation, not a product screenshot.
An Android application focused on Jyotish and Kundali functionality.
An astrology domain is deceptively computational: the interface is calendars and charts, but underneath it is deterministic calculation that has to agree with itself every single time. The work sits in the boundary between a mobile application architecture and the calculation logic it depends on.
Schematic representation, not a product screenshot.
Engineering and simulation work involving embedded systems, C++, bit-shifting logic, and hardware-oriented processing.
A speed sign is a small system with an unforgiving loop: a sensor produces a reading, embedded logic conditions it, and a display has to show the right number at the right moment. Working on it in simulation and on STM32/Arduino environments meant thinking in registers and bit-shifts rather than objects and abstractions.
Schematic representation, not a product screenshot.
System-design and development work involving travel workflows, CRM processes, financial integrity conditions, and structured business logic.
B2B travel is a workflow problem before it is a software problem: agents, bookings, and money move through states that must stay consistent with each other. The interesting engineering is in modelling those states, and in the financial integrity conditions that must hold no matter which path a record took to get there.
No percentages. Where a technology sits in the system is a more useful thing to know than a number someone invented for a bar chart.
The three I actually write in
Close to the metal
Services, data and APIs
What the user actually touches
Build, design-to-code and API workflow
Efficiency and customization are at the core of my workflow. I prefer a highly tailored, lightweight development environment and run Arch Linux powered by the Hyprland window manager. Combined with Waybar and a Kitty terminal, my setup is designed for speed, precision, and zero clutter.
kitty — ~/projects
~ ❯ fastfetch
~ ❯
41uint16_t frame = (hi << 8) | lo;
42if (frame & STATUS_MASK) {
43emit(decode(frame));
44}
hyprlandrunning
waybarrunning
kittyrunning
Interactive: select a workspace to re-tile the layout.
A tiling window manager is not an aesthetic choice. It removes the part of the day spent arranging windows, and it makes the machine behave the same way every single time — which is the same thing I want from a build pipeline.
Minimal environment.
Maximum control.
Not a chronology — no stage replaced the one before it. Each layer I learned is still in use, which is exactly why the boundaries between them are where I am most useful.
Foundation
The formal grounding: signals, circuits, and the discipline of reasoning about a system you cannot simply restart.
Firmware
Working close to the hardware — embedded C++, bit-level logic, prototyping and simulation on STM32 and Arduino environments.
Application
Moving up the stack into application code, where the same systems thinking applies to state, data flow and business rules.
Product
End-to-end delivery: backends, APIs, and mobile applications built with React Native, Expo and Firebase.
Current · Expogenius
Architecture and delivery across software and hardware-adjacent systems, working remotely from Kathmandu.
Engineering discipline extends beyond the terminal. Outside technology, I focus on fitness, consistency, and continuous self-improvement.
I am a fitness enthusiast and regular gym-goer. I maintain a consistent strength-training routine and focus on nutrition, discipline, and continuous improvement. For me, fitness is not simply about appearance — it is about building consistency, strength, and mental resilience.
Discipline in engineering.
Discipline in life.
The rest of it: mountains, long rides, and the occasional very bad idea at height. Nepal makes all three easy to find.
I enjoy working on technically challenging problems where software, hardware, and systems engineering come together.
Gokarna, Kathmandu, Nepal · Working Remotely · Asia/Kathmandu
// No email, GitHub or LinkedIn is published here yet. These
// slots are wired up — add the real values in data/site.ts and they
// render as live links automatically.
If a problem sits between disciplines — a calculation engine that has to feel instant on a phone, firmware that has to talk to a product, a workflow that has to stay financially consistent — that is the kind of work I want to hear about.