Nick M.
NM
Nick M.
Enterprise (> 1000 emp.)
"Comprehensive Metrics with Some Usability Challenges"
4.5/5
What do you like best about DX?

I find the regular snapshot feature very helpful in identifying issues around processes or ways of working that might not otherwise surface. The engineering metrics are great for seeing how teams are generally performing and spotting anything that might be slowing them down. I really like the comprehensive metrics provided by DX. Although I could potentially gather these myself with some digging, it's reassuring to know that the calculations have been rigorously done. The true Throughput metric, in particular, is very useful for quantifying the complexity of work delivered by the teams, as opposed to just plain velocity. Additionally, I really like that we can use AI to prompt, even though there were some challenges in getting the right queries. Review collected by and hosted on G2.com.

What do you dislike about DX?

I've found the Data Studio a little hard to use without first being shown. If it was more intuitive I would likely use it more. I really like that we can prompt through AI, but I had some trouble getting the right queries from the prompts. It could just be that the data I was requesting wasn't available though. Review collected by and hosted on G2.com.

Response from Taylor Bruneaux of DX

Nick, the True Throughput callout is spot on. Velocity alone doesn't tell you much about the complexity or weight of what a team is actually delivering, and that distinction matters when you're trying to have an honest conversation about performance.

The Data Studio feedback is useful. It's a powerful feature but the learning curve is real without some initial guidance. Same goes for the AI prompting experience. The query results are only as good as the data available, so that context is helpful to have. Our team is here to help: reach out if we can ever help you navigate the platform or craft queries.

Missy R.
MR
Missy R.
Software Engineering Manager
Small-Business (50 or fewer emp.)
"Very collaborative experience using DX"
4.5/5
What do you like best about DX?

DX has an intuitive, easy-to-use interface that makes it genuinely user-friendly. I also really appreciate that they surface the queries used to populate metrics, so I can dig in when needed and create custom metrics that are a better fit for the questions I’m trying to answer.

They’ve also been incredibly collaborative and responsive whenever I have questions or run into issues, and it’s clear they take the quality and usability of their product seriously. Even though we’re a smaller account for them, they’ve taken my feedback seriously and worked to implement product changes that better fit our engineering use case. I’ve been very impressed with that.

It's a decently pricey product and I was concerned at first that it would be difficult to prove out it's value. That said, we've gotten great feedback from DX that have led to needed changes in our department. Along with that value and with how much of a partnership we've had with them, it has made it worth it to me. Review collected by and hosted on G2.com.

What do you dislike about DX?

It’s hard to build a product that’s flexible enough to fit everyone’s use case while still being opinionated enough to avoid becoming a complete mess. Overall, I think they strike that balance very well. That said, it would be nice if a few areas were a bit more customizable. It’s not a major complaint, just a “nice to have.” Review collected by and hosted on G2.com.

Response from Taylor Bruneaux of DX

Missy, this genuinely made my day to read. Knowing your feedback has translated into real product changes is exactly the kind of relationship we want with every customer. Really glad the query transparency is useful too.On the customization front, I'll raise that internally. Your framing of the balance between flexibility and having a clear point of view is really helpful. Thanks for taking the time to write this up!

Bhavik H.
BH
Bhavik H.
Director of Software Engineering
Enterprise (> 1000 emp.)
"Streamlined Feedback with Robust Analytics"
4/5
What do you like best about DX?

I find DX to be a valuable tool for supporting day-to-day operational activities by providing a structured and efficient mechanism for collecting feedback, insights, and operational inputs across teams. I like how the platform simplifies survey creation and distribution while giving timely visibility into responses and trends. One of DX's key strengths is its ease of use and accessibility, which encourages broader participation and helps us gather actionable information quickly. The ability to centralize operational feedback has improved transparency, alignment, and responsiveness across stakeholders. I appreciate how DX helps streamline communication loops and reduce manual efforts associated with traditional feedback collection methods. Its reporting and tracking capabilities support leadership visibility and follow-through on identified actions. I also find the integration with my internal system quite robust. The enhanced analytics are great for transforming survey feedback into actionable insights, enabling faster identification of operational challenges, trends, and improvement opportunities, supporting more data-driven decision-making and better prioritization. DX provides an intuitive and efficient way to collect operational feedback with strong visibility into responses and trends, which supports faster decision-making and continuous improvement. The initial setup wasn't hard, and the provided examples were helpful. Review collected by and hosted on G2.com.

What do you dislike about DX?

Maybe the analytics can be made more better by adding a rich interface, some graphs perhaps. Review collected by and hosted on G2.com.

