About
An evolution in altitude
The path here was not a straight line of accumulating skills. It was a series of shifts in what 'good' means - each role changing the altitude at which the work happens.
The journey
From building systems to designing how they decide
- 01
Mechanical Engineer
Learning to see systems
Began in mechanical engineering - the discipline of tolerances, load paths, and failure modes. It taught a way of seeing the world as systems with constraints, long before any of it touched software.
- 02
SAP Consultant
Learning the enterprise
Moved into enterprise systems as an SAP consultant, working inside the processes that large organizations actually run on. This was the first encounter with how enterprises decide, govern, and resist change.
- 03
Backend Engineer
Learning the machine
Crossed into software through the systems beneath the surface: data, services, reliability, and the contracts that hold distributed systems together.
- 04
Full Stack Engineer
Learning the whole
Held the whole system at once - surface to storage. Seeing end to end is where the architectural instinct starts: understanding how a decision at one layer constrains every other.
- 05
Data Warehouse Engineer
Learning where truth lives
Built the foundations where data becomes truth - pipelines, models, and the warehouse that turns scattered records into something an organization can decide from. Architecture is only as honest as the data beneath it.
- 06
Gen AI Solution Consultant
Learning a new material
Worked with generative AI as a new material - shaping models into solutions and learning where intelligence genuinely fits and where it doesn't. The hard part was never the model; it was the judgment built around it.
- 07
Deployment Specialist
Learning what survives contact
Took systems the last mile - into production, where design meets reality and only what has been hardened survives. Shipping teaches what no diagram does: a system isn't real until it runs where it matters.
- 08
Systems Thinker
Learning to design the constraints
The shift from building within constraints to designing them. From asking "how do I build this correctly" to "what system should exist, and what must it protect?"
- 09
Founding Architect
Designing first principles
The role today: designing the first principles, decision systems, and governance an organization is built on - and building the frameworks and systems that let others do the same.
Why this matters
The point was never the skills. It was learning to operate at the altitude where the constraints themselves are designed.
Building systems that capture, preserve, and amplify human judgment at enterprise scale.