BIT_on_Tech™ is the signature I publish under.
Bit Veil is the veil itself.
I’m drawn to the spaces where electronics, sensors, and radio meet software, and where code meets reality,
often in the grey areas where things are rarely ever just black and white.
I design and build systems across that boundary, hardware circuits, firmware, and software alike,
not just to make them run, but to let electronic circuits, control logic, signal processing, algorithms,
and AI systems manifest in the physical world through sensors, actuators, and human interfaces.
I don’t limit myself to intended paths, because systems reveal more when approached from unexpected angles.
Not malicious. Not reckless. Just curious and analytical.
Some systems don’t explain themselves. Their undocumented behavior, edge cases, and deeper layers only emerge
when you move beyond the documented surface and immediate boundaries.
For me, that freedom means being able to inspect, trace, reverse, build, and reason about a system,
not to break it, but to know it.
Manuals describe intent. Real understanding and answers only emerge when you follow the system itself upstream.
At its core:
“Curiosity opens systems. Real understanding begins when you stop assuming they are telling you everything.
Discretion defines the engineer.”
Understanding systems beneath the surface…
is what makes building them truly powerful.
Technical background and accumulated domains
The following reflect domains where I have accumulated experience and deep familiarity over time, as they describe past involvement and long-term understanding.
Areas of prior specialization
Selected historical focus areas
Electronics, PCB & Circuit Design
Systems Programming & Low-level Code
Embedded Systems, IoT & Firmware
Reverse Engineering & Offensive Security
Cellular / LPWAN, Radio & RF
Networking, Telemetry & Backend Systems
More historical focus areas Click to expand
MCU Platforms, Device Buses & Interfaces
RF Direction Finding & Radar Systems
Cryptography, Auth & Access Control
Testing & Verification
Documentation, Release & Lifecycle
Contact boundaries
I don’t actively seek projects, and I don’t operate as a consultancy. Any engagement is highly selective and contingent on a problem being technically interesting, well-defined, and personally sustainable for me. If something resonates, I may be open to a conversation.
All messages are read manually. Replies are not guaranteed and should not be expected; they may occur only when relevance and clarity align with my capacity to engage with the problem at an appropriate depth.
Contact formats
Mail and SMS are distinct channels, each with a different intended scope.
- Preferred for introductions and technical context.
- Reserved for short, time-critical matters.