Response from Taylor Bruneaux of DX

Thanks for taking the time to write this up, Bhavik. Closing the loop between feedback collection and leadership visibility is one of the harder operational problems to solve, and it's good to know the platform is making that easier for your team.

Appreciate the note on analytics richness too. More visual depth in how data is surfaced is a fair ask. I'll flag this to your customer team to walk you through some of our current visualizations.

Jon David I.
JI
Jon David I.
Mid-Market (51-1000 emp.)
"Out of the Box Software Development Measurements"
5/5
What do you like best about DX?

I like how DX provides built-in comparisons, measuring against industry standards or our own past reporting periods. It aggregates data across multiple tools, which means I don't have to implement something in-house to derive insights from disparate systems. DX already shows the core metrics for software development, which are the specific metrics I'm looking for. It also has integrations with our GitHub, JIRA, and more, which is great. Plus, I use it in Slack to send AI-generated summaries on progress from my teams. As an individual user, I found the initial setup to be easy. Review collected by and hosted on G2.com.

What do you dislike about DX?

It's not always intuitive if you want to drill down into a specific report, or be able to compare individual cohorts to each other if those aren't already defined in DX. It's frustrating when I feel too locked into their predefined filters and reports without the flexibility to drill in a different way I want. Sometimes filter facets are only single select when I'd like to select multiple of that same facet type. Review collected by and hosted on G2.com.

Response from Taylor Bruneaux of DX

Jon David, thanks for the thoughtful write-up. The aggregation across GitHub, Jira, and other tools is a big part of what makes the out-of-the-box metrics actually usable without a custom build, so glad that's saving your team real work. The filter flexibility feedback is specific and fair. Single-select constraints and limited drill-down paths are the kind of friction that adds up quickly when you're trying to answer a question the predefined views don't cover. I'll reach out to your customer team to work closely with you on building customizations.

bhumik s.
BS
bhumik s.
Software Engineering Manager
Small-Business (50 or fewer emp.)
"Insightful Metrics, Easy Setup, Room for Improvement"
4/5
What do you like best about DX?

I like the way DX is able to pick up some KPIs and it's very generic and broad, yet the KPIs are still meaningful. It cuts through different programs, different projects effectively. I also find it meaningful because it gives me insights into our code velocity, especially after integrating AI into our workflows. It helps identify bottlenecks and areas to focus on, boosting our engineering throughput. Additionally, the setup was quite easy due to my organization's infrastructure team and all I had to do was ensure there were no mistakes in our team settings. Review collected by and hosted on G2.com.

What do you dislike about DX?

I feel like at times, some of the settings that I wanna change, like, there might be, things that the developers are working on, and it does not get captured very well. Change. Or simply, like, if I added a wrong GitHub username to a developer, I was not able to change that. Review collected by and hosted on G2.com.

Response from Taylor Bruneaux of DX

Bhumik, measuring code velocity before and after an AI integration is one of the more compelling ways to actually validate whether the tooling is paying off, so glad that's coming through clearly.

The GitHub username and settings flexibility issues are frustrating ones, especially when something as basic as correcting a username feels harder than it should. I recommend flagging these ASAP to your account team who can help you out swiftly Thanks for your review!

Antti M.
AM
Antti M.
Software engineer
Mid-Market (51-1000 emp.)
"Centralized Metrics and Actionable Insights"
5/5
What do you like best about DX?

I like the ease of use of DX and how it produces useful information for our teams to improve. We have found the snapshot surveys very informative, a good way to get input from our developers about what's slowing them down or what they wish us collectively to improve on. These are very actionable points that we then have worked on. Additionally, the initial setup was rather painless, thanks to the helpful team at DX. Review collected by and hosted on G2.com.

What do you dislike about DX?

Maybe some of the reports have been a bit confusing as to how they are produced, and this is tricky as if one reads them incorrectly, it is easy to draw very different conclusions. For example, the 'Innovation ratio' report. It is rather unclear on how it deduces what is 'innovation' work. Review collected by and hosted on G2.com.

Response from Taylor Bruneaux of DX

Thanks for this, Antti. Using snapshot feedback to surface what's actually slowing developers down and then acting on it is exactly the cycle those surveys are designed to support. Really glad that's been working for your team.

The Innovation ratio point is well taken. Any metric where the methodology isn't immediately transparent creates room for misinterpretation, and misreading that one in particular could lead to pretty different conclusions about where to focus. Your account team is on-call to help with any of these reports, so please reach out to learn more!

