Data, cloud and IT
Developer and engineering tools
We ask engineering leaders and developers how tools get chosen in their teams, who holds the budget and how AI coding tools are changing the stack.
What we’re researching
Three questions for 2027.
Findings publish once 100 qualified people have taken part. Until then, this page shows what we’re asking rather than what we’ve found.
- Q1
Who really chooses developer tools: engineers, platform teams or leadership?
- Q2
How are AI coding assistants changing engineering budgets?
- Q3
What makes an engineering team switch a tool it already uses every day?
Who should take part
- CTOs and VPs of engineering
- Engineering managers
- Platform and DevOps engineers
- Software developers
And anyone else shaping a developer and engineering tools decision for their organisation, in any country.
Areas the benchmark covers
Industries we research this with
FAQ
Questions people ask
Who can take the developer and engineering tools benchmark?
Anyone shaping a developer and engineering tools decision for an organisation, in any country and any industry. It is written for people answering in a professional capacity, such as ctos and vps of engineering, engineering managers, platform and devops engineers.
How long does it take?
About 7 minutes. There are 21 questions and no free-text answers.
Is it free?
Yes. Taking part is free and you see your scored result on screen straight away.
What happens to my answers?
Answers are stored without your name, email or IP address and combined into anonymised research. No figure is published for a group smaller than 10. Nobody contacts you unless you tick the box asking us to.
When will the developer and engineering tools findings be published?
Once 100 qualified people have taken part. Until then this page shows the questions we are asking, not findings.