Who I am
I work at the intersection of technical capability, operational reality, and institutional pressure. I am interested in what happens after the architecture diagram: the data semantics, the failure states, the controls, the evidence, and the decisions that make a system trustworthy.
Across approximately seven years, I have worked across the procurement, evaluation, and delivery phases of cybersecurity and infrastructure engagements. That experience taught me how regulated systems are bought, defended, documented, and challenged. My personal projects let me go further: from the operational model and API contract to the frontend control surface and the evidence needed to know whether the system is actually working.
I came into this work from a commercial angle, which shaped how I read technical proposals and vendor claims. I prefer solutions whose value can be clearly articulated—not only to engineers, but also to the decision-makers who own the outcome.
My direction is toward advisory and management roles. Not away from technical depth, but toward positions where that depth serves broader organizational judgment. I am interested in environments where structured thinking, accountability, and clear communication are treated as competitive advantages.
The international dimension is deliberate. Canada and Germany represent operating cultures—documentation-first, compliance-aware, governance-oriented—that align closely with how I already work. I am open to relocation and to remote-first, distributed teams.