DX Reviews & Product Details

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.

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.

One of the best things about DX is that it replaces assumptions with a clear, data-driven understanding of developer experience. Instead of relying on intuition and assumptions, DX gives us measurable, comparable insights into where friction actually exists, whether it's in tooling, documentation, cross-team collaboration, or pipelines and delivery flows.

It provides concrete data to validate whether our initiatives are truly moving the needle for product teams, giving us a much stronger foundation for prioritizing work and aligning improvements with real team needs.

As a platform domain, DX is especially valuable because it highlights where we can have the greatest positive impact across the organisation. When DX shows that certain issues (e.g., poor documentation quality) are common across the organisation, it helps us prioritise systemic improvements rather than local optimisations. It essentially gives us a shared compass for where our work will deliver the most value.

In short, DX helps ensure developer time is spent where it creates the most value, and that our technical decisions are backed by evidence rather than opinion. Review collected by and hosted on G2.com.

The main drawback is that DX still requires a certain level of maturity in how teams adopt, interpret, and act on the data. Without that maturity, insights risk becoming passive dashboards rather than meaningful drivers of change.

Also, DX is primarily designed with software engineering teams in mind. This makes it less directly applicable to more traditional infrastructure‑focused teams, where workflows and responsibilities differ from the assumptions built into the model.

It also demands a mindset shift: Teams need to actively work with the insights and continuously adjust their practices based on the data. This takes time and discipline, and there can be some initial overhead before the value becomes obvious.

In short, DX is powerful, but it requires commitment, behavioral change, and continuous refinement to reach its full potential. Review collected by and hosted on G2.com.

As a platform leader overseeing 10+ products and delivery teams, DX is a critical lever for identifying bottlenecks, friction points, and opportunities to improve the developer experience. DX insights help us move beyond what is happening to understand the why behind productivity challenges, enabling more informed, data-driven decisions. By survey feedback (run biannually), we can continuously track developer satisfaction, delivery health, and operational effectiveness. Integration with Jira and GitHub data, helps build metrics such as cycle time by project/team/individual, epic forecast accuracy, support tickets per customer, after-hours activity, and AI coding assistant adoption—allowing us to benchmark against industry standards, improve engineering quality, and ultimately deliver better customer outcomes. Review collected by and hosted on G2.com.

We’ve integrated with Outlook Calendar to get clearer visibility into how teams balance meeting time versus deep work. Right now, the metrics roll up all meetings, and we don’t yet have a way to exclude specific meeting types. That’s an area we can explore enhancing in the future to make the insights more accurate and relevant. Review collected by and hosted on G2.com.

It is maybe the best tool to measure developer experience out there. We in our Developer Tooling team find it very usefull because we can see what our engineers needs. Review collected by and hosted on G2.com.

There are some of the connestions that still are hard to setup, an example of this is how we integrate it into our ARGO cd with argo notifications. Review collected by and hosted on G2.com.

Core4, snapshots and triaging are great tools for making informed decisions, both locally and across the org. As a member of a Developer Tooling team, the insights from these features have been a guiding star for many of the initiatives we pursue. We quickly find out how to move forward by triaging, and finding things to improve, and we get a better indication on what to focus and prioritize our energy next, by investigating snapshots, and reading the comments on snapshots.

Likewise, Studies and PlatformX provide a structured way to gather intel from Product Teams. That’s often a really hard thing to do effectively in large organizations, where it can feel nearly impossible to know what’s going on without some consistent way to take the pulse. We strive to implement PlatformX on most of our products to help track adoption, ease of use, and general feedback.

Overall these features have a direct impact on how we work, and without these features we would have a harder time discovering and prioritizing where to put our energy next. Review collected by and hosted on G2.com.

DX has a lot of features, and getting the full benefit from them requires a significant investment of time and resources. The features themselves are nice, but I’m often left wondering how we’re supposed to apply them effectively within our product teams’ processes. I feel somewhat left to guess, and with everything else going on, that uncertainty limits adoption.

I’m also not clear on the prerequisites for success, or how DX is intended to fit with Scrum processes. These local, day-to-day challenges are hard to solve on our own, and while DX provides the tools, it often feels like our ability to use the full suite is constrained by a lack of practical, real-world examples of what successful adoption looks like.

Something like a welcome pane with clear, step-by-step tasks for admins, leadership, product teams, and individuals—guiding them through how to implement and use DX across an organization and teams—would be a big improvement. Review collected by and hosted on G2.com.

The DX user interface is extremely easy to use, and it provides highly valuable data insights across the entire system development life cycle. The customer success team is outstanding. They're extremely helpful with questions and ongoing suggestions on how to improve your SDLC based on the insights that DX provides. The implementation is pretty easy, and you can generally set it up yourself. Review collected by and hosted on G2.com.

There are so many reports available that it can be a bit overwhelming to figure out which one to use. Review collected by and hosted on G2.com.

As an engineering manager, I’m pretty close to what’s working and what’s not, but it’s still easy to rely too much on gut feel. DX has been useful as a way to sanity-check my assumptions and see whether changes we make are improving things over time.

The snapshot feedback is the most practical part for me. It’s quick for the team to respond to and gives me timely input I can actually act on. When we’ve tweaked sprint expectations, on-call rotations, or delivery process, the feedback has helped confirm whether those changes reduced friction or introduced new issues. Review collected by and hosted on G2.com.

It took a little time for the team to trust what the metrics represent, and I’m careful not to overreact to short-term swings. DX doesn’t replace 1:1s, retros, or just paying attention day to day. Review collected by and hosted on G2.com.

I like that DX allows teams to point to the most painful blockers. There are many predefined areas to choose from, therefore increasing responses. People tend to forget/overlook problems if they are only asked to remember what's blocked on the spot. This is not the case with DX.

I love how easy it is to configure Service catalog and Scorecards.

I have received a lot of help from the AI query builder, which makes accessing custom data easier. Review collected by and hosted on G2.com.

It's sometimes hard for me to separate my problems (if I work with a very small area of code/functionality) from the difficulties the company has (different teams have). This is partly because I'm working in a Devex team. Therefore, I need to think about how to improve work for other teams. Review collected by and hosted on G2.com.

I like clear surveys that we get via this tool. I use DX as an employee in an engineering position. Our organisation survey us to discover pain points and areas that we are doing great in. It lets us see how we are doing compared to the best of engineering teams. Review collected by and hosted on G2.com.

I think this tool has a lot of value to managers but as an individual contributor I don't use this tool that much, I only answer surveys. Maybe it should be made clearer somehow what value in can bring to others not only managers Review collected by and hosted on G2.com.

What I like best about DX is its well-designed features, especially the intuitive dashboard and clean layout. They make it easy to identify pain points and give our team, domain, and tech sector clear, concrete data. This clarity helps us take meaningful action and address issues effectively across multiple organisational levels. Review collected by and hosted on G2.com.

I don’t see any specific downsides, but I’d like the provided data to include a few examples of tangible use cases for addressing the highlighted pain points. This could help generate ideas for tackling the pain points. Review collected by and hosted on G2.com.