What do you like best about the product?

DX helped us in getting a clear idea from our team regarding the overall sentiment and feedback so that we can prioritize improving the score before we roll out the next survey. It helped us to compare the score in each quarter with the previous score and to see the progress we have made so far. It is easy to use, and the implementation was also smooth.

What do you dislike about the product?

I didn't find any issues so far! The ease of implementation and usage saved us a lot of time.

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

It helped us in getting the feedback and suggestions from the team so that we could prioritize and improve the areas based on these.

What do you like best about the product?

DX provides valuable measurement and benchmarking for all aspects of Developer Productivity. Metrics gathered by DX have been in use for years at Dropbox to prioritize investments in developer tooling and experience. Using an industry standard set of measurements, as well as industry benchmarks that DX provides has helped us cut through uncertainty about how/what to measure and focus on making meaningful improvements to Dropbox's developers' workflows.

DX has been able to capture data coming from proprietary systems as well as from OTS solutions. This has made implementation/deployment a breeze.

Finally, the Data Cloud tool suite has allowed us to perform advanced analysis on all aspects of our DX metrics. This has allowed us to gain deep insight into developer experience.

What do you dislike about the product?

Internal users tend to over estimate DX's scope due to how feature rich and adaptable DX has proven to be.

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

DX helps us track and analyze factors contributing to developer productivity, helping us maximize ROI on developer head count.

What do you like best about the product?

I really like how DX allows us to get deep, insightful answers and compare them directly to how we’ve approached things in the past. This makes it much easier to track progress and identify areas for improvement.

What do you dislike about the product?

The question types can feel a bit prescriptive and lack customization options. Sometimes this means we have to reframe the questions we actually want answered or adjust our wording to fit the available formats, which can be limiting.

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

We build internal tools that our developers use directly, so getting their feedback is extremely valuable. DX helps us gather that feedback in a structured, meaningful way, giving us a clear data point on how our work is landing. This insight is crucial for shaping the direction of our development and ensuring we’re meeting real needs.

What do you like best about the product?

Gives you the bigger picture and out of the box overview on what is going on within your team and are you on track to address those or not. with each snapshot you have the opportunity to track the progress

What do you dislike about the product?

Few integration has limited functionality. for instance some of Bitbucket activity/commits are not tracked.

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

Productivity and collaboration bottlenecks, what makes our team frustrated and what is the most important improvement which can be applied but we have not seen it.

What do you like best about the product?

DX Snapshots help you monitor developer sentiment across a wide array of dimensions and compare your results with industry benchmarks.
DX Studies make it easy to reach out and gather more information from specific cohorts .
DX PlatformX makes it easy to reach out to users after they perform specific events.
The DX team are industry leaders who make themselves knowledgeable and accessible.

What do you dislike about the product?

Not much is left to be desired. When I have had small issues, they've shipped feature requests in 3-4 days multiple times. They know what their product needs to do and they deliver on those expectations well.

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

They provide a suite of tools to connect with the developers that platform teams serve. They are industry leaders and share their knowledge through their product and content they publish.

What do you like best about the product?

Having our Gitlab/Github/Jira integrated with DX, it really surfaced a lot of our team's strengths and areas for improvements. As we perform quarterly surveys while emphasizing on transparency, team really is open to adopt the feedback process, which gives team areas of focus each quarter to make incremental improvements. It's really easy to integrate with the toolsets we have and DX team provides excellent white glove services.

What do you dislike about the product?

Every team is different and they have different priorities to look at. The nature of DX having many features may not highlight each team's focus, so it takes a bit time for each time to customize their own UI interface to highlight their needs but DX team has been phenomenal in adapting to customer needs.

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

The quarterly feedback system is a huge benefit to my team. It creates transparency (and we do address the feedback) among the developers and gives them a place to be heard frequently.

What do you like best about the product?

The survey design process is smooth and intuitive, with a user-friendly UI that makes setup fast and frustration-free. The main thing about the design is - it's research driven. I also really value the benchmarking feature, being able to compare our results against peers adds meaningful context to the data. The delivery mechanism is very impressive, it significantly boosts response rates that everyone struggles with.

What do you dislike about the product?

DX is still maturing in a few areas: particularly in how results are explored in the dashboard. The data is all there, but it can sometimes feel like you need to dig around a bit to surface the specific insights you're looking for. That said, the team more than makes up for it by proactively sharing tailored reports that highlight the most relevant findings. Their support has been excellent, and they’re always open to feedback and quick to act on it.

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

DX helps us gather high-quality feedback directly from developers, a group that’s typically hard to engage through traditional survey channels. It solves the challenge of both targeting the right audience and getting meaningful response rates. The insights we get help us prioritize product decisions, validate ideas, and stay aligned with what developers actually need. It’s become a key part of how we stay user-informed.
Beyond standard surveys, we can run targeted studies that dive deeper into specific cohorts, whether it’s by role, the language they write in, team etc. This level of granularity has been incredibly valuable for shaping product strategy, messaging, and overall user understanding. It’s helped us move from assumptions to evidence-based decisions.

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.