A construction technology director is hired to change how project teams work, not to buy tools. The seat needs someone with enough field and estimating credibility to be believed by superintendents, authority to retire systems, and a measure based on use. Contractors who hire a technologist to manage software usually get more software.
Somewhere in your company is a spreadsheet that runs a department. Everyone knows about it. The estimating platform you paid for exports into it, the project management system is updated from it on Fridays, and the one person who understands its macros has not taken a full week off in three years. A technology director is supposed to be the answer to that spreadsheet. Whether the hire works depends on a question most job descriptions never ask.
What does a construction technology director actually do?
Decides which systems the company runs its work on, makes the data pass between them, and gets project teams to use them the same way. Selection is a few weeks of the job. Getting consistent use across forty projects is the remaining years of it.
The scope usually covers the estimating platform, project management and document control, scheduling, field tools for daily reports and safety, the connection to accounting, and increasingly the models and reality capture that a VDC leader produces. Security sits nearby: contractors hold owner drawings, bank account information and bid numbers, and the federal cybersecurity agency publishes guidance that applies to a builder as much as to a bank.
The cost of systems that do not talk to each other has been measured. A NIST study of the US capital facilities industry put the annual cost of inadequate interoperability at $15.8 billion, much of it people re-entering and checking information that already existed elsewhere. The study is two decades old. The spreadsheet in your company suggests the finding has aged well.
Why do technology director hires disappoint?
Because the company hired for knowledge of software and the job turned out to be persuasion. A capable technologist with no standing among superintendents and estimators can configure anything and change nothing. Tools get installed, a few enthusiasts use them, and the old habits carry on underneath.
The gap is easy to measure, though few firms do. Suppose a contractor pays for 120 seats of a field management platform and 45 people open it in a typical week. The software is working. The implementation has reached fewer than four in ten of the people it was bought for. In the field, the standard for how a site is run is set by the general superintendent, so that is the first person a new director needs on side. Budget the onboarding timeline for that: a senior hire pays back at the end of the first full cycle they own, not at day 90.
There is a second, quieter failure. Tools tend to automate the part of the work that was already fast. Estimating shows it most clearly: pricing a defined scope has never been the slow step, and software now does it faster still. Working out what the scope actually is, from incomplete drawings and a narrative, remains the slow part, and no product has taken it over. A director who understands that will spend the budget differently from one who believes the demonstration.
Which background makes a credible technology director?
Operations first, technology second. The strongest candidates have run projects or estimates, became the person their colleagues asked about systems, and then took that role formally. They speak to a superintendent as someone who has filled in a daily report at six in the evening.
| Background | What they bring | What to check |
|---|---|---|
| Project manager or engineer turned technologist | Credibility with teams, knows the workflow | Can they hold a vendor to account on integration? |
| Estimator turned technologist | Understands data structure and cost codes | Have they worked with the field? |
| VDC or BIM lead | Strong on models and coordination | Do they see past the model to cost and schedule? |
| Corporate IT manager | Security, infrastructure, vendor management | Have they ever changed how a jobsite works? |
| Software vendor’s implementation staff | Deep product knowledge | Loyalty to one product; no line authority experience |
None of these backgrounds disqualifies anyone. The table points to the question each candidate has to answer. For the IT manager it is whether a project team ever did something differently because of them. For the vendor alumnus it is whether they would recommend removing their old employer’s product.
Pay does not map neatly onto a published category. The Bureau of Labor Statistics data for information systems managers is one reference and construction manager pay is another; the seat usually lands between them, with a premium in markets such as Dallas and Atlanta where large contractors compete for the few people who combine both.
How should the role be set up to succeed?
With authority to remove tools as well as add them, a reporting line into operations, and a scorecard built on use and rework avoided. A director who can only recommend will produce a strategy document. One who can switch off the old system on a named date will produce change.
Before the search starts, settle these:
- Who the seat reports to. The chief operating officer or president, in most firms. Our note on a chief operating officer covers how that seat carries change.
- What gets retired. Name two systems or spreadsheets the company is prepared to end. If none can be named, the role has no mandate.
- How success is counted. Weekly active use by project, duplicate entry removed, time from field event to cost report.
- Who owns the data standards. Cost codes and project setup rules decide whether anything integrates.
- How much field time the role spends. A director who visits a jobsite once a quarter is designing for a company that does not exist.
Budget follows from that list. Licenses are the visible cost. Training time, and the months when teams run slower on a new system, are the larger one, and candidates who have done this before will ask about it in the first interview. Estimating usually feels that slowdown first, so agree the rollout dates with your preconstruction director, who decides what the estimating team can carry in a bid season.
Who should not create this seat yet
- Firms where one platform would do. If the problem is that nobody finished implementing the system you own, hire an implementation lead for a year.
- Owners who will not back a mandate. A director overruled the first time a senior project executive objects will leave, and the good ones find out before accepting.
- Companies expecting headcount savings in year one. The early return is fewer errors and faster information, and the staffing effect comes later if at all.
- Anyone hiring to keep up with a competitor’s announcement. Their press release is not your problem.
When the seat does make sense, the search is usually sensitive: the candidate is employed by a competitor or a large subcontractor, and the incumbent arrangement inside your own firm often involves someone who expects the title. Selah Talent Partners is organized around that kind of search: confidential executive search for mandates that cannot be publicly posted, for contractors in Texas, the Southeast and across the United States. The employers page explains how to start, and our note on organization design may help before you do.
The spreadsheet will outlive every platform you buy until someone with authority understands why it exists: who built it, and what it does that nothing you paid for can. Hire the person who wants to know that before they recommend anything.
Sources and further reading
- NIST study, National Institute of Standards and Technology, cost of inadequate interoperability
- Cybersecurity agency, Cybersecurity and Infrastructure Security Agency
- Information systems managers, Bureau of Labor Statistics, occupational outlook