My journey started in Seattle. Not just playing in bands, but building systems. Long before I touched a terminal, I was obsessed with the architecture of creativity. I spent my youth designing tabletop RPGs, drawing comics, and making home recordings in rain-soaked basements.

This wasn't just a hobby; it was an education in grit and iteration. Seattle taught me how to handle the "starving artist" grind. Not for the sake of the struggle, but to develop the discipline required to master a craft.

I moved to Berlin to push my musical career to its logical conclusion. I reached a level of professional maturity where I was leading international tours across the US and Europe, eventually receiving state funding in Germany to compose and record with a 10-piece ensemble.

Then came March 2020.

When the pandemic halted live performance, I didn't just look for a new job. I looked for a new medium. The hours I'd spent in audio engineering, managing signal flow, troubleshooting hardware, obsessing over precision, turned out to be the perfect precursor to software engineering. I completed a full-stack bootcamp, but the real growth happened in the thousands of hours of self-teaching that followed. I didn't want to build "pages"; I wanted to understand the infrastructure.

Today, based in Madrid, my work has entered a new phase. We've moved past the era of manual boilerplate and into the era of AI-native engineering. For many, the rise of AI assistants and autonomous agents is a threat. For me, it is the ultimate creative multiplier. It has removed the "manual notation" of coding, the syntax struggles, the boilerplate, allowing me to return to my roots as an arranger and orchestrator. In 2026, being a great engineer is about system taste and architectural rigor. I use AI not to replace my thinking, but to execute at a scale that was previously impossible for a single developer.

• Orchestrating Agents: Just as I once coordinated a 10-piece band, I now coordinate AI agents to handle unit tests, refactoring, and infrastructure scaffolding.
• Focus on Composition: With AI handling the "rhythm section" of routine tasks, I focus on the "melody": the UX-minded engineering, the product logic, and the high-level architecture.
• Creative Velocity: I am building more complex systems with more precision and less friction than ever before.

I build with an artist's eye for taste and an engineer's requirement for rigor.

• Frontend Architecture: React, TypeScript, Remix, Vite, Tailwind, Storybook
• Infrastructure & Data: Terraform, AWS, Postgres, GraphQL
• AI-Native Workflow: Agentic workflows and LLM-integrated development to maximize build velocity without sacrificing code quality

I believe non-traditional backgrounds produce the most resilient engineers. My years in music gave me a toolkit that a CS degree cannot replicate:

• Arrangement is Architecture: Arranging music for a large ensemble is exactly like designing a distributed system, managing many interdependent parts so they function as a cohesive whole.
• The Discipline of the Rehearsal: I treat a sprint like a rehearsal. Deliberate repetition, patience, and the understanding that "done" is better than "perfect," but "excellent" is the goal.
• Ego Management: Leading a band through a high-pressure tour teaches you how to collaborate, communicate, and solve problems when things go wrong.