A Design Technology Director Owns What Your Practice Will Stamp

The Stair Core Passed Every Check Except the One Nobody Owned

The coordination model came back on a Tuesday with a stair core that resolved cleanly in the viewer and missed the local egress width. Three people had touched it. One generated layout variants with a plugin, one picked the variant that read best in section, one folded it into a set headed for permit. Nobody lied and nobody checked, because no written rule said whose job checking was.

That gap is the role. A Design Technology Director answers one question for every studio at once: which machine-produced output this practice is willing to put a seal on, and what has to happen to it first. Gensler's regional version of the seat reports to a global design technology director and to the regional managing principals, and the firm describes it as a leadership role centered on human enablement rather than as systems administration ¹.

Three traits separate a real one from a well-briefed tool enthusiast. The first is a bias toward the failure rather than the demo. Generated automation in Revit fails in a particular, boring way: a script references a node that is not in the installed package set, reads as correct in the transcript, and then breaks or misbehaves quietly inside the model. A strong candidate opens with that class of problem unprompted, and can name a package version it happened on. A weak one describes time saved.

The second is that they have refused something. Ask what they killed, and listen for the specifics: which tool, which project, which principal disagreed, what happened next. Somebody who has run adoption for three years and never blocked a deliverable has either had extraordinary luck or has been overruled quietly every time, and the second is far more common.

The third is enablement instinct. Ask how a new tool reaches a project architect who is already two weeks behind. Real answers involve a pilot team, a template, office hours and a written fallback for the day the plugin breaks. Performed answers involve a launch email and a license count. The boundary worth naming in the same conversation is with the computational design and automation specialist, who builds the scripts this director decides to trust.

Which Backgrounds Produce a Director Who Can Refuse a Drawing?

The obvious feeder is BIM management, and it is the right one. A BIM manager has spent years owning model standards, arguing about families and worksets, and being the person a project lead complains to when the standard costs a day. That is most of the political craft. What such a candidate usually lacks is the reflex to treat generated output as a claim needing verification rather than a file needing cleanup.

The second feeder is computational design: people who came up through Grasshopper, Dynamo and a scripting habit. They understand exactly how the automation breaks, which makes their skepticism cheap and reliable. The risk with this profile is the opposite one. They will build rather than standardize, and a practice ends up with brilliant tooling only its author can maintain. Screen for whether they have ever handed something they wrote to a person who did not want it.

The unexpected feeder is the specification writer. Specs are the discipline a practice already has for writing down what is acceptable, in enforceable language, with a named responsible party. Someone who has spent a decade drafting sections and defending them in submittal review already thinks in terms of what gets verified by whom before it leaves the office. Point that person at a model-generation workflow and the transfer is faster than it looks.

Two more worth calling: construction administration architects, who have watched what happens downstream when a drawing was optimistic, and VDC managers from the contractor side, who arrive with a low tolerance for geometry that coordinates on screen and not in the field.

One profile reads well and often disappoints. A pure IT or systems administrator can run the deployment cleanly and cannot judge a drawing, so every substantive call gets escalated back to a principal who does not have time for it. Licensure is not strictly required, but the role needs someone whose judgment about a set carries weight in a room full of licensed architects.

Ask How This Director Got Good at Catching a Confident Wrong Answer

Ask directly how they got good at working with these tools, and listen for a specific failure rather than a course. The answers worth hearing are concrete: an assistant produced a Dynamo graph that looked right and called a node that was not installed, or cited a code section that did not say what the summary claimed. They can name the claim, how it fell apart, and the check they have run ever since.

Good answers share a shape. Someone runs the same generation several times to see the spread before trusting any single output, because one plausible result is not evidence and five near-identical ones are. Someone else asks the assistant for the source of the one claim the decision rests on, then opens the code or the manufacturer's document instead of accepting the summary. A third keeps a running file of cases where a model went sideways, which usually turns into the practice's first validation checklist.

