DX Platform
DXReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
244 reviews
from
External reviews are not included in the AWS star rating for the product.
World Class.
What do you like best about the product?
Finally - a solution that gives engineers a voice, and allows us to objectively measure our improvement over time. The DX team are simply world class, not only in their ability to build features, but in the way they deal with customers. From beginning to end, the team have supported rolling DX out to thousands of engineers across the world.
What do you dislike about the product?
There are quite a number of features, and quite as lot of data - sometimes it's not clear exactly what we need to be focussed on.
What problems is the product solving and how is that benefiting you?
Understanding directly from engineers the pain points and challenges blocking them from being their best
Collecting insight from Developers easily
What do you like best about the product?
DX has a complete set of capabilities for qualitative assessment of Developer Experience. Its usage is smooth and easy, and integration with Slack and the timely reminders make running a survey relatively easy. It's easy to use it on a regular basis; we do once a quarter. The support they offer to review the survey output and generate a report where they guide the reading of the results is very useful, saves time, and represents an opportunity to have an external view. The availability of actions to fix the most common issues is also very helpful.
What do you dislike about the product?
To assess Developer Experience, DX focus primarily on qualitative input using a survey approach. It would be really powerful to connect the survey output with a more systematic data approach, where DORA metrics (for instance) are considered and connected with the survey output, to build the big picture. A survey-only approach is influenced by many factors that may not always be under the organisation's control. For instance, running the survey after an intense week of work generated by incidents makes a lot of difference to running the same study after an offsite. I know they are investing in this direction.
What problems is the product solving and how is that benefiting you?
DX is helping to address developer experience issues. I found it useful to have an official feedback about the impact of on call work for one of my teams. It's very helpful to facilitate a conversation with the teams. I also find it useful to assess how some of the actions we put in place resulted in positive impact from developer perspective.
Comparative engineering effectiveness metrics
What do you like best about the product?
Knowing how your engineering effectiveness compares to similar-sized companies within your industry is crucial for identifying strengths and weaknesses, optimizing performance, and making informed strategic decisions.
What do you dislike about the product?
The large number of reports and benchmarks can make it confusing to figure out which metrics matter most. So, you have to put in some time with the tool to learn what the information is telling you and see the connections.
What problems is the product solving and how is that benefiting you?
DX provides valuable insights into our company's performance relative to industry peers, while also streamlining the collection of engineering feedback to identify actionable improvements.
Excellent combination of qualitative & quantiative data to drive productivity and improve dev exp
What do you like best about the product?
DX's approach to combine hard metics (DORA) and more qualitative metrics (SPACE+) both gives a good insight into areas of improvement and friction, but also helps convince developers they're not just being mesured to perform but actually we care about their experience and how to improve "flow". The qualitative/suryve part has helped drive relevant discussions and enable engineering directors & managers to have more meaningful conversations, compare across teams and identify issues that previously wasn't uncovered, and combined with more quantiative metrics made it possible to challenge perceptions and truths to drive meaningful improvements. Highly recommend this tool to improve transparency into the organization and make more data-informed decisions/discussions.
What do you dislike about the product?
Getting started with the qualitative/survey parts was easy but some of the quantiative data has proven more challenging to get "right" in our context due to having different source code repos, CI/CD processes, and branching strategies as a consequence of acquisitions; thus getting the "hard metrics" right has been more challenging and would have been good to get more help during implementation in how to vet these data points, help teams on board through more of a "technical" check-list/workshop and helping sanity check data looks right. The solution is also quite costly.
What problems is the product solving and how is that benefiting you?
Improving developer experience, developer productivity and driving for high performance in our software development practices
Measuring engineering performance and extracting valuable insights to improve it
What do you like best about the product?
A set of aggregated qualitative and quantitative metrics (DORA, SPACE, DevEx, …). The synthesis of the Core 4. Integration with popular tools like Jira, GitHub, GitLab, and more. The new reporting section, which is very useful. Ease of use. Some additional gems like CapEx calculation and the impact of GenAI. The support in our Slack workspace.
What do you dislike about the product?
Honestly, I don’t think there are any truly useless parts.
What I find most problematic is the lack of team membership tracking over time. Let me explain: if a contributor moves from Team A to Team B, Team B “inherits” that contributor’s metrics from when they were still part of Team A, which distorts the historical data. This is really frustrating and, on top of that, makes it impossible to accurately assess the impact of organizational changes.
What I find most problematic is the lack of team membership tracking over time. Let me explain: if a contributor moves from Team A to Team B, Team B “inherits” that contributor’s metrics from when they were still part of Team A, which distorts the historical data. This is really frustrating and, on top of that, makes it impossible to accurately assess the impact of organizational changes.
What problems is the product solving and how is that benefiting you?
Extract valuable engineering metrics, get actionable suggestions for continuous team improvement, access a unified dashboard, and much more.
A platform yielding valuable, actionable insights across your engineering team
What do you like best about the product?
What I like best about DX is its ability to help move conversations beyond just raw data (with no insights) or raw commentary (with no data) and mesh the two in a meaningful way that drives valuable conversations within teams and leadership groups alike. It's something I literally use every day within my company.
What do you dislike about the product?
The team work really hard to ship new features, but at times they appear with little notice and can be a bit jarring or surprising for users. Equally it feels like there are a lot of features we're not currently taking advantage of, that we could understand a little better.
What problems is the product solving and how is that benefiting you?
It's helping us understand the points of friction in our development teams and associated processes, and work on ways of streamlining them to produce a better developer experience.
User of Dx
What do you like best about the product?
I like that I have many reports to use and I can get important info about my team's productivity and efficiency.
What do you dislike about the product?
I don't like that I can not set timezones and working days/time.
What problems is the product solving and how is that benefiting you?
More predictable deployment cycles, and improved collaboration across teams. Overall, DX is boosting our efficiency, reducing errors, and enabling us to deliver value to our users more quickly and reliably.
Invaluable insight into our developer experience and engineering processes.
What do you like best about the product?
The unified dashboard that combines quantitative metrics with qualitative feedback has been a game changer for us. Having all our data in one place gives us a holistic view of the developer experience, allowing us to quickly spot trends, identify pain points, and truly understand what’s happening across the team. This clarity leads directly to actionable insights, so we can focus our efforts where they matter most—and then measure the impact of our changes and adjust as needed.
The integration into slack allows for a low friction experience for our development team which has led to extremely high response rates.
Initial implementation was fairly low effort/friction. Especially with slack and some elements of GitHub.
The integration into slack allows for a low friction experience for our development team which has led to extremely high response rates.
Initial implementation was fairly low effort/friction. Especially with slack and some elements of GitHub.
What do you dislike about the product?
Our integrations still needs work. This is mostly an us-problem. Since we're not a standard SaaS company, many important metrics don't fall neatly into DORA or DX definitions, and we've just not taken the time to properly define what certain metrics mean to us and how we should best measure them in the context of DX.
What problems is the product solving and how is that benefiting you?
I've always believed that when people enjoy their work, they produce their best work—a view that's been backed by years of research. DX is helps us understand where our developer experience falls short and guides us toward changes to improve our team’s happiness and engagement.
Creating Valuable Insights from qualitative data - at scale and at speed
What do you like best about the product?
DX makes what happens in the engineering flow visible with the minimum fuss. Engaging the body of engineers to provide the on the ground information consistently across a wide range of metrics. This engagement happens timely, and encourages engineers to use DX more than just for responding to a survey. The best results are achieved by teams using the DX regularly.
In addition to the core "snapshot" DX offers several integrations. This allows companies to quickly supplement the engineers' voice with hard data. The hard data is often taken out of context and having both hard metrics and the engineers' voice in one place supports good decisions.
DX provides best in class customer support. Their support leading up and post "snapshot" is incredible. We achieve better than 90% response rates for snapshots, and often it is much higher. This adds to the credibility of the data.
Getting started with DX was as simple as giving the DX team roster information and aligning on the few optional questions. The roster is important to get right as it allows you to report information at team and/ or other group levels.
The other thing about DX is transparency. DX is setting the bar for transparency. Easy, and clear.
Every participant see the who responded and the details of the response. This helps with building trust, and increases ownership. This also increases the responsibility of leaaders to to take action.
For us DX has become the backbone of our functional experience insights. We encourage broad and regular use.
In addition to the core "snapshot" DX offers several integrations. This allows companies to quickly supplement the engineers' voice with hard data. The hard data is often taken out of context and having both hard metrics and the engineers' voice in one place supports good decisions.
DX provides best in class customer support. Their support leading up and post "snapshot" is incredible. We achieve better than 90% response rates for snapshots, and often it is much higher. This adds to the credibility of the data.
Getting started with DX was as simple as giving the DX team roster information and aligning on the few optional questions. The roster is important to get right as it allows you to report information at team and/ or other group levels.
The other thing about DX is transparency. DX is setting the bar for transparency. Easy, and clear.
Every participant see the who responded and the details of the response. This helps with building trust, and increases ownership. This also increases the responsibility of leaaders to to take action.
For us DX has become the backbone of our functional experience insights. We encourage broad and regular use.
What do you dislike about the product?
That we had to go through contracting with our procurement team before we could get started?
I don't have dislikes about DX.
I don't have dislikes about DX.
What problems is the product solving and how is that benefiting you?
Getting timely insights regarding aspects of the technical set-up that is impacting the engineering experience.
The DX tool is not a tool for management to hand-down direction.
DX is at the core a tool for the engineer(s) to shape how they work.
(The leaders still need to make decisions, but DX is serving the engineer first ... and that benefits the company and our customers.)
The DX tool is not a tool for management to hand-down direction.
DX is at the core a tool for the engineer(s) to shape how they work.
(The leaders still need to make decisions, but DX is serving the engineer first ... and that benefits the company and our customers.)
Dx is an easy to implement tool that provides a ton of valuable insight into the SE experience.
What do you like best about the product?
The ability to correlate usage of AI tooling to sentiment toward other areas like documentation, test coverage, domain knowledge and more.
What do you dislike about the product?
There's so much feedback that most of it you can't act on. You have to be mindful of the initiatives you prioritize because you can't do everything.
What problems is the product solving and how is that benefiting you?
It's hard to know where the most valuable opportunities are with the engineering experience. What problems exist? Where does it make sense to invest? Dx helps answer those questions in a way that gives software engineers a seat at the table.
showing 61 - 70