News & Events
Developer Experience (DevEx) has quickly moved from a niche concept to a boardroom priority. For technology leaders under pressure to deliver faster, retain talent, and modernise effectively, it offers a clear link between how developers work and how the business performs.
But while many organisations now recognise its importance, far fewer understand how to hire for it effectively. That’s where most efforts fall short.
Drawing on insights from Ethan Sumner, Co-Founder and CEO of Community Stack, who has worked across large-cap organisations, this article explores what DevEx really is and how to hire the people who can actually improve it.
At its simplest, DevEx is “the sum of everything a developer encounters when doing their job.” That includes tools, processes, feedback loops, documentation, and culture, the full texture of the working day.
It’s often confused with related disciplines:
DevEx cuts across all of them. It’s the human layer, asking whether the systems and processes in place actually work for the people using them.
As Ethan puts it, organisations can have impressive platforms and still deliver poor Developer Experience.
The rise of DevEx is being driven by both talent and economics.
Developers have more choices than ever, and reputation matters. Poor working environments are quickly exposed, making attraction and retention harder.
At the same time, the cost of friction is now measurable. Ethan describes modernisation work that saved thousands of engineering hours in just days, making DevEx a clear business case rather than a cultural initiative.
Strong DevEx also underpins key performance indicators such as deployment frequency, lead time, and system reliability. Organisations that invest in it gain a competitive edge, making the quality of DevEx hires critical.
Before hiring, organisations need a clear view of what “good” DexEx looks like.
In high-performing environments:
Most importantly, developers feel their time and cognitive capacity are respected.
This is the benchmark DevEx hiring should aim to support.
Many organisations still mis-hire in this space.
A common mistake is overemphasising technical skills while underestimating the human side. As Ethan explains, “Technical brilliance without empathy produces platforms nobody wants to use.” DevEx is fundamentally about improving how people work, not just what they use.
Another issue is mislabelling roles. Positions advertised as DevEx are often Platform Engineering roles in disguise, leading to mismatched expectations and poor outcomes.
There’s also a tendency to exclude developers from the hiring process, despite them being the primary stakeholders.
Strong DevEx professionals combine multiple capabilities.
They care about the details of the developer experience, observing friction others have learned to ignore.
DexEx professionals don’t need to be the most technical person in the room, but they do need enough depth to be credible, allowing them to engage confidently with developers and understand problems from the inside.
They treat developers as customers, focusing on journeys, adoption, and continuous improvement rather than one-off delivery.
DevEx rarely operates with direct authority. Success depends on working across teams, aligning stakeholders, and driving change through relationships.
DevEx is an ecosystem of roles working together.
Common roles include:
Together, these roles shape how developers experience their environment day to day.
DevEx hiring needs vary depending on scale.
Startups: need generalists who can move quickly and wear multiple hats.
Scale-ups: require a mix of technical skill and change management to formalise what has grown organically.
Enterprises: face complexity, legacy systems, stakeholders, and organisational dynamics, where influence is as important as engineering ability.
As Ethan notes from experience, “the technology is rarely the hardest part at that scale.
Traditional interview approaches often fall short.
Instead, focus on real-world problem solving:
Practical exercises can also help, such as reviewing a fictional developer platform and identifying friction points.
How candidates describe developers is revealing. Strong DevEx hires think in terms of real people and real constraints, not abstract users.
Hiring for Developer Experience requires more than matching technical skills to a job description. Many organisations are still defining what DevEx means internally, which can make attracting and assessing the right talent particularly challenging.
As a specialist technology recruitment partner, Harvey Nash supports organisations in building DevEx capability across a range of environments, from scaling technology businesses to complex enterprise transformation programmes.
That includes helping organisations hire for roles such as:
Successful DevEx hiring depends on more than technical capability alone. The strongest professionals combine engineering credibility with empathy, communication skills, product thinking, and the ability to influence across teams.
Harvey Nash works closely with organisations to define these requirements clearly, align hiring processes to real-world DevEx outcomes, and connect businesses with talent capable of improving developer workflows, reducing friction, and supporting long-term engineering performance.
To discuss hiring within DevOps, Platform Engineering, and Developer Experience, get in touch with our specialist consultant, James Constantinou, or explore our DevOps Specialism page.
Community engagement also plays an important role in shaping strong Developer Experience environments.
Community Stack, co-founded by Ethan Sumner, works across AI, Cloud, DevOps, Platform Engineering, Data, and Open Source communities, helping practitioners share real-world experiences and best practices. Through events, partnerships, and collaboration with enterprise and public sector organisations, the business provides valuable insight into what developers value most in modern engineering environments.
That proximity to developer communities offers a strong perspective on where organisations are succeeding, and where friction still exists within the developer experience.
Find out more about Community Stack
