Lost in Translation. Why overly technical job specs are killing your Enterprise Architecture hires
Hiring for EA roles is a challenge. On paper, it seems straightforward . . “Find someone with the right skills to align your business goals with your tech stack”.
But here’s where many organisations fumble. They treat EA like it’s just another IT role, plastering job specs with hyper technical requirements that alienate the very talent they need most.
If you’re guilty of this, don’t worry . . you’re not alone. But it is time to fix it.
What does an Enterprise Architect ACTUALLY do?
Enterprise Architects aren’t just techies. They’re strategists, communicators, and leaders.
They’re the bridge between your business strategy and your technology execution. Sure, they need to understand the tech, but their primary focus is:
Strategic thinking:
Aligning IT roadmaps with your organisation’s goals.
Communication skills:
Translating complex tech jargon into something non-technical stakeholders can actually understand.
Collaboration and leadership:
Bringing teams together to drive transformational change.
They’re the people who connect dots, solve puzzles, and make sure your IT doesn’t just work . . it works for you.
The danger of overly technical job specs
Now let’s talk about what happens when you focus too much on technical expertise in your job descriptions.
You scare off the strategic thinkers:
Those business-savvy Architects who thrive on aligning tech with goals? They’re rolling their eyes at your laundry list of coding languages and niche software. You’re essentially telling them, “We’re not looking for someone like you.”
You attract the WRONG Candidates:
Developers and Solution Architects with deep technical skills might tick all the boxes on your spec, but do they have the strategic vision or business acumen to drive enterprise-wide change? Probably not.
You forget the soft skills:
EA is a people game. Leadership, negotiation, and clear communication are non-negotiable for success in this role. Yet, these crucial qualities are often missing from overly technical job specs.
How to write better EA job descriptions
Here’s the good news. Fixing your job specs is easier than you think. A few tweaks can make all the difference:
Lead with Strategy, NOT Tech
Focus on what really matters . . aligning IT with business goals. For example;
“Collaborate with senior leaders to define and implement IT strategies that drive organisational growth.”
Ditch the niche tech talk
Instead of demanding mastery of niche tools or coding languages, highlight broad technical expertise. For example;
“Experience managing complex IT ecosystems and delivering strategic solutions.”
Showcase leadership and communication
Make it clear that this role is about influence, not just implementation. For example;
“Demonstrated ability to lead cross-functional teams and communicate effectively with technical and non-technical stakeholders.”
Think BEYOND titles and tenure
Years of experience in a specific role doesn’t guarantee success. Focus on transferable skills and tangible achievements instead.
Why does this matter?
Enterprise Architecture is too important to get wrong.
When you focus on the wrong things (like obsessing over technical minutiae) you’re not just limiting your talent pool. You’re jeopardising your organisation’s ability to align technology with its strategic vision.
Let’s open up the conversation. Does your EA job spec reflect the true nature of the role? Or is it an outdated checklist that needs rethinking?
BOTTOM LINE (underline, underline, underline)
Enterprise Architects aren’t code warriors. They’re strategic enablers. It’s time we start treating them like it.
By focusing on what really matters (strategy, collaboration, and leadership) you’ll not only attract the RIGHT talent but also set your organisation up for long-term success.
