01 // journey :: system log
A career, read as a control system.
Every chapter is a feedback loop: sense the system, close the loop, scale what holds. From physical machines to the machinery of organizations — replayed below in order.
LOOP-00
origin
Learning to think in whole machines.
Mechatronic Engineering teaches you to think about the whole machine: sensors, signals, control loops, and the inconvenient physics in between. Nothing works in isolation, and the failure is always at an interface.
LOOP-01
signal
The machines became organizations.
I carried the whole-machine habit into data and software, where the machines are organizations and the control loops are pipelines, workflows, and decisions. The physics got softer; the interfaces stayed inconvenient.
LOOP-02
build
Connecting fragmented tools into operating systems.
As a Senior Data & Automation Engineer, I built data pipelines, integration services, and process automation that connected fragmented tools into reliable operating systems for cross-functional teams — and learned which systems survive their builders.
LOOP-03
scale
Platforms, programs, and the teams behind them.
Today, as Data, AI & Automation Engineering Lead, the loop runs at enterprise scale: data platform architecture, AI adoption with governance and workflow fit, automation programs designed as capabilities, and executive reporting that boards can trust.
LOOP-04
mission
Systems that reach communities, not just dashboards.
The systems I architect power large-scale civic and climate engagement. Enterprise architecture is a means; durable human outcomes are the end. Built remote-first, across time zones — where "resourceful" is an engineering methodology, not a buzzword.
LOOP-05
trajectory
The chief-track: loop still open.
The current chapter is deliberate: deepening board-level fluency in strategy, capital allocation, and organizational design — building toward Chief-level data & AI leadership.
02 // next loop