What's a Design Technologist?
I've had two Design Technologist roles now. Let's talk about what each has meant.
last edited: 5/14/2024
Writing state: concept
I've had two Design Technologist roles now. Let's talk about what each has meant.
last edited: 5/14/2024
Writing state: concept
Design Technologist - I've had this job title twice now: my current role at var(--some-job-board, LinkedIn)
can lead to even more different different DT roles. I'm looking to clear that up a little bit here - provide some background to what I did/am doing at my Design Technologist role at least.
At Square, my role can be thought of similarly to what I discussed in my
Generally though, as DTs at Square, we sit within the Design Org and work directly with brand creative teams to create web experiences (and emails though that responsibility is lessening as our PMMs move towards WYSIWIG email builders using DT-build email design systems) describing and marketing the various products that Square - or really
I've been involved very deeply within the design process for some projects - such as
I've also been brought in much too late on other projects - the
I guess this is my long way of saying that, as a Design Technologist as Square, my role is narrow in one sense: craft beautiful web experiences. But it is also broad in another: we are also designers and educators. When used to our fullest, we are asked to bring our own design ideas to the table, educating/guiding our designers and pushing them further to the boundaries of what is possible on the modern web.
My experience at EvolveLAB was much different though it may be familiar to those involved with Technology at architecture and engineering firms. While it is true that I got my frontend engineering start there - at least in a professional sense - my role went far beyond the web. In fact, it was not until relatively late that I got into engineering web applications and web-based frontends. This role was linked much more closely with my
My role at EvolveLAB started at a much more basic level: I was tasked with building out Revit families. It was not glamorous work but, at that time, EvolveLAB was just starting to dip its toe in the water of software engineering. A few sets of Revit families - casework, windows, and doors if I recall correctly - were what was paying the bills back then.
I was able to quickly move into more complex roles. At that time, when software building for me was at the hobbyist level of watching online courses, "complex roles" meant pushing the boundaries of Grasshopper and Dynamo. I made quite a few scripts for clients. I very much enjoyed the work. I'm not sure that I would as much now. Not when I can just as easily write code. But back then, it was great work. It allowed me to slowly dip my toe in the water of software engineering.
My first professional coding experiences, I'm not counting a couple scripts I wrote for small web projects we took on at
We quickly leveled up from there. I joined a small group of EvolveLAB-ers that were building a much more complex mini-application - okay fine, it was just a very complex Revit plugin but still - for a Michigan-based metal panel manufactuer. That code was also... not great... But we learned a lot and leveled up quickly as we worked. This experience really got me ready to lead a generative design, web application we built for an architecture firm client. It was my first professional web app and it opened a lot of doors. I built the first UI for