My background isn't traditional software engineering. Before I started building automation systems, I spent years learning brand strategy and business thinking, and that's shaped how I approach this work now.

I don't start with the tech. I start with questions. Where is time getting wasted. Which tasks are repetitive. What would actually move the needle if it ran itself. Once I've got a clear answer, I design a workflow that fits the business instead of forcing a generic template on it.

Today I build AI-powered automation with n8n, connecting APIs, databases, and language models into systems that save real time and cut real busywork.

I'm also building in public, sharing what I'm learning and what I'm shipping as I go. That habit has sharpened how I explain technical work to people who aren't technical, which turns out to matter just as much as the build itself.