Built from first principles.
Two co-founders. 20+ years of combined engineering experience. One who builds from the kernel up, one who designs from the human side down. This is how we got here.
The full stack — from silicon to human
Most software vendors have engineers who work at the application layer. Some have engineers who work at the systems layer. Very few have both: co-founders who have independently proven it at demanding companies.
One co-founder brings systems engineering depth at the kernel and OS level: contributions to a sub-2 MB x86 operating system written in assembly, browser porting across networking and windowing subsystems, work in a high-frequency trading environment under microsecond latency discipline, and years of safety-critical embedded software where hardware-software integration failures have physical consequences.
The other brings the applied layer: a formal postgraduate specialisation in Human-Computer Interaction, VR and AR research on human perception and information visualisation, AI/ML product design for large-scale enterprise cognitive systems, and years of product engineering on complex enterprise software where human usability is not optional.
The two skillsets are complementary in the exact way that complex system development requires. One founder who can build what runs under the hood. One who can design what humans actually use. For systems where both software correctness and human usability are mission-critical, this is not a nice-to-have combination. It is the requirement.
How we think about software
We believe software quality is an engineering discipline, not a product feature. It is the outcome of hiring people who have worked in environments where getting it wrong has consequences, and who carry that discipline into every subsequent project, regardless of the stakes.
“The most important thing about a system is not whether it works the first time. It is whether it keeps working: under load, under failure, under the conditions no one anticipated.”
Our founders have worked in High-Frequency Trading, where a slow trade means a lost trade and software correctness is measured in microseconds. In safety-critical embedded contexts, where a bug can have physical consequences. In large-scale production systems, where errors cascade across infrastructure serving millions of people. That experience is not a credential to put on a slide. It is the origin of how we reason about reliability, testing, and systems correctness.
India needs software companies that take reliability seriously. Not just as a market differentiator, but as a fundamental commitment to the people who depend on the systems we build. Bitnibblr exists to be one of those companies.
The engineers behind the work
Co-founder — Systems & Kernel Engineering
Specialisation
“Built software where a slow trade means a lost trade, where a bug has physical consequences, and where correctness is non-negotiable. That shapes everything we build.”
Co-founder — UX Design & Product Engineering
Specialisation
“Formal postgraduate specialisation in Human-Computer Interaction, combined with years designing AI/ML systems at enterprise scale. Interfaces for high-stakes environments that work under pressure.”