Data center design is entering a particularly interesting period.
For years, the core challenge was designing facilities that could provide reliable power, cooling and connectivity at scale. Those fundamentals remain, but AI is changing the assumptions behind them.
Rack densities are increasing. Liquid cooling is moving further into mainstream data center design. Electrical systems are becoming more demanding. Developers are looking for ways to standardise and accelerate construction. Customers want capacity delivered faster, with enough flexibility to support technologies that may not even exist when the building is designed.
That creates a useful question for design professionals considering their next move:
Does your experience demonstrate that you can design the data centers the market is going to need next?
For candidates, there is a lot you can do to make the answer obvious.
Understand where the design brief is heading
Start with the fundamentals.
You should understand why AI is changing data center design rather than simply knowing that AI is driving demand.
Higher-density compute means more power concentrated into a smaller physical footprint. That creates consequences for electrical distribution, cooling, heat rejection, floor loading, redundancy, monitoring and ultimately the overall architecture of the facility.
Liquid cooling introduces another layer.
Design teams increasingly need to understand direct-to-chip cooling, coolant distribution, heat exchangers and the relationship between liquid and air cooling systems.
You don’t need to specialise in every emerging technology.
You should understand enough to have an intelligent conversation about how it affects the building.
That knowledge is becoming increasingly valuable.
Know the difference between designing a building and designing an infrastructure platform
Modern data centers are expected to evolve.
A facility may open with one generation of servers and be upgraded several times during its operating life.
That means flexibility matters.
Design professionals should understand concepts such as modularity, phased deployment, expandable electrical infrastructure and future cooling requirements.
Think about the lifecycle.
What happens when the customer wants another 20MW?
What happens when rack densities double?
What happens when the cooling technology changes?
What happens when a tenant wants to deploy liquid-cooled infrastructure?
A design that works beautifully on day one but creates major constraints three years later may not be particularly successful.
Employers increasingly need designers who think beyond the initial handover.
Build strong MEP knowledge
Data center design is inherently multidisciplinary.
Architectural, structural, electrical and mechanical decisions are closely connected.
That means having a strong understanding of your neighbouring disciplines can be extremely valuable.
If you’re an electrical designer, understand how your decisions affect mechanical systems.
If you’re mechanical, understand the electrical implications of your cooling strategy.
If you’re an architect, understand the infrastructure constraints that shape the building.
If you’re a structural engineer, understand what increasingly dense equipment and mechanical systems mean for the structure.
You don’t need to become a generalist.
You should become very good at collaborating with specialists.
Learn to design for constructability
A technically impressive design still has to be built.
This is particularly important in an industry where schedules are becoming increasingly aggressive.
Design teams need to understand how their decisions affect procurement, prefabrication, sequencing, installation and commissioning.
Construction experience can therefore be extremely valuable for a design professional.
If you’ve spent time on site, coordinated directly with contractors or worked through constructability reviews, highlight it.
Companies such as Gensler, Jacobs, AECOM, Arup and DPR all operate across different parts of the data center design and delivery ecosystem, although their specific roles and hiring requirements vary.
The broader lesson is useful for candidates: employers increasingly value people who understand how design decisions survive contact with a construction site.
Commissioning knowledge is a serious advantage
Commissioning should not be treated as something that happens at the end of the project.
Design decisions have a direct impact on how effectively a facility can be tested, commissioned and handed over.
A designer who understands commissioning can spot potential problems earlier.
That might involve equipment access, controls, redundancy, sequencing, isolation, testing requirements or maintainability.
If you have commissioning experience, make it prominent.
If you haven’t, learn how the process works.
Understanding the journey from design through construction, commissioning and operations gives you a much broader perspective.
It also makes you more useful to multidisciplinary teams.
Become comfortable with BIM and digital design
Digital design tools are now fundamental to large-scale data center projects.
BIM coordination, clash detection, digital twins and increasingly sophisticated modelling processes can have a significant impact on project delivery.
If you work in design and haven’t invested in these skills recently, it is worth looking at where your capabilities sit.
The important question isn’t simply whether you know a particular software package.
It is whether you can use digital tools to improve coordination, identify problems and communicate design intent.
Employers are looking for people who can operate effectively within increasingly digital project environments.
Understand standardisation
One of the major themes in data center construction is repeatability.
Developers and operators are looking to standardise designs where possible.
The reasons are fairly straightforward.
A repeatable design can reduce engineering time, simplify procurement, improve quality and accelerate delivery.
That doesn’t mean every data center will look identical.
It means designers need to understand when standardisation makes sense and when a project genuinely requires something different.
Experience with modular design, repeatable electrical or mechanical systems and standardised design packages can therefore be useful.
If you have helped create a design that was subsequently replicated across multiple facilities, that is worth highlighting.
Think about the developer’s perspective
A design professional can become more commercially valuable by understanding what the developer is trying to achieve.
Every design decision has consequences.
More equipment can mean more capital expenditure.
A larger mechanical plant may increase capacity but consume additional space.
A particular cooling approach may support higher density but require different infrastructure.
A design change late in the project can affect procurement and schedule.
Understanding those trade-offs helps you communicate with clients and project leadership.
You don’t need to become a developer.
You should understand enough about development economics to know why the client cares about your design decisions.
Make AI part of your professional development
You don’t need to become an AI hardware expert.
You should understand the infrastructure requirements associated with AI workloads.
Learn the basics of:
• GPU infrastructure
• High-performance computing
• Rack density
• Direct-to-chip liquid cooling
• Heat rejection
• High-density electrical distribution
• Power usage
• Network requirements
• Future expansion
Follow what companies such as NVIDIA, Vertiv, Schneider Electric and Eaton are doing.
Their technology developments can provide useful clues about where facility design is heading.
The more closely you understand the technology driving your client’s requirements, the better prepared you’ll be to design around it.
Choose employers for the project exposure
When considering a new role, look beyond the company name.
Ask what projects you will actually work on.
Will you be designing hyperscale facilities?
AI campuses?
Colocation?
High-density environments?
Retrofits?
New builds?
Will you have exposure to different markets?
Will you work directly with developers?
Will you interact with construction teams?
Will you see your designs through commissioning?
The answer can have a major impact on the value of the experience you gain.
A role that gives you responsibility across an entire project lifecycle may be more valuable than one that offers a more impressive title but keeps you within a narrow design discipline.
Make your CV technically specific
Design CVs often become lists of software and responsibilities.
That doesn’t tell the whole story.
Include the project details that demonstrate scale and complexity.
• MW capacity
• Square footage
• Facility type
• Electrical capacity
• Cooling strategy
• Rack density
• Project value
• Design stage
• Your discipline
• Your specific responsibilities
• Construction involvement
• Commissioning involvement
• Client exposure
Compare:
“Designed electrical systems for data center projects.”
with:
“Led electrical design for a 60MW hyperscale campus, coordinating medium-voltage distribution, UPS, generator and switchgear systems through detailed design and construction.”
The second version immediately gives an employer something to evaluate.
Build experience across the lifecycle
If you have only worked in early-stage design, look for opportunities to see what happens afterwards.
If you’ve only worked on construction documents, seek exposure to concept design.
If you have never been involved in commissioning, volunteer for it.
If you’ve only worked on new builds, consider learning about live-site upgrades.
Breadth matters.
A designer who understands the full journey from site selection through design, construction, commissioning and operations can communicate with considerably more confidence.
That makes you valuable in multidisciplinary organisations.
Consider where your career could go next
Design can lead in several directions.
Technical leadership.
Design management.
Engineering management.
Project management.
Development.
Consulting.
Owner-side technical roles.
Some of those paths require deeper technical specialisation. Others reward broader commercial and project experience.
Your next move should reflect the direction you want to take.
If you want to become a technical authority, pursue increasingly complex systems and specialist knowledge.
If you want to move towards design management, build coordination, client and commercial experience.
If development interests you, start learning about power, land, permitting and project economics.
Don’t wait until you’re ready for the next job title to start developing the skills that job requires.
What would I focus on?
If I were a design professional looking for my next data center role today, I’d prioritise five areas.
High-density infrastructure. Understand what AI is doing to power and cooling.
Multidisciplinary capability. Know how your decisions affect the rest of the project.
Constructability. Understand how your designs will actually be delivered.
Digital design. Stay current with BIM, coordination and emerging digital tools.
Lifecycle experience. Get exposure to design, construction, commissioning and operations.
There is a huge amount of data center design work ahead.
The industry will need specialists, but it will also need designers who can connect those specialisms.
The most interesting opportunities may go to people who can look at a set of drawings and understand not only whether the design works, but how it will be built, commissioned, operated, expanded and eventually adapted to whatever comes next.
That is a valuable skill in any market.
It could become an especially valuable one in data centers.