The underlying skill is checking an assertion against something outside the conversation. A model states an occupancy classification; the director opens the adopted code. A tool reports that a family has been swapped across four hundred instances; the director schedules the parameter and counts. This habit describes badly in an interview, because the vocabulary is easy to borrow and the practice is not.

So do not run the whole assessment as a conversation. Give a candidate a real, small mess from your own office: a script somebody generated last quarter, a model with a known coordination error, ninety minutes, and the assistant of their choice. Watch what they verify first and what they take on faith. The gap between people who can do this work and people who can talk about it shows up in the first twenty minutes, and it never shows up in a résumé. That evaluation discipline is close to what an autonomy evaluation operations manager does full time in a different industry.

Where Do You Find One While the Title Is Still Forming?

Look inside the practice first. In most firms the person already doing a third of this job is a BIM manager or a senior associate with a scripting habit, known to every studio, currently unpaid for the standard-setting they do informally. Promoting that person costs less than a search and skips the year it takes an outsider to learn which principals can be told no.

Outside, the venues are real and long-standing. The AIA's Technology in Architectural Practice knowledge community, BILT conferences, Autodesk University, and the Dynamo and Grasshopper forums are where these people have been visible for a decade. Contractor VDC teams are an underused pool. So are technical artists from game and film pipelines, who have spent careers making a toolchain reliable for people who did not build it, though they will need time to learn what a permit set is.

The title itself is still settling, which cuts both ways. An Indeed search under design technology director and adjacent names returns thousands of listings, so search volume is not the problem ¹. That is a count of what a search-results page matched rather than a count of this seat, which is itself the point. Scope is the problem. Two people with the same title may be running a help desk and running a firm-wide standard, so read the reporting line before the résumé: a director who reports to IT is doing the old job, and one who reports to the managing principals is doing this one.

Closing the hire turns on authority rather than on tooling budget. The candidates worth having will ask, in the first call, whether they can stop a set from going out. Have a real answer ready, and name the meeting where that gets decided and who chairs it. Two more things close it: a training budget with hours attached rather than licenses, and one named pilot project with a principal who has already agreed to be the first to work differently. Without that last item the role becomes advisory within a quarter, and the good ones have seen that happen before.

What Does the Role Pay, and Does It Need a Desk in the Studio?

No wage series covers this title, and nothing found for this piece prices it credibly, so this stays qualitative on purpose. A dollar figure quoted for a category still forming is a guess wearing a benchmark's clothes. Price it internally: the seat hires against your senior associate or studio director band when it carries firm-wide standard-setting authority, and against a technical lead band when it is mostly tooling support.

Where the person also builds and maintains automation, you will be competing with software employers rather than with other practices, and that is a different band entirely.

One macro signal is worth carrying into the compensation conversation without over-reading it. PwC's 2026 AI Jobs Barometer reports an average wage premium of 62 percent for roles advertising AI skills across roughly one billion job ads ². That is an economy-wide average across every occupation, not a number for this title, and it should inform your expectations rather than your offer letter.

On location, the standards work travels and the adoption work does not. Writing the validation rule, evaluating a plugin and maintaining templates are all remote-friendly. Changing how a project architect works is not, and directors who never sit in the studio end up publishing standards nobody follows. Most practices land on a hybrid with a real presence in each office on a rotation, plus site visits for anyone whose judgment about constructability is supposed to carry weight.

On-premise pressure comes from three places: model files large enough that latency decides whether a tool gets used, client confidentiality clauses on government, defense and healthcare work, and firms that will not send project data to a hosted model at all. Settle that before the offer, because it decides which tools are even on the table.

One legal flag, offered as a flag and not as advice. Architectural licensure and the duties attached to sealing documents are set state by state in the United States and vary by jurisdiction elsewhere, and responsibility for a sealed document does not move because a tool produced part of it. Separately, professional liability carriers have begun asking how firms govern generative tools, and those questions are still changing through 2026. Read the primary source for your jurisdiction and check with counsel and your carrier rather than reasoning from a summary. The same posture applies in regulated hardware, where a notified body AI conformity assessor does this work as the whole job.

See a sample report >