DX Platform
DXReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
296 reviews
from
External reviews are not included in the AWS star rating for the product.
DX Turns Developer Insights into Data-Driven Improvements at Scale
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
we use this DX Platform to pinpoint developer-experience bottlenecks and understand the root causes behind productivity challenges in one place.
Built with Empathy for Engineers—A Shared Language for Better Flow
What do you like best about the product?
What really stands out to me is that it’s built with empathy for engineers. It doesn’t try to micromanage individuals; it helps teams spot friction, improve flow, and have better conversations about what’s slowing them down. Used well, it becomes a shared language between engineering, leadership, and platform teams and that’s incredibly powerful.
What do you dislike about the product?
If I’m being honest, the biggest thing to dislike about tools like DX is that they can be misunderstood or misused when the intent isn’t clearly communicated.
Because DX surfaces a lot of data, there’s a real risk that some orgs treat it like an individual performance dashboard rather than a way to understand systemic friction. If teams don’t establish trust and shared context upfront, engineers may start to worry they’re being measured instead of supported, and that can easily backfire.
Another potential downside is that metrics alone don’t tell the full story. DX is great at highlighting where things are slowing down, but you still need strong engineering judgment and real conversations to understand the “why” and decide what to fix. Without that, it’s easy to end up optimizing the numbers instead of improving the actual day-to-day experience.
Because DX surfaces a lot of data, there’s a real risk that some orgs treat it like an individual performance dashboard rather than a way to understand systemic friction. If teams don’t establish trust and shared context upfront, engineers may start to worry they’re being measured instead of supported, and that can easily backfire.
Another potential downside is that metrics alone don’t tell the full story. DX is great at highlighting where things are slowing down, but you still need strong engineering judgment and real conversations to understand the “why” and decide what to fix. Without that, it’s easy to end up optimizing the numbers instead of improving the actual day-to-day experience.
What problems is the product solving and how is that benefiting you?
Before using DX, capturing team feedback felt fragmented and reactive. We relied on a mix of ad-hoc Slack conversations, occasional retros, and periodic surveys. Feedback often arrived late, lacked context, and by the time patterns emerged, the window to act had already passed. It was also difficult to connect sentiment to what was actually happening in the delivery cycle, so many concerns stayed anecdotal.
With DX’s snapshotting feature, that changed in a very practical way. We had struggled to get timely, structured feedback that reflected how teams were feeling in the moment. Now we can capture lightweight, contextual snapshots tied to real events releases, incidents, and changes in process which has produced a clearer signal and faster action on real friction points.Participation improved as well, because snapshots are quick and low-effort, leading to more honest and more representative input from teams.
In terms of impact, we’ve reduced the time spent trying to interpret team sentiment by 30–40%, since the feedback is clearer and easier to synthesize. Follow-ups on DX or process issues now happen in days instead of weeks, which helps prevent small frustrations from turning into recurring problems. Leaders spend less time chasing qualitative input, and teams feel more heard, which has measurably improved engagement in retros and improvement initiatives.
Overall, DX’s snapshotting has turned feedback from a lagging indicator into a near-real-time signal, making it easier to act early and make changes that actually stick.
With DX’s snapshotting feature, that changed in a very practical way. We had struggled to get timely, structured feedback that reflected how teams were feeling in the moment. Now we can capture lightweight, contextual snapshots tied to real events releases, incidents, and changes in process which has produced a clearer signal and faster action on real friction points.Participation improved as well, because snapshots are quick and low-effort, leading to more honest and more representative input from teams.
In terms of impact, we’ve reduced the time spent trying to interpret team sentiment by 30–40%, since the feedback is clearer and easier to synthesize. Follow-ups on DX or process issues now happen in days instead of weeks, which helps prevent small frustrations from turning into recurring problems. Leaders spend less time chasing qualitative input, and teams feel more heard, which has measurably improved engagement in retros and improvement initiatives.
Overall, DX’s snapshotting has turned feedback from a lagging indicator into a near-real-time signal, making it easier to act early and make changes that actually stick.
Easy Developer Feedback Collection with Actionable Insights—No Data Science Needed
What do you like best about the product?
DX is very easy to use for gathering developer feedback across a variety of areas. It collects the data in a way that helps avoid notification fatigue, and it also supports analyzing that data and turning it into actionable insights. The tool is straightforward enough that you don’t need anyone on the team with a specific data science background to get value from it.
What do you dislike about the product?
Some of the integrations still require manual setup and configuration.
What problems is the product solving and how is that benefiting you?
Insights into the developer experience across a large organization.
Great Integrations—Especially GitHub—for Easy Developer Feedback
What do you like best about the product?
DX has great tools that integrate with other platforms, which makes it easy to get developers to provide feedback. I especially like the GitHub integration, and the fact that you can identify actors from usernames and similar details.
What do you dislike about the product?
The status codes I receive from some of the API endpoints aren’t very descriptive and don’t feel fully thought out. It could just be me, but getting a 422 return code on a failed call isn’t very informative.
What problems is the product solving and how is that benefiting you?
DX provides insight into the problems and frustrations developers face in their day-to-day work. With DX, we can measure these issues and make better decisions about where to focus next, based on real data.
Transparent Pain Point Insights with Concrete Data That Drives Action
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
DX makes identifying pain points a very transparent process. It provides our team, domain, and tech sector with concrete data, which makes it much easier to take action and address those pain points across multiple organisational levels.
Best-in-Class Tool for Measuring Developer Experience
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
DX helps us understand what developers actually need from our Developer Tooling team by providing data-driven insights instead of relying on assumptions or anecdotal feedback. This allows us to better prioritize improvements and focus our efforts where they create the most value.
More broadly, our Tech Enabling domain (including the Developer Cloud Platform and Observability teams) can use DX in the same way to identify friction points and opportunities across the developer experience.
In addition, individual teams can use DX to gain visibility into their own workflows at a team level. This enables them to use data to reflect on how they work and supports informed discussions when they want to adjust or improve their ways of working.
More broadly, our Tech Enabling domain (including the Developer Cloud Platform and Observability teams) can use DX in the same way to identify friction points and opportunities across the developer experience.
In addition, individual teams can use DX to gain visibility into their own workflows at a team level. This enables them to use data to reflect on how they work and supports informed discussions when they want to adjust or improve their ways of working.
Comprehensive Qual + Quant Data Framework That Clearly Guides Improvement
What do you like best about the product?
The data framework of qualitative and quantitative input that as a whole gives you a complete picture of where you need to put your energy to improve
What do you dislike about the product?
I think the ux could be better and I think you could leverage that postgres data alot more through AI
What problems is the product solving and how is that benefiting you?
Actionable insights, into our product teams pain points
Valuable Customer Success Partners with Efficient AI Summaries & Actionable Insights
What do you like best about the product?
Customer success partners are very valuable. The AI summaries make it efficient and easy to consume the data, and the suggested actions for improving pain points are super helpful.
What do you dislike about the product?
The number of reports to read through and fully understand can feel overwhelming at times. Other than that, I’m still learning about DX, and I expect I’ll be able to share more helpful feedback here in the future.
What problems is the product solving and how is that benefiting you?
They identify bottlenecks and pain points and provide recommendations on how to improve. Ultimately, this helps us deliver software faster and with better quality.
Snapshots, Triaging & PlatformX: Essential Insights for Better Prioritization
What do you like best about the product?
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.
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.
What do you dislike about the product?
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.
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.
What problems is the product solving and how is that benefiting you?
Before DX, we didn’t have an effective way to identify where to focus our energy or to understand how effective our initiatives really were. Without a clear method to spot organization-wide problems and measure success, most of our work was driven by opinion-based issues and ended up having little to no impact.
After DX, we have insights that guide our initiatives using honest, unambiguous data. We can identify the problems that actually matter and build solutions informed by user feedback, which helps ensure we’re building “the right thing.”.
After DX, we have insights that guide our initiatives using honest, unambiguous data. We can identify the problems that actually matter and build solutions informed by user feedback, which helps ensure we’re building “the right thing.”.
Effective, Well-Organized Surveys with Powerful SQL-Based Reporting
What do you like best about the product?
I love the way DX manages surveys; it’s very effective and well organized. Moreover, beyond all the reports available, the ability to build on top of plain SQL is a real blessing.
What do you dislike about the product?
The learning curve is steep, and the product has so many functionalities that it’s easy to get lost at first.
What problems is the product solving and how is that benefiting you?
We need a deeper understanding of what we can improve so our engineers can work more efficiently and effectively.
showing 21 - 30