01
Connected Device Firmware
Firmware for connected products where the device, hardware interfaces, network behavior and lifecycle all have to agree.
SERVICES / SYSTEMS ENGINEERING
Hands-on engineering across the whole path.
I work best where a product or failure crosses boundaries — firmware and hardware, endpoint and PBX, application and infrastructure, service state and user-visible behavior.
02
Voice & Real-Time Communications
SIP/RTP systems from endpoint behavior through PBX and media paths, including the failures that only appear during real calls.
03
Infrastructure & Operations
Linux and container infrastructure with clear ingress, health, observability, service state and recovery paths.
04
Cross-Layer Debugging
For problems that refuse to stay in one box: audio that is really timing, calls that connect without media, or healthy processes behind broken services.
HOW AN ENGAGEMENT MOVES
Frame the system
Map boundaries, clocks, dependencies, data paths and the exact failure before changing behavior.
Make it observable
Collect the evidence the system already has: logs, packets, timing, state, metrics and hardware behavior.
Isolate one boundary
Preserve a known-good control and change one part of the path at a time.
Build and retest
Turn the hypothesis into the smallest useful change, then repeat the same failure test.
Leave a trail
Document architecture, verification and recovery so the system is easier to operate after the fix.
GOOD FIT
You already have a real system, a real product, or a real failure.
Connected device firmware that has to integrate with the rest of the product.
Voice or SIP/RTP behavior that needs endpoint-to-media-path debugging.
Linux/container infrastructure that needs clearer state, health and operational control.
A problem that keeps bouncing between teams because no single layer explains it.
RELATED CASE STUDIESAll work →
01↗02↗03↗04↗
Embedded firmware / real-time audio / SIP-RTP
ESP32-S3 Connected Voice Device
Building and debugging a real-time voice device across firmware, codecs, audio timing, packet transport, PBX integration and hardware behavior.
Linux / Docker / secure ingress / operations
Infrastructure Operations Platform
An operations layer for a multi-service Linux environment where runtime state, health, dependencies, access and recovery need to be understood together.
Prometheus / Grafana / failure simulation
Production Observability & Alert Validation
Testing whether monitoring detects real failure, including deliberately creating load and proving the complete alert path rather than trusting dashboards.
SIP signaling / RTP media / distributed debugging
VoIP & Real-Time Communications Infrastructure
Building and debugging signaling, routing, media, endpoints and infrastructure around real-time communications rather than treating the PBX as the whole system.