A career path from production infrastructure through embedded firmware and kernel networking to real-time AI. The layers changed; the operating discipline did not: explicit constraints, observable state, bounded failure, and recovery that works outside the demo.
Four operating layers, ordered by where the work began. Each record names the environment, the responsibility, and the technical evidence that carried forward.
System administrator / infrastructure operator
Operate production systems across dedicated servers and cloud platforms, with virtualization, storage, firewalls, secure access, public routing, monitoring, backup discipline, incident debugging, and explicit recovery paths.
Embedded systems software developer
Built bare-metal and RTOS firmware for access-control and security devices, including supervised field protocols, constrained-device cryptography, UWB/BLE localization, calibration tools, and production debugging across physical interfaces.
Systems software developer
Developed a real-time Layer 2 networking stack for aerial vehicles, moving IEEE 802.1CB replication and elimination into the Linux fast path while working across TSN timing, Rust control planes, and custom embedded Linux images.
Lead software engineer
Own architecture and production hardening for a multimodal agent platform spanning voice, tools, state, memory, retrieval, persistence, WebRTC delivery, observability, and failure-safe asynchronous lifecycles.
Public technical records spanning AI runtime, kernel fast paths, physical devices, and infrastructure operations.
Production voice-agent paths are architected end to end—from audio ingress and interruption handling to tool execution, memory, recovery, and stage-level telemetry.
scope: Production architecture, published without customer details
Latency ownership · bounded queues · cancellation · degraded modes · OpenTelemetry
inspect proof ->IEEE 802.1CB-style replication and duplicate elimination move into the Linux receive path under verifier, state-budget, packet-reordering, and sequence-window constraints.
scope: Real-time Layer 2 networking, documented without private vehicle topology
Bare-metal and RTOS products combine secure supervised device communication with UWB/BLE localization, filtering, calibration, visualization, and field-debugging tools.
scope: Embedded security and RTLS work under constrained-device and deployment limits
A segmented virtualization and routing fabric treats public ingress, storage, secure administration, observability, backups, and service recovery as one operated system.
scope: Independent infrastructure operations with public homelab architecture evidence
Proxmox · QEMU/KVM · Ceph · OPNsense · WireGuard · NGINX · recovery paths
inspect proof ->