I'm a backend & systems engineer building production infrastructure for railway safety and monitoring — the kind of systems that run 24/7 on edge hardware in the field and can't afford to fall over.
Day to day that means:
- Real-time signaling & sensor diagnostics — parsing binary packets off serial links, GSM/LTE modems, and RTUs, then turning noisy field data into actionable alarms.
- Distributed acoustic sensing (DAS) pipelines — signal processing + ML to tell an elephant apart from a passing train.
- Time-series data at scale — multi-TB PostgreSQL (partitioning, query planning, HA), plus VictoriaMetrics + Grafana for monitoring the monitors.
- Linux daemons & edge systems — systemd, IRQ/serial debugging, iptables, Docker networking, and license enforcement bound to the hardware itself.
- Concurrent Go services — gRPC, WebSockets, and MQTT/Kafka/NATS message plumbing holding it all together.
I like working close to the metal — where a bug is a race condition or a dropped packet, not a missing semicolon.
- Systems & low-level programming — currently learning Rust and poking at embedded.
- Signal processing & ML/DL — mostly through vibe coding, but the models ship. 🎛️
- Databases done right — Postgres internals, HA, and squeezing seconds off slow queries.
- Content creation — writing & videos on backend and production engineering.
Strong — Go · PostgreSQL · Docker · Linux | Comfortable — Python · Flutter · Redis · Kafka/NATS/MQTT · gRPC · VictoriaMetrics/Grafana | Learning — Zig · Kubernetes | Vibing — Signal Processing · ML/DL
Building infrastructure that runs quietly in the background — the way good systems should.