Janey L.
JL
Janey L.
Engineering Manager
Enterprise (> 1000 emp.)
"Data-Driven Clarity for Team Management"
5/5
What do you like best about DX?

I really appreciate the clarity DX gives me. With a small team, it's easy to assume things are on track, but DX backs that up with data, which is great. The dashboard offers a quick snapshot of the team's progress, and I can see if we're on track or slipping without going through complex tools. It saves me time and makes my check-ins more productive. Specifically, the cycle time and throughput metrics are helpful for understanding our delivery speed, and the PR and code review analytics are really useful. Review collected by and hosted on G2.com.

What do you dislike about DX?

I think some of the metrics and visualizations can be more compact, and there could be AI powered insights or summaries which could save me even more time. Review collected by and hosted on G2.com.

Response from Taylor Bruneaux of DX

Janey, this is such a relatable scenario. Small teams can feel like everything is fine right up until it isn't, so having cycle time and throughput data to sanity-check your instincts is genuinely useful, not just nice to have.

The AI-powered summaries idea is a good one. This is something that we've begun to roll out, so I recommend connecting with your customer team to see our features here!

Jason B.
JB
Jason B.
Senior Software Engineer Team Lead
Mid-Market (51-1000 emp.)
"Invaluable for Team Performance Monitoring"
5/5
What do you like best about DX?

I find the quarterly snapshots in DX incredibly useful because they expose issues with our process and provide the tools to determine if the changes we make based on those issues are actually making a difference. This feature allows us to break down answers by team, monitor stats like PR Cycle Time and AI usage, and find out what parts of our process are working well. Review collected by and hosted on G2.com.

What do you dislike about DX?

The list of reports can be a little overwhelming, making it hard to know what I should be paying attention to. Also the time in hours can be confusing to know if it's working hours vs clock hours, and how they calculate business hours. Review collected by and hosted on G2.com.

Response from Taylor Bruneaux of DX

Love seeing this use case, Jason. A lot of teams use snapshots to identify problems and stop there. The fact that you're looping back to check whether your fixes are actually landing is the whole point.

The hours ambiguity is a fair callout and more confusing than it should be. When cycle time is your north star metric, working hours vs. clock hours is not a small distinction. Your customer team can walk through this with you!

Verified User in Information Technology and Services
UI
Verified User in Information Technology and Services
Enterprise (> 1000 emp.)
"Great for Quarterly Tracking, but Needs More Relevant Questions and Better Reporting"
3.5/5
What do you like best about DX?

Running this survey on a recurring basis, with a measurement every three months, really helps track evolution and improvement over time. Comparing results against other teams in the organization, or even against the industry, also helps identify and better understand the areas where we can improve. Review collected by and hosted on G2.com.

What do you dislike about DX?

Some questions don’t apply to our team, and that creates friction when we have to complete them. Also, the reporting tool has a lot of room for improvement. I’d really appreciate an integration with a retrospective tool and with Jira tickets, so that when we identify action items, we can track them more easily. Review collected by and hosted on G2.com.

Response from Taylor Bruneaux of DX

Really appreciate you taking the time to share this. Quarterly tracking with consistent benchmarks is one of the more powerful ways to build a credible improvement narrative over time, so it's good to know that cadence is working for your team. The question relevance friction and the additional Jira integration ask are both worth calling out. Being able to close the loop from identified action items into actual tracked work is a real gap, and the specificity here is helpful.

Verified User in Leisure, Travel & Tourism
UL
Verified User in Leisure, Travel & Tourism
Enterprise (> 1000 emp.)
"Comprehensive Surveys with Peer Benchmarks That Drive Clear Improvement Actions"
5/5
What do you like best about DX?

The survey’s comprehensive and objective framing helps us identify the areas that need attention. The platform’s peer-comparison offering also helps us understand where we stand and where to invest further. The specificity around Front End/ Back End / Platform/ Data Layers helps us get closer to improvement actions Review collected by and hosted on G2.com.

What do you dislike about DX?

While most aspects of Developer Productivity are covered, aspects around Dev Operations and Tech Operations (post production) can be improved. Any engineer still has to spend decent time in operational aspects beyond being Goalie/on-call, the productivity improvements intelligence for these are areas to be improved on DX Review collected by and hosted on G2.com.

Response from Taylor Bruneaux of DX

Really appreciate the detailed feedback here. The layer-specific breakdowns resonating with your team is great to hear, and the framing around combining qualitative and system data to get to the nuances is exactly the outcome we're going for.

The Dev Ops and Tech Ops coverage point is well taken. Operational load beyond on-call is a real part of how engineers spend their time and it's a meaningful gap to flag.