I've been building for the web for over twenty years, starting while I was studying physics and computing at Queen's University. That background still shapes how I work. I look for the underlying system before I write code: how the data should be modelled, where the boundaries between services belong, and which decisions will be expensive to undo later. Most recently I was Lead Developer at a Vancouver creative agency. I set the technical direction across more than twenty client projects, designing content architectures, relational data models and custom integrations that connect separate platforms into systems that run themselves.
The work I'm proudest of is taking messy operational problems and turning them into something reliable. That usually means sitting down with the people who actually run the business, understanding their workflow better than they expect me to, and then designing a solution simple enough to maintain long after I've moved on. I care a lot about the parts of engineering that don't show up in a demo, like consistent standards, readable code, accessible interfaces and sensible defaults. I've also carried the infrastructure side: identity and access management, device fleets, security tooling and the everyday IT that keeps a team productive.
I'm most useful where engineering meets people: working with designers, strategists and clients, mentoring less experienced developers, and explaining technical trade-offs to non-technical stakeholders so good decisions get made early. I keep learning on purpose, and my current side project is a full-stack TypeScript app that pulls public environmental model data into a real product. I'm looking for a team that values that mix of hands-on building, systems thinking and clear communication.