I got into tech during the COVID lockdown in 2020, starting with content writing and SEO before getting into WordPress. That became my foundation and gave me my first real experience building and managing websites.

As I worked on more WordPress projects, I started running into limitations with themes, plugins, and how much control I had over what I could build. I wanted more flexibility and the ability to build things exactly the way I wanted, so in 2021, I started learning frontend development and moved deeper into software engineering.

Over time, that naturally expanded beyond the frontend. Building complete products meant I needed to understand APIs, databases, authentication, backend systems, infrastructure, deployments, and how everything connects.

Over the past 5+ years, I've worked on projects across EdTech, eCommerce, Web3, non-profits, SaaS, and other business platforms. Some have been relatively straightforward websites, while others have involved mobile apps, APIs, authentication systems, real-time features, admin platforms, databases, infrastructure, and production deployments.

These days, I'd describe myself as a frontend-leaning full-stack engineer. I care a lot about good interfaces, but I also want to understand what is happening behind them.

I can't publicly show everything I've worked on, but you can see some of my work here, ranging from CMS and eCommerce projects to fully custom web and mobile applications.

A lot of my work starts before I write any code.

I spend a good amount of time understanding the spec, asking questions, identifying edge cases, and figuring out what actually needs to be built. I also like explaining technical decisions clearly, especially when I'm working with founders or clients who aren't engineers.

Once the direction is clear, I move into architecture and implementation.

I use AI heavily in my development workflow, but I don't treat it as a replacement for engineering knowledge. For me, it's more like a very fast pair programmer. The quality of what it produces still depends on the context, constraints, architecture, and direction I give it.

That's why context engineering has become a big part of how I work. I'd rather spend time giving an AI agent the right context upfront than burn time going back and forth fixing code that was built on the wrong assumptions.

From there, it's implementation, testing, reviewing edge cases, and making sure what we built actually works properly in production.

When I'm not coding, I'm probably indoors surfing the internet, watching one of my favorite YouTube shows, or playing the piano.

I'm definitely a homebody, although I do go outside and touch grass once in a while.

I'm currently open to freelance projects and full-time opportunities, either remote or hybrid.

That could mean joining an engineering team, building a product from scratch, improving an existing application, fixing performance or architecture problems, or helping take an MVP to the next stage.

And if you're a non-technical founder who built an MVP with AI and it somehow works, but you're now worried about the architecture, security, scalability, or what exactly is happening under the hood, I can help with that too.

Let's talk.