The Design Technologist: Part Architect, Part Developer, Part Systems Builder
For a long time, the creative and technical worlds operated in silos. Architects designed the buildings, engineers calculated the loads. Designers created the UI mockups, developers wrote the React components.
But as the tools of creation—from Revit to Next.js to AI—have become more complex and deeply intertwined, a new role has emerged: The Design Technologist.
What is a Design Technologist?
A Design Technologist is someone who refuses to hand off the execution. They don't just draw the blueprint; they build the machine that builds the blueprint.
In my career, this has manifested across three distinct phases:
- Architecture: Instead of manually drafting 50 wall sections, I learned to write Dynamo scripts to automate the documentation of parametric Revit models.
- Media: Instead of manually scrubbing 3,000 BMX videos, I built a C++ and Python computer vision pipeline to index them.
- Software/AI: Instead of just prompting ChatGPT to write code, I build local MCP servers with 63 custom endpoints so the AI can execute the work autonomously.
Bridging the Gap
The true value of a Design Technologist isn't being the best structural engineer or the best C++ programmer in the room. It's being the only person who speaks both languages fluently enough to build the bridge between them.
When an architecture firm wants to implement AI for clash detection (as detailed in my AEC Conflict Finder post), a pure software engineer will fail because they don't understand how to read an RCP. A pure architect will fail because they don't know how to train a YOLO model.
The Design Technologist lives in the overlap.
The Future is Agentic
We are moving into an era where AI agents will handle the raw production of code, imagery, and 3D geometry. In this world, the most valuable skill isn't knowing the exact syntax of a Python function. It's knowing how to design the system—the architecture of how these agents communicate, access data, and verify their own work.
The future of software development looks a lot like the history of architectural design: you define the constraints, you design the systems, and you orchestrate the execution.