Mechanical Engineer (EIT) & Project Manager

Where I work best

I work best where the problem crosses boundaries: a construction detail that affects schedule, a workflow that keeps losing information, a physical part that has to fit the real object, or a technical issue that needs to make sense to people with different roles.

My background spans mechanical engineering, project management, construction coordination, process improvement, automation, and hands-on making. The common thread is the habit of finding the real constraint, making it understandable, and carrying the solution far enough that someone else can use it.

I am comfortable moving between drawings, job sites, spreadsheets, CAD models, automations, field conditions, contractors, tenants, owners, and users. I like the point where the clean plan meets the messy reality, because that is where most useful work happens.

I also work comfortably with AI-assisted tools, especially when they help move between research, writing, code, documentation, and decision-making. I do not treat AI as the work. I use it to move faster through the messy middle: testing ideas, finding structure, drafting options, checking assumptions, and turning scattered information into something usable.

Make it work. Make it usable. Make it make sense.

Good work should be buildable, explainable, and easier to hand off than it was when it started.

Sometimes that means redesigning a detail. Sometimes it means writing the process down. Sometimes it means asking the awkward question before it becomes an expensive problem.

This site is a record of that kind of work: projects where design, coordination, communication, and follow-through had to meet in the same place.

Background

My background combines a Bachelor of Engineering from UVic, a Mechanical Engineering Technologist diploma from Camosun College, a Commerce degree in Entrepreneurial Management from Royal Roads, and project management training through the Gustavson School of Business Executive Programs at UVic.

That mix fits the way I work: understand the technical system, deal with the field reality, keep the business context in view, and carry the work through to a usable handoff.