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.
Effortless Quarterly Dev Surveys that need some refinement terms for special use cases
What do you like best about the product?
Insights into how the dev's feel about their work and tooling. It's impossible to get a clear cut response otherwise. We could spin up a survey for a given tool, but it requires manual checking at regular intervals and comparing of notes afterwards. Here we are able to have the quarterly survey go out without much work at all. And it automatically compares the history so we can see the trends
What do you dislike about the product?
The values are much less meaningful for certain teams: particularly Mobile and Platform teams. Platform teams might always have much lower values, for example, on PR time, but that doesn't necessarily mean that something is wrong. Showing it as a yellow value compared to feature teams is a bit discouraging. Similarly, comparing release time for Mobile releases does not even remotely compare to Web releases. The numbers may look bad even though they aren't.
What problems is the product solving and how is that benefiting you?
Getting a pulse on how the developers feel about certain areas; But most importantly, WHAT problem is the most important to them this quarter. It seems to change every quarter and that allows me to rotate my focus to serve them.
Good intent, but value depends heavily on setup and data quality
What do you like best about the product?
Helpful visibility into engineering productivity signals and delivery trends across teams.
What do you dislike about the product?
Feels noisy and hard to operationalise; insights aren’t always actionable without heavy configuration.
What problems is the product solving and how is that benefiting you?
It aims to quantify delivery health and bottlenecks, supporting better planning and stakeholder alignment.
DX Nails It: Insightful Surveys, Perfect UX, and Powerful Dashboards
What do you like best about the product?
I've been following DX for many years, always appreciating their in-depth researches, insights, knowledge of the market, and understanding of what engineers and companies needs, how to make both happy and why, what are the tradeoffs, and more.
Then it I had a big surprise when one day, as part of big ex devex and engineering excellence investments, Preply's Slack had a new bot, DX, asking me to fill out a survey 😍
Then I got even more joy when I realized that not only the survey was interesting and I'm point, but also the UX of the web app was perfect!
When I got the link to the dashboard to look at the company data, it was another moment of joy: I can look at tons of detailed data, analyze it easily, compare them team by team, compare it with the market, read the whole company engineers feedback, and way more.
I want to highlight that nailing something like DX's for isn't granted. If you have ever worked with dashboards and the need to allow the users to gather meaningful information out of an ocean of datw isn't straightforward.
DX nailed everything they do, and every moment of interaction with them and they product is a spark of joy. I can't recommend DX more, I really love them, what they do, their product, and the productivity outcome they unleash for their clients. 😍
Then it I had a big surprise when one day, as part of big ex devex and engineering excellence investments, Preply's Slack had a new bot, DX, asking me to fill out a survey 😍
Then I got even more joy when I realized that not only the survey was interesting and I'm point, but also the UX of the web app was perfect!
When I got the link to the dashboard to look at the company data, it was another moment of joy: I can look at tons of detailed data, analyze it easily, compare them team by team, compare it with the market, read the whole company engineers feedback, and way more.
I want to highlight that nailing something like DX's for isn't granted. If you have ever worked with dashboards and the need to allow the users to gather meaningful information out of an ocean of datw isn't straightforward.
DX nailed everything they do, and every moment of interaction with them and they product is a spark of joy. I can't recommend DX more, I really love them, what they do, their product, and the productivity outcome they unleash for their clients. 😍
What do you dislike about the product?
To be honest: nothing, I think the platform is perfect as it is at the moment
What problems is the product solving and how is that benefiting you?
Getting high quality, actionable, and quick insights about the devex situation
Helpful for Spotting Systemic Friction and Team Trends
What do you like best about the product?
In my role, I’m trying to understand where friction is systemic versus local, and DX has been helpful for that. It’s not something I look at daily, but it’s useful when stepping back and looking at trends across teams, especially in areas like delivery flow and operational load.
What do you dislike about the product?
There is some upfront work to align on interpretation, and it’s not a replacement for deeper analysis. Used intentionally, it’s been a solid input into higher-level technical and operational conversations.
What problems is the product solving and how is that benefiting you?
We’ve gotten value from the AI adoption tracker in particular. It’s helped clarify which teams are actually integrating AI into their workflows versus where it’s still more exploratory. That’s been useful for shaping platform direction and internal guidance without pushing everyone toward the same solution too early.
Versatile Insights Tool for Leadership, Platform, and Team Improvements
What do you like best about the product?
I like that the tool can be used in multiple ways across the organisation, with a wide range of features that support those different needs.
For our leadership team, it offers useful insights to help steer our engineering strategy and track how we’re progressing against it.
For Platform teams, it’s a valuable way to gather internal user feedback and use those insights to inform roadmap decisions.
For individual teams, it provides a strong pulse-check to reflect on and retrospect about the developer experience, helping drive meaningful improvements at the team level.
For our leadership team, it offers useful insights to help steer our engineering strategy and track how we’re progressing against it.
For Platform teams, it’s a valuable way to gather internal user feedback and use those insights to inform roadmap decisions.
For individual teams, it provides a strong pulse-check to reflect on and retrospect about the developer experience, helping drive meaningful improvements at the team level.
What do you dislike about the product?
After using the product for a while, we’ve found that the drivers are more useful at the leadership level than for generating platform product insights. In our case, we’ve relied more on CSATs and PlatformX surveys to gather information that’s been more actionable and helpful. That approach naturally comes with a small additional overhead.
What problems is the product solving and how is that benefiting you?
When we first established DX, our focus was on understanding developer efficiency in context. With the tools we used previously, we could see efficiency data, but it only told us the “what,” not the “why.”
DX’s features and overall approach have helped us better pinpoint the “why,” which in turn has enabled more informed, effective decisions about where and how to improve.
DX’s features and overall approach have helped us better pinpoint the “why,” which in turn has enabled more informed, effective decisions about where and how to improve.
Helpful, lightweight way to check whether changes are actually helping
What do you like best about the product?
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.
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
Understanding my team's developer sentiments, what is blocking them, what bothers them, what can make things better. Also giving actionable items to improve and help the team going forward.
A steady, practical way to talk about developer experience at the leadership level
What do you like best about the product?
From a senior leadership perspective, developer experience is one of those things everyone agrees is important, but it’s hard to talk about consistently. Most of what you get is anecdotal or very team-specific. DX has been useful for us as a way to bring some structure to those conversations without pretending the problem is simple.
We primarily use the core four metrics as directional signals. I don’t expect them to be perfectly precise, but they give us a common baseline across teams and over time. That’s been helpful in planning discussions, budgeting conversations, and when we’re evaluating whether changes to process or staffing are actually improving things or just moving pain around.
Where DX has helped most is in exec-level communication. It gives us a neutral vocabulary to discuss engineering health that isn’t tied to any one team or tool, which makes tradeoffs easier to explain and decisions easier to justify.
We primarily use the core four metrics as directional signals. I don’t expect them to be perfectly precise, but they give us a common baseline across teams and over time. That’s been helpful in planning discussions, budgeting conversations, and when we’re evaluating whether changes to process or staffing are actually improving things or just moving pain around.
Where DX has helped most is in exec-level communication. It gives us a neutral vocabulary to discuss engineering health that isn’t tied to any one team or tool, which makes tradeoffs easier to explain and decisions easier to justify.
What do you dislike about the product?
That said, it requires discipline. The metrics don’t stand on their own and shouldn’t be treated as goals. We’re careful to pair them with qualitative input and manager judgment. Used that way, DX has fit well as a supporting input rather than something that drives decisions outright.
What problems is the product solving and how is that benefiting you?
Overall, it’s been a reasonable addition to how we think about developer experience at scale.
Engineering Intelligence, backed by an excellent Support Team
What do you like best about the product?
DX gives us meaningful insights into how well our engineering organization is working and helps us make better decisions. What really sets DX apart is the level of partnership we’ve experienced; having a direct communication channel with their team for feature requests and support makes a huge difference.
I also like that we reach almost all employees with the quarterly Snapshot surveys, with much higher engagement than other internal surveys we’ve run. Another feature worth highlighting is the AI assistant for writing database queries, which makes creating custom reports a breeze even without deep SQL knowledge. I also appreciate the flexibility: DX comes with strong out-of-the-box integrations (like GitHub or Linear) but also let us send custom metrics to enhance the available data.
I also like that we reach almost all employees with the quarterly Snapshot surveys, with much higher engagement than other internal surveys we’ve run. Another feature worth highlighting is the AI assistant for writing database queries, which makes creating custom reports a breeze even without deep SQL knowledge. I also appreciate the flexibility: DX comes with strong out-of-the-box integrations (like GitHub or Linear) but also let us send custom metrics to enhance the available data.
What do you dislike about the product?
For us, the main limitation is the subscription structure, which can feel a bit restrictive. For example, we’d like to use the Sentry connector, but that requires upgrading to the "Full Service Cloud" package. It would be much more helpful to have greater flexibility to select and enable individual integrations without needing to move to a higher-tier bundle.
In our case, the catalog of services also feels somewhat crowded because it includes many auto-generated tools that aren’t relevant to us. In addition, although many fields display industry comparison values, those benchmarks are often missing. That makes it harder to judge whether our numbers are in a good range or if they need attention.
In our case, the catalog of services also feels somewhat crowded because it includes many auto-generated tools that aren’t relevant to us. In addition, although many fields display industry comparison values, those benchmarks are often missing. That makes it harder to judge whether our numbers are in a good range or if they need attention.
What problems is the product solving and how is that benefiting you?
Before adopting DX, we didn’t have deep visibility into the overall health and performance of our engineering organization. Our standard internal surveys also tended to have low engagement, which left us with incomplete data and an unclear picture.
DX has addressed this by providing a platform our developers actually use and engage with, giving us a more reliable “pulse” on the organization. On top of that, being able to combine standard integrations (like GitHub) with our own custom data helps us make evidence-based decisions instead of relying on gut feeling.
DX has addressed this by providing a platform our developers actually use and engage with, giving us a more reliable “pulse” on the organization. On top of that, being able to combine standard integrations (like GitHub) with our own custom data helps us make evidence-based decisions instead of relying on gut feeling.
GetDX Delivers Deep Developer Insights with Powerful Survey Tools
What do you like best about the product?
For me - a DevEx team developer and also us as a team - I could not think of a better way to get insights from our developers which then dictates our goals, weak and strong sides. DX provides the opportunity to achieve simple goal - survey the developers, but also gives all those other useful tools (feature toggle, comparison to industry standards and etc.).
What do you dislike about the product?
Nothing much to dislike about DX from my perspective, but since this is a survey-driven platform, the surveys itself can be improved in terms of interactivity. More appealing, interesting and quicker surveys can reduce the fatigue which developers can get while filling in the surveys.
What problems is the product solving and how is that benefiting you?
Mostly - local development issues, also: tech debt management, test efficiency, cross-team collaboration, ease of release, code review and probably 10+ more.
Useful signal for understanding developer experience
What do you like best about the product?
- It gives a clear, structured view into developer productivity and experience.
- The benchmarks help put team signals into context instead of guessing.
- The benchmarks help put team signals into context instead of guessing.
What do you dislike about the product?
- Some insights stay fairly high-level and require extra interpretation.
- Customization and deeper qualitative context can feel limited.
- Customization and deeper qualitative context can feel limited.
What problems is the product solving and how is that benefiting you?
- DX helps make sense of developer productivity by connecting delivery data with how developers actually experience their work.
- It benefits me by highlighting real bottlenecks and friction points, so I can focus on fixing the right problems instead of relying on assumptions or vanity metrics.
- It benefits me by highlighting real bottlenecks and friction points, so I can focus on fixing the right problems instead of relying on assumptions or vanity metrics.
showing 31 - 40