What do you like best about the product?

DX helps us by offering both qualitative and quantitative ways to see the “whole picture” behind our engineering teams.

By following industry best practice we are able to measure just the right metrics to know where our teams need to improve.

Furthermore, our product teams are able to engage with the tool and run studies targeting different areas, groups, etc and get near-instant feedback from our developers.

What do you dislike about the product?

Initially I found some data a bit difficult to find but after being enabled on Data Studio I found everything was pretty easy to learn about.

Folks not using Data Studio might have a bit of a challenging time finding exactly the user segments they want.

What problems is the product solving and how is that benefiting you?

It’s giving me a dashboard into the developer pains across the organization which allows me to quantify those pains and prioritize different product efforts.

What do you like best about the product?

I am a product manager and the product lead for an internal developer platform supporting about 700 internal developers at a large media company. DX has become an invaluable tool to doing my job well, especially when I was the sole product manager for our platform engineering org. The fact that DX is designed by researchers means that I have a lot of confidence in how the questions are designed. DX as a tool is quite easy to use as an admin, so I spend nearly all of my time inside the tool benefitting from the insights it provides rather than having to configure it, etc.

I use the quarterly survey snapshots as a diagnosis tool, helping me to understand where my users (internal developers) are struggling and where they are well-served. I often then will use the DX Studies tool to send targeted studies to users to better understand pain points (for example, sending a few custom survey questions about slow pipelines to users who noted in the quarterly snapshot that their deployment lead times are particularly long, or sending a survey I created about IaC development only to users who report spending the majority of their time making infrastructure changes). My org is just starting to use DX's Platform X (just-in-time surveys triggered by user events) to understand how users are feeling right after they use a particular feature. As any product manager knows, user research is very time consuming. While I still make sure we perform some user interviews, DX adds so many extra user insights through the quarterly snapshots, custom studies, and just-in-time surveys that I otherwise may have missed.

