About
i'm an engineer — of the built world, by training; and of software, by trade.
A little about the path from one to the other.
I trained first as an engineer of the built world, and later became an engineer in software. What connects the two for me is structure: how things are designed, how they hold together, and whether they actually serve the people they are for.
In software, that has meant a steady interest in systems, interfaces, and the layers in between. I most recently spent four years at SmileID building out the web strategy: starting from a single component, moving to an iframe-powered embed, and eventually helping shape a no-code self-serve solution called SmileLinks.
I also worked on some of the APIs that power the SmileID system, and on the customer dashboard application itself. The work changed shape from project to project, but the through-line stayed the same: make the system clearer, make the interface more useful, and make the whole thing easier for people to work with.
More broadly, I care about tools that are well-structured, legible, and humane. I like systems that do their job without making themselves the centre of attention.