REAZ ROMEN / ABOUT

I’m Reaz Romen. I work at the seams between systems.

I work across IoT, embedded systems, VoIP, telecommunications and Linux infrastructure. I also research and write about technology, engineering, science and the systems behind them. I’m most useful when a product crosses several layers and the problem does not belong cleanly to one team or one tool.

A lot of my work is hands-on: ESP32-S3 firmware and audio, SIP/RTP call paths, Asterisk and FreeSWITCH, Linux services, Docker and Kubernetes, observability, ingress and the glue between them. The symptom often appears in one layer while the root cause lives somewhere else.

I prefer evidence over guesswork. I use serial logs, packet captures, timing measurements, metrics, controlled A/B builds and known-good baselines. I preserve working states before changing them, and I document the path so the system can be understood again later.

The part I enjoy most is turning a messy cross-layer failure into a system somebody can reason about.
WHAT I BUILD

IoT and embedded devices, VoIP systems, Linux infrastructure and technical writing.

HOW I DEBUG

SIP/RTP, FreeSWITCH, Asterisk, Docker, Kubernetes, logs, metrics, controlled changes and repeatable tests.

WHERE I FIT

Problems spanning device, network, media, service and infrastructure boundaries.

01 / THE WORKWork →

I work across four connected areas.

Connected products rarely fail according to an org chart. Firmware timing can surface as audio quality. SIP can succeed while RTP fails. A container can be running while its service remains unusable. I follow the actual data path until the failure makes sense.

IoT & Embedded Systems: ESP32-S3, ESP-IDF/ADF, audio codecs, I2S/I2C, connectivity, provisioning, OTA, controls and board bring-up.

VoIP & Real-Time Communications: SIP, SDP, RTP, Asterisk, FreeSWITCH, OpenSIPS, Drachtio, PBX, SIP trunks, routing and media-path debugging.

Linux, Containers & Infrastructure: Linux, Docker, Kubernetes, ingress, observability, service health, logging, dependencies and recovery.

02 / WORKING STYLEServices →
01

Frame the system

Map boundaries, clocks, dependencies, data paths and the exact failure before changing behavior.

02

Make it observable

Collect the evidence the system already has: logs, packets, timing, state, metrics and hardware behavior.

03

Isolate one boundary

Preserve a known-good control and change one part of the path at a time.

04

Build and retest

Turn the hypothesis into the smallest useful change, then repeat the same failure test.

05

Leave a trail

Document architecture, verification and recovery so the system is easier to operate after the fix.

03 / WHERE I CAN TAKE OWNERSHIP
01

IoT & Embedded Systems

Connected-device development from ESP32 firmware and hardware interfaces to connectivity, provisioning, telemetry and OTA lifecycle.

02

VoIP & Real-Time Communications

SIP/RTP systems from endpoint behavior through PBX, SIP trunking, routing and media paths, including failures that only appear during real calls.

03

Linux, Containers & Infrastructure

Linux services and containerized workloads with Docker and Kubernetes, supported by clear ingress, health checks, observability and recovery paths.

04

Technical Writing & Research

Research, technical explainers, system documentation and evidence-based writing about engineering, science and technology.

A FEW THINGS I CARE ABOUT

01 Preserve a working state before “improving” it.

02 Make the system observable before tuning it.

03 Separate confirmed facts from assumptions.

04 Reproduce the same failure after the fix.

05 Leave documentation that survives the person who wrote it.

THE SHORT VERSION

I build, debug and explain systems that cross boundaries.

If you want to understand the kind of problems that means in practice, the case studies are the best place to start.

Quick navigationEsc