A few other reasons that I am an evangelist for DX:
* When it came time to justify why we are prioritizing some outcomes over others, the DX quarterly survey data gave me some great data points to use ("we can stop prioritizing work towards improving quality and reliability, since we can see in DX that our quality score is far above the industry 90th, and developers are reporting very few incidents on the relevant DX question".
* At a certain point, the leader of my org needed to justify the value of Platform Engineering to company leadership. Because we had run about 7 quarterly snapshots at that point, he had lots of trend data from DX to show how much value we had delivered to users over the two years we had been collecting data (developer speed up, time loss per week down, etc).
* The DX team is unbelievably responsive. Not only are they consistently helpful and friendly, but when I have requested features or changes in DX, they are often completed, and quickly. Small UI requests are often shipped within a day or two, and larger requests have been implemented in a few weeks.

What do you dislike about the product?

I've encountered no true downsides of using DX. The biggest challenge is the bias people bring in about survey data versus systems data. When I was first introduced to the idea of DX, I had thoughts like "why would I trust a developer's estimation of deployment lead time when you can just measure it with Github events?" Through education from the DX team, I started to understand the issues with that perspective. First of all, developers are your users as a platform engineering org, and if they perceive deployment as slow, it doesn't really matter whether it really is or not, the perception has a large impact on the satisfaction/happiness of the developer who is feeling that. Also, for things like iteration cycle time, while you CAN perhaps measure it with things like Jira events, in reality that system data could be incredibly messy (different Jira practices across different developer teams, bad Jira hygene) and survey data could actually be giving you truer feedback. Thirdly, because it is so fast and easy to run the quarterly surveys through DX as well as the custom surveys through DX Studies, you can get lots of data covering a wide range of topics very quickly. This partly means that you can use DX as a diagnostic tool, to pinpoint which problem areas you should put time into getting systems data for. And it also means that you don't have to make the decision between waiting a month or more to get systems data or just moving forward on a project without any signal. Instead, you can use survey data to give you a decent signal and later refine that signal using systems data when it is finally available.

What problems is the product solving and how is that benefiting you?

DX helps me understand, as a product manager of an internal developer platform, which problems I should tackle. It saves me an enormous amount of time and gives me lots of data so I can make data-driven decisions. It also has helped me justify the value of the internal developer platform to company leadership, by being able to point to reported value from users (internal developers).

What do you like best about the product?

I love that DX gives a structure way of examining our practices, successes, and failures and compare them across time. Self-reflection is a core value of mine, and having a tool that can help us implement long term reflection has been huge. I like how clean and easy to use the the surveys are and that I can leave comments anonymously so I don't have to worry about the politics of work to express my opinions and experiences.

What do you dislike about the product?

The post-survey review process is a little laborious. Navigating the UI to find comments on various subjects have occasionally proven challenging as some comments are put in different parts of the UI.

What problems is the product solving and how is that benefiting you?

DX provides a framework to review our engineering practices at a high level, provide feedback, and plan for change to improve how things work.

What do you like best about the product?

I love that DX gives all our engineers a meaningful way to be heard. We mainly use DX for the snapshots and analyze that data provided in their dashboard. The survey is fairly quick and easy to complete, but the insights we get are anything but shallow. It prompts thoughtful, honest feedback that has sparked real, positive changes in our engineering org. For example, we have seen a significant increase in the quantity and quality of unit testing org wide. I also appreciate how we can track progress over time by comparing results quarter to quarter. The benchmarking against other companies is incredibly valuable to. It helps us understand where we stand and where we can grow, not just internally but across the industry. As a frontend engineer, I appreciate their commitment to a great user experience, modern user interface, and great product overall.

What do you dislike about the product?

There’s not much to dislike, but if I had to nitpick, I’d love to see more feature support for leaving feedback in different contexts. As companies grow, developer experience is shaped by more than just the immediate engineering team. It’s influenced by cross-functional work with product, design, and other engineering disciplines like frontend, backend, and platform. Without that context, feedback can feel a bit skewed and make it harder to pinpoint what’s truly working or needs improvement.

What problems is the product solving and how is that benefiting you?

DX helps us identify what’s helping or hurting our engineering teams, especially things that often go unnoticed in the day-to-day. It surfaces trends around collaboration, tools, processes, and team health, giving us a data-backed way to prioritize improvements. Instead of guessing what’s broken or waiting for burnout, we can be proactive about creating a better developer experience. That’s led to real improvements in engagement, retention, and productivity across our teams.

What do you like best about the product?

DX does a great job of easily integrating all of our various data sources. It has a well-designed interface that lets you explore the data collected and an extremely powerful "Data Studio" that lets you interact with the data via SQL. The Slack integration is very well built and makes conducting studies seamless.

What do you dislike about the product?

Best practices result in long feedback loops. This is intentionally designed and has good reasoning behind it, but it does seem to limit the pace at which you can measure changes you've made to address pain points. Studies can help between snapshots.

What problems is the product solving and how is that benefiting you?

DX gives us clearer insight into our engineer's software development lifecycle and helps us identify and address blockers or choke points in our process. In particular, DX does a wonderful job of making information gathering as painless as possible. Whether through automated ingestion of git and ticket system information or through measured snapshots and studies, DX has given us a myriad of tools for slicing and dicing our engineers' collective experience. The support, both during on-boarding and afterwards, has been phenomenal. They always seem to have a well-reasoned explanation for why they suggest doing things a certain way, which has been great when their recommendations run counter to our assumptions or plans.

What do you like best about the product?

Easy to set up and use, industry benchmarks and tooling result in significantly higher response rates than other survey mechanisms (over 90%). Feedback captured by DX is actionable and highly relevant to both product work by platform teams and to the cultural and organizational shifts needed. The DX customer success team is fantastic and super responsive.

What do you dislike about the product?

Lack of free-form dashboarding tools to derive additional insights

What problems is the product solving and how is that benefiting you?

Understand areas of investment for platform teams based on drivers and CSAT
Organizational and cultural shifts needed to address key issues faced by technical talent

What do you like best about the product?

After using DX (getdx.com) for 2-3 years to support our engineering team's productivity and happiness, I'd like to share our experience with the platform.

What We Love About DX
Developer Experience Focus
The platform's emphasis on making developers' lives better aligns perfectly with our team culture. It has given us actionable insights to enhance collaboration, reduce friction points, and ultimately keep our engineers happy and productive.

Team Health Monitoring
The platform's ability to track team health metrics has been crucial for identifying burnout risks before they become problems. The sentiment analysis features help us understand how developers feel about their work.

Data-Driven Improvements
Having quantifiable metrics has enabled us to make objective decisions about process improvements rather than relying solely on intuition. This has led to measurable gains in developer satisfaction and productivity.

What do you dislike about the product?

While DX has been overwhelmingly positive for our team culture, there are some natural challenges we've encountered:

Time Investment Required
Taking time away from development work for regular retrospectives and discussions can initially feel counterproductive. Engineers sometimes resist pausing "productive" work to discuss process improvements or address team challenges. However, we've found this investment ultimately pays dividends in the long run.

Change Management Friction
Implementing changes based on DX insights sometimes meets resistance, especially when addressing deeply ingrained habits or workflows. The platform highlights issues, but solving them still requires thoughtful change management and team buy-in.

Accountability Pressure
DX creates greater transparency and accountability for management, which is ultimately positive but can be uncomfortable. Leaders must respond to identified issues rather than ignoring them, which requires genuine commitment to improving developer experience over focusing solely on delivery timelines.

What problems is the product solving and how is that benefiting you?

Fragmented Developer Feedback Collection
Before DX, we struggled to collect comprehensive feedback from engineers about their work experience in a structured way. The 360 Snapshots provide a consistent framework for gathering insights across multiple dimensions of the developer experience.

Blind Spots in Team Sentiment
Previously, we only discovered team frustrations during exit interviews or when issues reached a breaking point. 360 Snapshots give us regular temperature checks that surface concerns before they become critical problems.

Lack of Data-Driven Culture Improvements
We often made culture and process changes based on anecdotal evidence or the loudest voices in the room. The quantifiable metrics from 360 Snapshots allow us to make more objective decisions.

What do you like best about the product?

Knowing how well an Engineering team is doing on various aspects is a very difficult task. The quarterly DX survey gives us two things, namely feedback directly from the engineers on things that are working and that are not working, and a way for us to compare ourselves to industry peers. Those two things really help us to know where to focus improvements.

What do you dislike about the product?

It's not cheap for a survey, but once you understand the benefit and it is important to you, it will make the decision easier.

What problems is the product solving and how is that benefiting you?

It is giving us insights (from our engineers and our industry peers) where we should focus improvements in our engineering team.

What do you like best about the product?

I like its user-friendliness, its ability to enable teams to continuously identify and work on improvements themselves, and I also appreciate the AI capabilities.

What do you dislike about the product?

There is nothing special about this product that I dislike

What problems is the product solving and how is that benefiting you?

It helps our teams become more productive.

What do you like best about the product?

Having a comparison with companies in the market, in the same segment, to be able to understand where you need to work to improve that experience, makes all the difference.

What do you dislike about the product?

The tool could enable interaction and exchange of experiences between participating companies.

What problems is the product solving and how is that benefiting you?

Helps understand friction points we may have in our software development process.