I began my career as a CAD technician, immersed in Revit, Rhino and AutoCAD, using them day in, day out for years. I built models, produced drawings, revised them, and repeated the process. It was valuable experience, but often repetitive and time-consuming, especially when implementing late-stage changes.
In 2014, I was introduced to the work of the computational design team at Ramboll. It fundamentally shifted my perspective. Curious to learn more, I searched online and discovered Dynamo, then at version 0.6.8. These were the early days: unstable, prone to crashing, and limited in capability. Yet even then, I could see its potential, not just to improve workflows, but to reshape how we approach structural engineering.
I quickly realised that while Dynamo wasn’t ideal for complex geometry generation, it was exceptionally powerful for manipulating and automating data within Revit. That led me to explore Grasshopper, where I became absorbed in parametric geometry and generative workflows. This was before the era of Rhino.Inside.Revit, so interoperability required creativity, using plugins like Hummingbird and analytical software as intermediaries to transfer models into Revit.
It wasn’t seamless, but it was transformative. It opened up new opportunities and pushed me to learn Python and C#, expanding my capability from visual scripting into full programming.
This skillset enabled me to contribute to a diverse range of projects:
-
Developing parametric models for the Discovery Building at the British Antarctic Survey.
-
Automating drawing production workflows for modular CLT housing schemes.
-
Creating a structural frame generator to compare embodied carbon across material options and grid configurations for an innovation district in Italy.
-
And many smaller process improvements that collectively saved significant time and improved design quality.
I loved working at the intersection of BIM, automation and structural design. However, I recognised that to push computational design further, particularly within structural engineering, I needed a deeper grounding in engineering fundamentals. I wanted to understand, rigorously, how to design steel and concrete members, foundations, and lateral stability systems, and to embed that engineering intelligence into the tools I was building.
After several years of day release at Kingston University, I achieved my degree. Alongside professional experience, it strengthened my understanding of structural analysis and design, materials, and engineering principles. Individually, these experiences shaped me as a technician, an engineer and a coder. Together, they enable me to operate in a hybrid role, bridging technical delivery, digital strategy and computational development within structural engineering.
At London Structures Lab, I contributed to the development of an in-house steel reuse tool for One Golden Lane. The project successfully reused 15 tonnes of steelwork from the existing site, alongside reclaimed steel from other locations. Beyond project-specific innovation, I also helped shape the practice’s BIM and digitalisation strategy.
In late 2025, I moved to Arup, where I have focused on advancing digital capability within the local team while aligning with the wider business strategy. My role includes contributing to digital execution plans, developing bespoke tools to meet project and regional needs, and acting as a catalyst for upskilling, sharing knowledge and embedding digital thinking across teams.
Looking back 12 years, building tools, shaping strategy and stepping away from a “traditional” engineering pathway felt uncertain. Today, it feels like a natural evolution. I’m not just following a predefined route, I’m helping define how technology and digital engineering integrate into structural practice.