# DX Reviews **Vendor:** DX **Category:** [Software Development Analytics Tools](https://www.g2.com/categories/software-development-analytics-tools) **Average Rating:** 4.6/5.0 **Total Reviews:** 321 ## About DX DX is the developer intelligence platform designed by leading researchers to help engineering organizations measure productivity and navigate the shift to AI-augmented engineering. The platform provides research-backed measurement by unifying quantitative data from SDLC tools with qualitative, developer-reported friction to offer a complete view of engineering performance. By serving hundreds of the world’s most iconic companies, including Dropbox, Pfizer, and Uber, DX provides the data and insights leaders need to lead with confidence in the AI era. Measuring productivity has long been an elusive challenge, but DX anchors insights in validated signals through the DX Core 4—measuring speed, effectiveness, quality, and impact—and the Developer Experience Index (DXI). These frameworks allow organizations to see how developers work and where they get stuck to reduce friction and boost satisfaction. By using tools like Workflow Analysis, Experience Sampling, and DevSat, DX captures the conditions developers need to deliver effectively, moving beyond "culture fluff" to connect developer friction directly to business impact. The platform offers extensive Engineering Productivity capabilities, including SDLC Analytics, TrueThroughput™, and Engineering Allocation to align engineering with business goals. Leaders can use Team Dashboards and Custom Reporting to find bottlenecks, while R&D Capitalization and Sprint Analytics provide precise evaluation of organizational performance. To understand how a company compares to the broader market, Industry Benchmarking allows for a precise evaluation of performance against specific peer companies and industry segments. To manage the transition to generative AI, DX provides a specialized AI Measurement framework. This allows leaders to track GenAI adoption and impact to guide smarter decisions at scale. Organizations use these insights for Strategic Planning, Vendor Evaluation, and AI Workflow Optimization, ensuring that AI investments result in tangible improvements to engineering velocity. Additionally, AI Enablement tools—including the Systems Catalog, Context Management, and the Internal Developer Portal—help unify context from across the SDLC to power an AI-native future. This suite also includes AI Readiness assessments, Agent Ops Tools, and Scorecards to ensure developer self-service is optimized for high output. DX AI serves as an AI Copilot for engineering leaders, acting as an analytical layer over the organization's data. Instead of static dashboards, DX AI continuously delivers insights and flags risks automatically. It helps leaders answer complex questions about their data, creates custom reports from simple prompts, and provides specific AI Recommendations on where leaders should focus next. Every insight in DX is designed to be actionable, leading toward a clearer question or a concrete next step. Through Executive Reporting and Targeted Studies, the platform provides CXOs and managers with the evidence needed to decide more effectively. By identifying measurement gaps and revealing what the data or developer voice shows, DX helps organizations optimize their engineering performance in an increasingly complex technical landscape. ## DX Pros & Cons **What users like:** - Users value the **actionable insights** from DX, enhancing decision-making and driving significant improvements in developer experience. (116 reviews) - Users value the **great metrics** and ease of use in DX, along with excellent integrations and customer support. (87 reviews) - Users value the **team collaboration** in DX, appreciating the support and autonomy it fosters for engineers. (72 reviews) - Users praise DX for its **flexible integration and first-class survey tools** , enhancing feedback collection and data analysis. (71 reviews) - Users value the **productivity insights** provided by DX, enhancing team efficiency and supporting continuous improvement efforts. (71 reviews) - Users praise the **amazing customer support** of GetDX for its prompt responses and helpful insights throughout their experience. (67 reviews) - Metrics (64 reviews) - Ease of Use (63 reviews) - Visibility (44 reviews) - Issue Identification (42 reviews) **What users dislike:** - Users express concerns about **metrics issues** in DX, highlighting misinterpretations and outdated data leading to confusion and inefficiencies. (32 reviews) - Users find the **limited customization features** of DX complicate tailoring the interface to specific team needs. (27 reviews) - Users face **integration issues** with DX, experiencing fragmentation and incomplete features that hinder overall workflow cohesion. (21 reviews) - Users find the **team management process complex** , facing challenges in effective implementation and adoption within their teams. (21 reviews) - Users find the **complex configuration** challenging, especially when integrating with non-standard tools and during onboarding. (16 reviews) - Lack of Customization (16 reviews) - UX Improvement (15 reviews) - Difficult Configuration (13 reviews) - Reporting Issues (13 reviews) - Difficult Navigation (12 reviews) ## DX Reviews ### 1. Clean, Easy-to-Use Snapshots and Surveys That Strengthen Our Roadmaps **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) **Reviewed Date:** May 19, 2026 **What do you like best about DX?** The snapshots are great and help us a ton to build our roadmaps and address what's really painful first. Building and running surveys is also great and helps our infrastructure team really lean into the Product mindset. The interface is clean and simple to use. The Slack connector works well as well, and helps ensure everyone answers the snapshots. Performance-wise, I don't have much to say; things are working great so far. I haven't had the chance to play with the AI/Intelligence, automated features, etc, but it's one of my projects for this year. I'm not exposed to Pricing and never dealt with Support, so I can't say much on that front. **What do you dislike about DX?** When you have a monorepository, it can be a bit confusing to split it into different services in GetDX. **What problems is DX solving and how is that benefiting you?** We had a hard time identifying the main pain points of our customers (the developers), and DX really helps us adopt a Product mindset and build the muscle of feedback gathering. **Official Response from Taylor Bruneaux:** > Thanks for this. The use case you're describing is exactly what snapshots are built for: getting a direct, validated read on developer pain so infrastructure and platform teams can prioritize with confidence rather than guessing. Really glad it's helping your team build that feedback muscle. Good callout on the monorepo service splitting. That's a real edge case and something we're actively working to make clearer. Appreciate you flagging it. When you do get to the AI features, would love to hear what you think. There's a lot there for teams already operating with a product mindset. ### 2. Effortless Integration and Insightful Analytics **Rating:** 4.0/5.0 stars **Reviewed by:** James W. | Technology Director, Mid-Market (51-1000 emp.) **Reviewed Date:** May 19, 2026 **What do you like best about DX?** I think DX is pretty easy to use. I like the Slack integrations because they notify me when things are fully out of scope, like PRs needing review, which is really helpful. I also like that I can write SQL queries and pull my own data, as most tools seem to be integrated with DX, making it easier to have one source for everything. The Slackbot integration is particularly useful because it helps me track PRs that are outside of the cycle time, encouraging follow-ups. The ability to write SQL queries is helpful for writing custom reports, especially around AI efficiency and token usage, allowing me to drill into the data in a way that I prefer. The initial setup was pretty straightforward with simple integrations. **What do you dislike about DX?** Maybe for some of the common things, especially AI, having some more default templates and views reports would be helpful. **What problems is DX solving and how is that benefiting you?** I use DX to evaluate productivity and performance, gaining insights into how often engineers ship code or defects, and analyzing AI tooling effectiveness and costs. **Official Response from Taylor Bruneaux:** > Thanks James. The SQL access use case you're describing is one of my favorites. Being able to drill into AI token usage and efficiency at that level of granularity is exactly the kind of measurement flexibility we want leaders to have. Glad the Slack integration is doing its job on PR cycle time too. The point on AI default views is fair. There's a lot of signal available and we know the starting point matters. Appreciate you flagging it! ### 3. Insightful Team Stats with Scope for UI Improvement **Rating:** 3.5/5.0 stars **Reviewed by:** Alessandra G. | Mid-Market (51-1000 emp.) **Reviewed Date:** May 15, 2026 **What do you like best about DX?** I use DX for tracking my team's statistics, mostly productivity. I appreciate having reliable numbers and graphs that I can efficiently share over Slack. The team's stats board is great because it puts a lot of information in one place, giving me a clear picture. I also find the feature that allows me to comment on results or on topics identified as pain points very useful, as it facilitates starting discussions in the thread itself. Additionally, it helps me understand the productivity of team members and identify support trends and ongoing issues. Setting up DX for my personal account was very easy. **What do you dislike about DX?** I don't find it very intuitive to reach sections. Now of course I've learned, but at the beginning I was having trouble reaching the pages and dashboards that I needed, and had to rely on saved links. **What problems is DX solving and how is that benefiting you?** I use DX for tracking team statistics and productivity, sharing reliable numbers through Slack. It helps understand team productivity and support trends, and features a stats board and comment function for addressing issues and starting discussions. **Official Response from Taylor Bruneaux:** > Really glad the stats board and Slack sharing are pulling their weight for you, Alessandra. The commenting feature is a good one to call out. Being able to start a conversation directly in the context of a pain point is a lot more useful than taking it somewhere else to discuss. The navigation learning curve is real, especially early on. Good feedback for us and our team—thanks! ### 4. Insightful Metrics, But Needs Improved Management Views **Rating:** 4.5/5.0 stars **Reviewed by:** Bobby M. | Mid-Market (51-1000 emp.) **Reviewed Date:** May 14, 2026 **What do you like best about DX?** I really appreciate the different types of metrics that DX offers, as they provide great insights into my team's performance. The automated nature of data availability is also a standout feature, making it really convenient to access necessary information quickly. I find the industry benchmarks and comparison data with other teams in my organization extremely helpful. This functionality allows me to understand if my team is lagging or leading, and it helps me identify areas for rewarding or improving performance. **What do you dislike about DX?** The ability to add management layers is currently not possible. If I have two teams, I'm forced to choose a team and unable to get a combined view of everyone across both teams, while retaining the ability to breakout by those individual teams. **What problems is DX solving and how is that benefiting you?** I use DX to gain insights into team performance, providing visibility into scope, velocity, and impact. It benchmarks against other teams and industry standards, helping me identify areas to improve or reward. The automated data availability is extremely helpful. **Official Response from Taylor Bruneaux:** > Bobby, the benchmarking use case you're describing is one of the most powerful ways to use DX. Having a calibrated read on where your team stands relative to peers and industry data makes the performance conversation a lot more grounded. The multi-team rollup limitation is a specific and fair callout. That kind of hierarchical view matters a lot when you're managing across multiple teams and need both the aggregate picture and the breakdown. I'll flag to your customer team that this is a view that you need. Thanks! ### 5. Comprehensive Metrics with Some Usability Challenges **Rating:** 4.5/5.0 stars **Reviewed by:** Nick M. | Enterprise (> 1000 emp.) **Reviewed Date:** May 14, 2026 **What do you like best about DX?** I find the regular snapshot feature very helpful in identifying issues around processes or ways of working that might not otherwise surface. The engineering metrics are great for seeing how teams are generally performing and spotting anything that might be slowing them down. I really like the comprehensive metrics provided by DX. Although I could potentially gather these myself with some digging, it's reassuring to know that the calculations have been rigorously done. The true Throughput metric, in particular, is very useful for quantifying the complexity of work delivered by the teams, as opposed to just plain velocity. Additionally, I really like that we can use AI to prompt, even though there were some challenges in getting the right queries. **What do you dislike about DX?** I've found the Data Studio a little hard to use without first being shown. If it was more intuitive I would likely use it more. I really like that we can prompt through AI, but I had some trouble getting the right queries from the prompts. It could just be that the data I was requesting wasn't available though. **What problems is DX solving and how is that benefiting you?** DX helps identify process issues through regular surveys and improves performance tracking with engineering metrics. The True Throughput metric is particularly beneficial in quantifying work complexity over just velocity. **Official Response from Taylor Bruneaux:** > Nick, the True Throughput callout is spot on. Velocity alone doesn't tell you much about the complexity or weight of what a team is actually delivering, and that distinction matters when you're trying to have an honest conversation about performance. The Data Studio feedback is useful. It's a powerful feature but the learning curve is real without some initial guidance. Same goes for the AI prompting experience. The query results are only as good as the data available, so that context is helpful to have. Our team is here to help: reach out if we can ever help you navigate the platform or craft queries. ### 6. Very collaborative experience using DX **Rating:** 4.5/5.0 stars **Reviewed by:** Missy R. | Software Engineering Manager, Small-Business (50 or fewer emp.) **Reviewed Date:** February 27, 2026 **What do you like best about DX?** DX has an intuitive, easy-to-use interface that makes it genuinely user-friendly. I also really appreciate that they surface the queries used to populate metrics, so I can dig in when needed and create custom metrics that are a better fit for the questions I’m trying to answer. They’ve also been incredibly collaborative and responsive whenever I have questions or run into issues, and it’s clear they take the quality and usability of their product seriously. Even though we’re a smaller account for them, they’ve taken my feedback seriously and worked to implement product changes that better fit our engineering use case. I’ve been very impressed with that. It's a decently pricey product and I was concerned at first that it would be difficult to prove out it's value. That said, we've gotten great feedback from DX that have led to needed changes in our department. Along with that value and with how much of a partnership we've had with them, it has made it worth it to me. **What do you dislike about DX?** It’s hard to build a product that’s flexible enough to fit everyone’s use case while still being opinionated enough to avoid becoming a complete mess. Overall, I think they strike that balance very well. That said, it would be nice if a few areas were a bit more customizable. It’s not a major complaint, just a “nice to have.” **What problems is DX solving and how is that benefiting you?** DX has been a useful tool for putting real data behind how teams and individuals are performing. As a manager, the insights I get from this software have helped me coach people on my team more effectively and with more confidence. We’ve also been able to use what we find in the app to set clear team goals around efficiency improvements and track progress based on the data. **Official Response from Taylor Bruneaux:** > Missy, this genuinely made my day to read. Knowing your feedback has translated into real product changes is exactly the kind of relationship we want with every customer. Really glad the query transparency is useful too.On the customization front, I'll raise that internally. Your framing of the balance between flexibility and having a clear point of view is really helpful. Thanks for taking the time to write this up! ### 7. Streamlined Feedback with Robust Analytics **Rating:** 4.0/5.0 stars **Reviewed by:** Bhavik H. | Director of Software Engineering, Enterprise (> 1000 emp.) **Reviewed Date:** May 13, 2026 **What do you like best about DX?** I find DX to be a valuable tool for supporting day-to-day operational activities by providing a structured and efficient mechanism for collecting feedback, insights, and operational inputs across teams. I like how the platform simplifies survey creation and distribution while giving timely visibility into responses and trends. One of DX's key strengths is its ease of use and accessibility, which encourages broader participation and helps us gather actionable information quickly. The ability to centralize operational feedback has improved transparency, alignment, and responsiveness across stakeholders. I appreciate how DX helps streamline communication loops and reduce manual efforts associated with traditional feedback collection methods. Its reporting and tracking capabilities support leadership visibility and follow-through on identified actions. I also find the integration with my internal system quite robust. The enhanced analytics are great for transforming survey feedback into actionable insights, enabling faster identification of operational challenges, trends, and improvement opportunities, supporting more data-driven decision-making and better prioritization. DX provides an intuitive and efficient way to collect operational feedback with strong visibility into responses and trends, which supports faster decision-making and continuous improvement. The initial setup wasn't hard, and the provided examples were helpful. **What do you dislike about DX?** Maybe the analytics can be made more better by adding a rich interface, some graphs perhaps. **What problems is DX solving and how is that benefiting you?** I use DX to support day-to-day operations, streamline communication, and reduce manual feedback collection efforts. It centralizes operational feedback, improving transparency and responsiveness. Enhanced analytics transform feedback into actionable insights, boosting decision-making and leadership visibility. **Official Response from Taylor Bruneaux:** > Thanks for taking the time to write this up, Bhavik. Closing the loop between feedback collection and leadership visibility is one of the harder operational problems to solve, and it's good to know the platform is making that easier for your team. Appreciate the note on analytics richness too. More visual depth in how data is surfaced is a fair ask. I'll flag this to your customer team to walk you through some of our current visualizations. ### 8. Out of the Box Software Development Measurements **Rating:** 5.0/5.0 stars **Reviewed by:** Jon David I. | Mid-Market (51-1000 emp.) **Reviewed Date:** May 12, 2026 **What do you like best about DX?** I like how DX provides built-in comparisons, measuring against industry standards or our own past reporting periods. It aggregates data across multiple tools, which means I don't have to implement something in-house to derive insights from disparate systems. DX already shows the core metrics for software development, which are the specific metrics I'm looking for. It also has integrations with our GitHub, JIRA, and more, which is great. Plus, I use it in Slack to send AI-generated summaries on progress from my teams. As an individual user, I found the initial setup to be easy. **What do you dislike about DX?** It's not always intuitive if you want to drill down into a specific report, or be able to compare individual cohorts to each other if those aren't already defined in DX. It's frustrating when I feel too locked into their predefined filters and reports without the flexibility to drill in a different way I want. Sometimes filter facets are only single select when I'd like to select multiple of that same facet type. **What problems is DX solving and how is that benefiting you?** I use DX to identify improvement areas and track progress in development teams. It aggregates insights from tools like GitHub, Jira, and provides built-in comparisons which prevents the need for in-house solutions. **Official Response from Taylor Bruneaux:** > Jon David, thanks for the thoughtful write-up. The aggregation across GitHub, Jira, and other tools is a big part of what makes the out-of-the-box metrics actually usable without a custom build, so glad that's saving your team real work. The filter flexibility feedback is specific and fair. Single-select constraints and limited drill-down paths are the kind of friction that adds up quickly when you're trying to answer a question the predefined views don't cover. I'll reach out to your customer team to work closely with you on building customizations. ### 9. Insightful Metrics, Easy Setup, Room for Improvement **Rating:** 4.0/5.0 stars **Reviewed by:** bhumik s. | Software Engineering Manager, Small-Business (50 or fewer emp.) **Reviewed Date:** May 12, 2026 **What do you like best about DX?** I like the way DX is able to pick up some KPIs and it's very generic and broad, yet the KPIs are still meaningful. It cuts through different programs, different projects effectively. I also find it meaningful because it gives me insights into our code velocity, especially after integrating AI into our workflows. It helps identify bottlenecks and areas to focus on, boosting our engineering throughput. Additionally, the setup was quite easy due to my organization's infrastructure team and all I had to do was ensure there were no mistakes in our team settings. **What do you dislike about DX?** I feel like at times, some of the settings that I wanna change, like, there might be, things that the developers are working on, and it does not get captured very well. Change. Or simply, like, if I added a wrong GitHub username to a developer, I was not able to change that. **What problems is DX solving and how is that benefiting you?** I use DX to get engineering metrics, identifying bottlenecks in our SDLC developer inner loop, which helps us focus and improve engineering throughput. It provides meaningful insights into code velocity, especially after integrating AI into our workflows. **Official Response from Taylor Bruneaux:** > Bhumik, measuring code velocity before and after an AI integration is one of the more compelling ways to actually validate whether the tooling is paying off, so glad that's coming through clearly. The GitHub username and settings flexibility issues are frustrating ones, especially when something as basic as correcting a username feels harder than it should. I recommend flagging these ASAP to your account team who can help you out swiftly Thanks for your review! ### 10. Centralized Metrics and Actionable Insights **Rating:** 5.0/5.0 stars **Reviewed by:** Antti M. | Software engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** May 12, 2026 **What do you like best about DX?** I like the ease of use of DX and how it produces useful information for our teams to improve. We have found the snapshot surveys very informative, a good way to get input from our developers about what's slowing them down or what they wish us collectively to improve on. These are very actionable points that we then have worked on. Additionally, the initial setup was rather painless, thanks to the helpful team at DX. **What do you dislike about DX?** Maybe some of the reports have been a bit confusing as to how they are produced, and this is tricky as if one reads them incorrectly, it is easy to draw very different conclusions. For example, the 'Innovation ratio' report. It is rather unclear on how it deduces what is 'innovation' work. **What problems is DX solving and how is that benefiting you?** I use DX for tracking development velocity and quality, providing centralized visibility for DORA metrics, and benchmarking against others. **Official Response from Taylor Bruneaux:** > Thanks for this, Antti. Using snapshot feedback to surface what's actually slowing developers down and then acting on it is exactly the cycle those surveys are designed to support. Really glad that's been working for your team. The Innovation ratio point is well taken. Any metric where the methodology isn't immediately transparent creates room for misinterpretation, and misreading that one in particular could lead to pretty different conclusions about where to focus. Your account team is on-call to help with any of these reports, so please reach out to learn more! ### 11. Data-Driven Clarity for Team Management **Rating:** 5.0/5.0 stars **Reviewed by:** Janey L. | Engineering Manager, Enterprise (> 1000 emp.) **Reviewed Date:** May 12, 2026 **What do you like best about DX?** I really appreciate the clarity DX gives me. With a small team, it's easy to assume things are on track, but DX backs that up with data, which is great. The dashboard offers a quick snapshot of the team's progress, and I can see if we're on track or slipping without going through complex tools. It saves me time and makes my check-ins more productive. Specifically, the cycle time and throughput metrics are helpful for understanding our delivery speed, and the PR and code review analytics are really useful. **What do you dislike about DX?** I think some of the metrics and visualizations can be more compact, and there could be AI powered insights or summaries which could save me even more time. **What problems is DX solving and how is that benefiting you?** I use DX to track team progress and monitor delivery speed. It provides visibility without micromanaging, helps spot bottlenecks, and backs insights with data for productive check-ins. **Official Response from Taylor Bruneaux:** > Janey, this is such a relatable scenario. Small teams can feel like everything is fine right up until it isn't, so having cycle time and throughput data to sanity-check your instincts is genuinely useful, not just nice to have. The AI-powered summaries idea is a good one. This is something that we've begun to roll out, so I recommend connecting with your customer team to see our features here! ### 12. Invaluable for Team Performance Monitoring **Rating:** 5.0/5.0 stars **Reviewed by:** Jason B. | Senior Software Engineer Team Lead, Mid-Market (51-1000 emp.) **Reviewed Date:** May 12, 2026 **What do you like best about DX?** I find the quarterly snapshots in DX incredibly useful because they expose issues with our process and provide the tools to determine if the changes we make based on those issues are actually making a difference. This feature allows us to break down answers by team, monitor stats like PR Cycle Time and AI usage, and find out what parts of our process are working well. **What do you dislike about DX?** The list of reports can be a little overwhelming, making it hard to know what I should be paying attention to. Also the time in hours can be confusing to know if it's working hours vs clock hours, and how they calculate business hours. **What problems is DX solving and how is that benefiting you?** I use DX to monitor team performance and track process effectiveness, exposing areas for improvement. It provides insights on PR Cycle Time and AI usage to determine if we're on the right track. **Official Response from Taylor Bruneaux:** > Love seeing this use case, Jason. A lot of teams use snapshots to identify problems and stop there. The fact that you're looping back to check whether your fixes are actually landing is the whole point. The hours ambiguity is a fair callout and more confusing than it should be. When cycle time is your north star metric, working hours vs. clock hours is not a small distinction. Your customer team can walk through this with you! ### 13. Great for Quarterly Tracking, but Needs More Relevant Questions and Better Reporting **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** May 13, 2026 **What do you like best about DX?** Running this survey on a recurring basis, with a measurement every three months, really helps track evolution and improvement over time. Comparing results against other teams in the organization, or even against the industry, also helps identify and better understand the areas where we can improve. **What do you dislike about DX?** Some questions don’t apply to our team, and that creates friction when we have to complete them. Also, the reporting tool has a lot of room for improvement. I’d really appreciate an integration with a retrospective tool and with Jira tickets, so that when we identify action items, we can track them more easily. **What problems is DX solving and how is that benefiting you?** Mostly it helps to identify problems on the developers experience, being standarize it covers a lot of areas and help us focus on the weakest ones. It gathers a lot of information than then we need to analyze and process to improve **Official Response from Taylor Bruneaux:** > Really appreciate you taking the time to share this. Quarterly tracking with consistent benchmarks is one of the more powerful ways to build a credible improvement narrative over time, so it's good to know that cadence is working for your team. The question relevance friction and the additional Jira integration ask are both worth calling out. Being able to close the loop from identified action items into actual tracked work is a real gap, and the specificity here is helpful. ### 14. Comprehensive Surveys with Peer Benchmarks That Drive Clear Improvement Actions **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Leisure, Travel & Tourism | Enterprise (> 1000 emp.) **Reviewed Date:** May 14, 2026 **What do you like best about DX?** The survey’s comprehensive and objective framing helps us identify the areas that need attention. The platform’s peer-comparison offering also helps us understand where we stand and where to invest further. The specificity around Front End/ Back End / Platform/ Data Layers helps us get closer to improvement actions **What do you dislike about DX?** While most aspects of Developer Productivity are covered, aspects around Dev Operations and Tech Operations (post production) can be improved. Any engineer still has to spend decent time in operational aspects beyond being Goalie/on-call, the productivity improvements intelligence for these are areas to be improved on DX **What problems is DX solving and how is that benefiting you?** Problem/ Gap identification is the biggest area on where the DX helps, the best part being unification of survey and system data for a complete view of developer productivity. The qualitative inputs help in getting to nuances that are not captured in the objective numbers **Official Response from Taylor Bruneaux:** > Really appreciate the detailed feedback here. The layer-specific breakdowns resonating with your team is great to hear, and the framing around combining qualitative and system data to get to the nuances is exactly the outcome we're going for. The Dev Ops and Tech Ops coverage point is well taken. Operational load beyond on-call is a real part of how engineers spend their time and it's a meaningful gap to flag. ### 15. Data-Driven Developer Experience Insights That Help Us Prioritise What Matters **Rating:** 4.5/5.0 stars **Reviewed by:** Martin V. | Staff Software Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** February 06, 2026 **What do you like best about DX?** One of the best things about DX is that it replaces assumptions with a clear, data-driven understanding of developer experience. Instead of relying on intuition and assumptions, DX gives us measurable, comparable insights into where friction actually exists, whether it's in tooling, documentation, cross-team collaboration, or pipelines and delivery flows. It provides concrete data to validate whether our initiatives are truly moving the needle for product teams, giving us a much stronger foundation for prioritizing work and aligning improvements with real team needs. As a platform domain, DX is especially valuable because it highlights where we can have the greatest positive impact across the organisation. When DX shows that certain issues (e.g., poor documentation quality) are common across the organisation, it helps us prioritise systemic improvements rather than local optimisations. It essentially gives us a shared compass for where our work will deliver the most value. In short, DX helps ensure developer time is spent where it creates the most value, and that our technical decisions are backed by evidence rather than opinion. **What do you dislike about DX?** The main drawback is that DX still requires a certain level of maturity in how teams adopt, interpret, and act on the data. Without that maturity, insights risk becoming passive dashboards rather than meaningful drivers of change. Also, DX is primarily designed with software engineering teams in mind. This makes it less directly applicable to more traditional infrastructure‑focused teams, where workflows and responsibilities differ from the assumptions built into the model. It also demands a mindset shift: Teams need to actively work with the insights and continuously adjust their practices based on the data. This takes time and discipline, and there can be some initial overhead before the value becomes obvious. In short, DX is powerful, but it requires commitment, behavioral change, and continuous refinement to reach its full potential. **What problems is DX solving and how is that benefiting you?** DX helps us understand and identify friction and bottlenecks across the organisation - based on data, not assumptions. This transparency allows us to pinpoint the areas where developer time is being lost and where improvements will have the greatest impact. DX also highlights which issues affect the most teams and where improvements will have the largest impact. This helps us in our platform domain to focus on initiatives that raise the baseline for everyone. Whether it's improving documentation, improving shared tooling, or CI/CD foundations, DX guides us towards initiatives with the highest leverage. DX gives platform teams and product teams a shared picture of where improvements matter most. That alignment ensures that shared investments (e.g., in tooling, observability, or build performance) target the areas with real, proven impact. Overall, DX enables more consistent prioritisation, stronger cross‑team alignment, and more predictable improvement in both developer experience and broader technical health. **Official Response from Taylor Bruneaux:** > Martin, the "shared compass" framing is exactly right and a great way to put it. Really glad DX is helping your platform domain prioritize systemic improvements over local ones! That's one of the harder problems to solve at enterprise scale. Your point about maturity is fair and honestly something we think about a lot. The data is only as valuable as the organizational habits built around it, and that takes real work. Thanks for such a well-considered review. ### 16. DX Turns Developer Insights into Data-Driven Improvements at Scale **Rating:** 5.0/5.0 stars **Reviewed by:** Sujith C. | VP of Engineering, Mid-Market (51-1000 emp.) **Reviewed Date:** February 05, 2026 **What do you like best about DX?** 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 DX?** 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 DX 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. **Official Response from Taylor Bruneaux:** > Sujith, this is a really thoughtful breakdown of how you're using DX across a complex org and it's great to see the platform working at that scale. The combination of biannual survey cycles with Jira and GitHub signal to get at the "why" behind productivity trends is exactly the use case we design for. On the calendar integration, the ability to filter out specific meeting types to get a cleaner picture of deep work time is a really smart ask and we'll raise directly with the team so it gets into the right hands. Appreciate you taking the time to write this up in such detail. ### 17. Best-in-Class Tool for Measuring Developer Experience **Rating:** 4.0/5.0 stars **Reviewed by:** Jonas Alslev R. | Software Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** February 03, 2026 **What do you like best about DX?** 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 DX?** 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 DX 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. **Official Response from Taylor Bruneaux:** > Really glad DX is giving your Developer Tooling team a clear signal on what engineers actually need, Jonas. That's exactly the use case we built for. On the ArgoCD integration setup, that's specific and helpful feedback. I'll make sure it gets to the right people. Appreciate you flagging it. ### 18. Snapshots, Triaging & PlatformX: Essential Insights for Better Prioritization **Rating:** 4.0/5.0 stars **Reviewed by:** Nikolai Emil D. | Senior Software Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** February 03, 2026 **What do you like best about DX?** 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. **What do you dislike about DX?** 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. **What problems is DX 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.”. **Official Response from Taylor Bruneaux:** > It’s fantastic to hear that Core4 and PlatformX are serving as a guiding star for your tooling initiatives. We hear you on the adoption curve, and our account managers are ready to partner with you to provide the practical examples and process integration your teams need to feel confident. Thanks for the review, Nikolai! ### 19. Insightful Tracking and Action Feedback **Rating:** 5.0/5.0 stars **Reviewed by:** Patrick d. | Small-Business (50 or fewer emp.) **Reviewed Date:** May 12, 2026 **What do you like best about DX?** I like that DX makes it easy to get insights from team members and track actions for issues with low scores. The tracking mechanism is great because I can easily see whether the actions are having results. Registering an action for a given subject and seeing the improvements in the next measure is particularly helpful. Compared to several types of polls we use, DX stands out with its tracking capabilities. **What do you dislike about DX?** In my company the use of DX is not anonymous, which makes some people insecure about answering it. I'm not sure if this is a choice or a limitation of the platform. **What problems is DX solving and how is that benefiting you?** I use DX for assessing developer experience. It makes it easy to get insights from the team and track actions on low scores. I like the tracking mechanism; it shows if actions result in improvements. **Official Response from Taylor Bruneaux:** > Patrick, glad the action tracking is clicking for you. Being able to register an issue, take action, and then actually see it move in the next measurement cycle is the feedback loop we want teams to have. Most survey tools stop at the data collection step. On the anonymity question, survey responses are anonymous, but comments are not by design since they're meant to spark real conversations. I recommend checking in with your account team to confirm DX is best configured for your org! ### 20. Best in Class - Comprehensive Qual + Quant Data Framework for Developer Experience for AI Adoption **Rating:** 5.0/5.0 stars **Reviewed by:** Greg S. | Chief Software Architect, Mid-Market (51-1000 emp.) **Reviewed Date:** February 20, 2026 **What do you like best about DX?** The DX user interface is extremely easy to use, and it provides highly valuable data insights across the entire system development life cycle. The customer success team is outstanding. They're extremely helpful with questions and ongoing suggestions on how to improve your SDLC based on the insights that DX provides. The implementation is pretty easy, and you can generally set it up yourself. **What do you dislike about DX?** There are so many reports available that it can be a bit overwhelming to figure out which one to use. **What problems is DX solving and how is that benefiting you?** We have a fairly large R&D organization that, historically, hasn’t delivered through the most efficient processes. DX provides both AI adoption metrics and clear visibility into where we can improve across our SDLC. It enables engineering managers to look at opportunities tactically and strategically, so they can see where other teams could improve speed and quality. **Official Response from Taylor Bruneaux:** > Greg, this is a really meaningful review to read, especially hearing about enabling both tactical and strategic decision-making across a large R&D org. That's exactly the problem we set out to solve, and it's validating to hear it working at that scale. The point about report overload is well taken — having comprehensive data is only useful if you can find the right starting point, and that's an area we're actively thinking about as we roll out more AI insights. Really glad the customer success team has been a strong partner throughout. Thanks for taking the time to write this up so thoroughly. ### 21. Empowers Team Engagement with Insightful Features **Rating:** 4.5/5.0 stars **Reviewed by:** Stephanie C. | Mid-Market (51-1000 emp.) **Reviewed Date:** April 14, 2026 **What do you like best about DX?** I like that we managed to get 100% participation from our engineering team on our second survey, which usually means they found our actions useful and felt their voices were heard. The heatmap features are the most fun, helping me identify problem areas and facilitating discussions about where we should spend our time for improvements and learning from what other teams are doing well. **What do you dislike about DX?** Since our team is only focusing on a few metrics or graphs at a time, it takes a few extra seconds to find the right ones, but I haven't tried to customize the interface or build team specific views of graphs yet. The default being 'industry p50' I'm always skeptical of, so I usually change that. Especially if your team has conducted multiple snapshots, defaulting it to the previous one seems more useful. **What problems is DX solving and how is that benefiting you?** DX provides both qualitative and quantitative insights to improve developer experience. I enjoy the heatmap features that help identify problem areas and facilitate broader engineering discussions. **Official Response from Taylor Bruneaux:** > We really appreciate the review! I love to hear you reached 100% participation: that is a huge win for team engagement and the success of your program. That's also a great note about customizing your benchmarks: our team can help configure this for you. Thanks for the great feedback! ### 22. Streamlined Feedback Collection with Room for Growth **Rating:** 4.0/5.0 stars **Reviewed by:** Jelle V. | Mid-Market (51-1000 emp.) **Reviewed Date:** April 08, 2026 **What do you like best about DX?** I appreciate that DX is easy to use for both the people filling in the survey and those who need to triage the results. It's convenient to have a quick overview of all the comments, which helps to quickly summarize common pain points across various teams and their members. Having a single location for feedback with transparency on progress over time is valuable, especially since we have multiple teams working separately and don't have to manage this manually per team. **What do you dislike about DX?** I think it would be great to add actions per driver during the triage. Now this is still a manual step we perform after the triage. I would mind some graphs to easily see the score of each driver over team and being able to click on points in the graph to quickly see patterns on why it changed. We want to be able to detect which actions completed had impact on the scores. **What problems is DX solving and how is that benefiting you?** DX helps gather and centralize feedback, providing transparency on progress. It's easy to use and offers a quick overview of comments, helping to identify common pain points. It cuts manual work by using a single tool across separate teams. **Official Response from Taylor Bruneaux:** > Jelle, glad the feedback collection experience is working well for your team. We're always iterating on the platform and love hearing where customers see opportunity — if AI-powered pattern surfacing is on your wishlist, getdx.com/ai-recommendations/ is worth a look at what we've been building. ### 23. Effortless Data Sharing with Insightful Analysis **Rating:** 5.0/5.0 stars **Reviewed by:** Panagiotis T. | Enterprise (> 1000 emp.) **Reviewed Date:** April 24, 2026 **What do you like best about DX?** I like using DX because it's an easy platform for everyone in the company, which makes collecting and sharing survey results straightforward. The ease of use means there's a big percentage of participation, and management can extract insights and action items quickly. The nice reports that DX provides are another positive aspect, making the data useful and presentable. Additionally, the initial setup of DX was easy and nice, which added to the overall positive experience. **What do you dislike about DX?** I'm pretty much happy with it. Maybe more ways to aggregate and compare data. I'd like to be able to pick specific performance views and add them to a comparison view so I can compare different views. **What problems is DX solving and how is that benefiting you?** I use DX for collecting and sharing survey results. It provides an easy platform for the whole company, generates nice reports, and helps management quickly extract insights and action items. **Official Response from Taylor Bruneaux:** > It’s awesome to hear that the platform is making things easier for everyone at the company—seeing high participation rates is exactly what we aim for. We're also glad the initial setup felt smooth and that the reports are hitting the mark for your management team. I've flagged for your account manager to dive into the additional ways that we're able to compare data with your team. Thanks Panagiotis! ### 24. Improves Feedback Efficiency but Needs Better AI Summaries **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User | Mid-Market (51-1000 emp.) **Reviewed Date:** April 07, 2026 **What do you like best about DX?** I find the developer experience surveys in DX valuable as they provide actionable feedback from developers. These surveys are crucial for me to gather more feedback and make improvements. **What do you dislike about DX?** I'd like you to use AI to create better summaries of the survey review feedback. You have it already, but it's not as good as it could be, imo. It'd be nice if you could just run improved AI summarization tooling on all the feedback and have it spit out a nice, summarized, actionable report to everyone on the team immediately to discuss, and we can tweak / edit as needed. I know DX takes a more team-based approach to dev metrics, but it's a real gap in what we need sometimes. Sometimes we need to know where a dev isn't pulling their weight but it's not showing up as much because others are taking on more than their share of the slack (but not saying anything because they don't want to be a narc). **What problems is DX solving and how is that benefiting you?** DX provides actionable feedback from developers, helping me gather more input to make improvements. **Official Response from Taylor Bruneaux:** > Hi there! Just this week, we've released a slew of new and improved AI features that do exactly what you're looking for: https://getdx.com/blog/introducing-the-new-dx-ai-chat/ and https://getdx.com/blog/introducing-pulse/. Please reach out to us if you'd like a walkthrough! ### 25. Helpful, lightweight way to check whether changes are actually helping **Rating:** 4.5/5.0 stars **Reviewed by:** Andrew W. | Software Engineering Manager, Mid-Market (51-1000 emp.) **Reviewed Date:** January 15, 2026 **What do you like best about DX?** 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. **What do you dislike about DX?** 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 DX 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. **Official Response from Taylor Bruneaux:** > Andrew—it’s great to hear that snapshots are helping to confirm whether process changes are actually reducing friction. We completely agree that the data is best used alongside 1:1s and retros to give a full picture of team health and help your engineers feel heard. ### 26. A tool to catch problems and communicate with stakeholders about engineeringexcellence **Rating:** 4.5/5.0 stars **Reviewed by:** Saulius S. | Staff Back-End engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** May 21, 2025 **What do you like best about DX?** I like that DX allows teams to point to the most painful blockers. There are many predefined areas to choose from, therefore increasing responses. People tend to forget/overlook problems if they are only asked to remember what's blocked on the spot. This is not the case with DX. I love how easy it is to configure Service catalog and Scorecards. I have received a lot of help from the AI query builder, which makes accessing custom data easier. **What do you dislike about DX?** It's sometimes hard for me to separate my problems (if I work with a very small area of code/functionality) from the difficulties the company has (different teams have). This is partly because I'm working in a Devex team. Therefore, I need to think about how to improve work for other teams. **What problems is DX solving and how is that benefiting you?** It helps me see the problems developers face and which they consider the most urgent to fix. Each team ends the DX survey by choosing which (up to three) issues are the most relevant, which can be solved by the team, and which require help from the Devex team. This allows me to focus on the most important issues for developers. It is a great tool for providing statistics-based arguments to stakeholders about engineering excellence. To present an objective argument for why the company needs to spend time improving engineering quality. ### 27. Clear, Easy-to-Use Surveys via DX **Rating:** 5.0/5.0 stars **Reviewed by:** Inga V. | Frontend Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** March 18, 2026 **What do you like best about DX?** I like clear surveys that we get via this tool. I use DX as an employee in an engineering position. Our organisation survey us to discover pain points and areas that we are doing great in. It lets us see how we are doing compared to the best of engineering teams. **What do you dislike about DX?** I think this tool has a lot of value to managers but as an individual contributor I don't use this tool that much, I only answer surveys. Maybe it should be made clearer somehow what value in can bring to others not only managers **What problems is DX solving and how is that benefiting you?** It helps our organisation to see what areas need improvement and what areas we are doing great in **Official Response from Taylor Bruneaux:** > Inga, really glad the survey experience feels clear and low-friction. That matters a lot when you're the one being asked to take time out of your day! Your point about IC visibility is a great one, and something we think about. The idea behind DX is that surfacing these insights leads to real changes in how individual developers work: fewer blockers, better tooling, less time lost to friction. Hopefully you start to feel that loop closing on your end too. Appreciate you sharing your side of the DX experience! ### 28. Seamless Slack Integration Enhances Team Engagement **Rating:** 4.0/5.0 stars **Reviewed by:** Stafford S. | Senior Lead Software Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** April 07, 2026 **What do you like best about DX?** I appreciate how DX integrates into Slack, allowing for a high level of engagement as it messages engineers directly when their input is needed. This is particularly effective because our engineers are consistently on Slack, which makes it a more efficient communication method than email. I also like the product a lot and find it easy to set up; our lead engineer volunteered to handle the setup, and there have been no complaints. **What do you dislike about DX?** The comments in the surveys cannot be anonymous. Some engineers might want to share input anonymously that they don't want public. It would be good to have more visualization options in the reports. **What problems is DX solving and how is that benefiting you?** I use DX to find gaps in documentation and processes by polling 150+ engineers, improving our processes. It integrates with Slack, allowing direct communication and higher engagement than email. **Official Response from Taylor Bruneaux:** > Thanks Stafford, high engagement through low-friction touchpoints is the whole game — glad Slack is delivering that for your team. → If you're looking to learn more about our approach to anonymous comments, we dive into this in our helpdocs: https://docs.getdx.com/knowledgebase/why-are-comments-non-anonymous/. → If you want to layer in workflow-level signals on top of the survey data, getdx.com/workflow-analysis/ pairs well with what you're already doing! ### 29. DX Delivers Clear Org-Wide Visibility with an Easy UI and Fast, Helpful Support **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** May 12, 2026 **What do you like best about DX?** DX is a great tool to give me high-level visibility across my organization. The UI/UX is easy to use and integrates well with the tools in our organization. The support team is great. Any time I have had an issue, they respond quickly, including bug fixes. It's been great to help us understand performance bottlenecks in our SDLC and AI adoption. **What do you dislike about DX?** There is not much I dislike about DX. I think that it does a great job at engaging the organization through the survey tool, and the team behind it has been receptive to feedback. **What problems is DX solving and how is that benefiting you?** Helping to get a holistic view of our engineering teams, and converting that to measurable data across our various systems. **Official Response from Taylor Bruneaux:** > This is a great one to read. Org-wide visibility that actually connects to measurable data across systems is a hard problem, and it means a lot to hear it's working that way in practice. Really glad the support experience has been solid too. The team takes that seriously, so good to know it's coming through. ### 30. Transparent Pain Point Insights with Concrete Data That Drives Action **Rating:** 4.5/5.0 stars **Reviewed by:** Marcel G. | Student Developer Experience Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** February 04, 2026 **What do you like best about DX?** 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 DX?** 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 DX 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. **Official Response from Taylor Bruneaux:** > Marcel, glad the dashboard is making it easy to surface and act on pain points across the org. The suggestion around tangible use cases tied to specific pain points is a good one and I'll raise it internally. In the meantime, DX AI is worth exploring for exactly that, it surfaces actionable recommendations directly from your data: getdx.com/ai-recommendations/. ### 31. Centralized Collaboration and Clear Visibility for Deployments and Incidents **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Financial Services | Mid-Market (51-1000 emp.) **Reviewed Date:** May 10, 2026 **What do you like best about DX?** What I like most about DX is how it centralizes collaboration and operational visibility across teams. At Pliant GmbH, where engineering, product, operations, and compliance work closely together on payment infrastructure and card management features, DX helped reduce the fragmentation that often comes from relying on multiple tools in parallel. One of the most valuable benefits for me was having a clearer, shared overview of ongoing projects, deployments, and incident handling in a single place. For example, during API rollout phases or payment-processing updates, DX made it much easier to coordinate between developers, product managers, and operations without depending entirely on scattered Slack conversations and Jira tickets. I also appreciated how DX strengthened our incident-response workflows. When issues were detected through Datadog alerts, teams could coordinate faster, assign ownership more clearly, and track progress in a more structured way. In a fintech environment where response times and operational reliability are critical, that added visibility and coordination made a noticeable difference. **What do you dislike about DX?** One thing I disliked about DX is that some workflows could feel too rigid when handling more complex, cross-functional processes. At Pliant GmbH, teams like engineering, compliance, operations, and product management often work in very different ways, and adapting DX to fit all of those approaches sometimes meant relying on additional manual workarounds. Another challenge was the depth of reporting and analytics. DX offered solid high-level visibility, but there were cases where teams needed more granular insights. For instance, during larger payment infrastructure rollouts or incident reviews, it would have been helpful to have more advanced dashboards, clearer dependency tracking, and stronger historical analytics without having to rely on external reporting tools. There were also occasional limitations with integrations. Since we used Jira, Slack, GitHub, Confluence, and Datadog at the same time, keeping workflows fully synchronized sometimes required extra manual coordination. Updates in one system didn’t always show up instantly or clearly across connected workflows, which could lead to duplicate follow-ups or small communication gaps. Lastly, as workflows scaled across multiple teams and projects, navigation and performance sometimes felt slower than expected, especially when working with larger operational boards or more complex project structures. **What problems is DX solving and how is that benefiting you?** DX mainly addresses issues caused by fragmented communication, limited workflow visibility, and inefficient coordination across teams. At Pliant GmbH, many teams collaborate closely on payment infrastructure, card operations, API integrations, compliance processes, and customer-facing product features. Before DX, a lot of information was scattered across Slack conversations, Jira tickets, Confluence pages, and monitoring tools, which made it difficult to maintain a clear operational overview. A major benefit has been stronger cross-functional coordination. For example, during payment-processing updates or new feature rollouts, engineering, product, and operations teams can now track progress, blockers, deployment status, and ownership in a more central place, rather than relying on multiple disconnected systems. This has reduced communication overhead and helped teams move faster with fewer misunderstandings. DX has also improved incident management workflows. When Datadog alerts indicate service degradation or payment-related issues, teams can coordinate responses more efficiently, assign responsibilities more quickly, and keep better visibility into resolution progress. In a fintech environment where uptime and response speed are critical, this has directly improved operational reliability and reduced delays during incident handling. Another important benefit is the reduction in manual effort. Teams spend less time switching between tools or chasing updates across different channels, which lets them focus more on delivery, troubleshooting, and product improvements. As the company scaled, this became increasingly valuable, since operational complexity grew significantly across departments. **Official Response from Taylor Bruneaux:** > This is a really detailed and thoughtful review, so thank you for taking the time. The incident coordination use case in a fintech environment is a compelling one. When response time directly affects operational reliability, clearer ownership and progress tracking in one place makes a measurable difference. On the cross-functional workflow piece, our goal is to make the platform work for you and your use case. If you haven't already, it's worth looping in your account team to work through some of those setup questions together! ### 32. GetDX Delivers Deep Developer Insights with Powerful Survey Tools **Rating:** 5.0/5.0 stars **Reviewed by:** Rokas R. | Freelance WordPress Developer, Mid-Market (51-1000 emp.) **Reviewed Date:** January 14, 2026 **What do you like best about DX?** 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 DX?** 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 DX 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. **Official Response from Taylor Bruneaux:** > Hi Rokas—It’s great to hear that DX is helping your team pinpoint exactly where to focus, from tech debt to release processes. We really value your feedback on survey interactivity: keeping developers engaged without the fatigue is a top priority for us, and we're always looking for ways to make those check-ins feel quicker and more natural. ### 33. Insightful AI Monitoring with Extensive Connectivity **Rating:** 4.5/5.0 stars **Reviewed by:** Thomas V. | TechOps, Mid-Market (51-1000 emp.) **Reviewed Date:** April 22, 2026 **What do you like best about DX?** I love the insane number of connectors that DX natively integrates with, like Claude, Codex, Github, and Opsgenie. They connect smoothly and fetch relevant data, giving us insights into our usage. The initial setup was pretty easy and convenient too. **What do you dislike about DX?** The AI lightweight daemon for macOS feels a bit tricky to use, and visual aspects of the dashboards could be improved. Also, during deployment, running 'cat' on deployed machines exposes the API credentials to end users who have root access, which could be a security concern. **What problems is DX solving and how is that benefiting you?** DX lets me monitor AI usage in our organization while providing more visibility on AI spends, and its numerous connectors smoothly integrate tools, fetching data and offering usage insights. **Official Response from Taylor Bruneaux:** > Thanks Thomas for the great feedback! We're glad the native integrations are working smoothly for you, and we’ve noted your concerns regarding the daemon and deployment security to your CSM—they'll continue to walk you through as these features are iterated upon. ### 34. All Metrics and Reports in One Place—Easy to Navigate **Rating:** 4.5/5.0 stars **Reviewed by:** Luis G. | Engineering Manager, Enterprise (> 1000 emp.) **Reviewed Date:** May 18, 2026 **What do you like best about DX?** All metrics, reports, and information are in one place, which makes it easy to find what I need. **What do you dislike about DX?** By the way, sometimes it’s difficult to find the right information. **What problems is DX solving and how is that benefiting you?** DX lets me track key metrics for my team, and even for individual colleagues. It makes progress easy to see at a glance, which helps me stay on top of how things are going. **Official Response from Taylor Bruneaux:** > Thanks for taking the time, Luis. A single place to track what's happening across your team and individual contributors is something engineering managers tell us makes a real difference in how they run their week. Noted on finding the right information. Good to know as we think about how people move through the product. ### 35. Built with Empathy for Engineers—A Shared Language for Better Flow **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Mid-Market (51-1000 emp.) **Reviewed Date:** February 05, 2026 **What do you like best about DX?** 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 DX?** 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. **What problems is DX 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. **Official Response from Taylor Bruneaux:** > Really appreciate this review. The "shared language" framing is exactly right. On the misuse risk, you're not wrong, and it's something we take seriously. DX is built for systemic improvement, not individual surveillance. That only works when leaders set the right context upfront, and helping customers do that well is a core part of how we work. The outcomes you're describing: faster follow-ups, better participation and 30-40% less time interpreting sentiment, are exactly what we're building toward and look forward to continue to help your team achieve! ### 36. Over 95% Engagement—Enough Said **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Financial Services | Mid-Market (51-1000 emp.) **Reviewed Date:** May 20, 2025 **What do you like best about DX?** I’m genuinely a big fan of GetDX—it’s been a game changer for how we think about developer experience. From the start, it was incredibly easy to implement. Everything worked right out of the box with just a few clicks—no hassle, no setup headaches. I honestly can’t remember hitting a single issue during rollout. And whenever we’ve had questions, their support has been amazing—quick to respond and always full of helpful insights, often going deep into our own snapshot data. We don’t use it daily, but we run quarterly check-ins, and that rhythm works really well for us. The surveys give us a clear, reliable pulse on how the team is feeling, while the newly added data tools take things to the next level. Together, they allow us not only to understand sentiment, but also to validate assumptions, raise hypotheses around efficiency or friction points, and actually verify them with data. That combination has been incredibly powerful for driving more informed, evidence-based improvements. The data is simple to understand but genuinely insightful. It’s helped us structure our processes better, uncover blind spots we didn’t know we had, and—most importantly—have meaningful conversations backed by real signals rather than gut feeling. **What do you dislike about DX?** Today, DX shows you what is happening very clearly. It would be incredibly valuable if it also helped teams answer why it’s happening and what to try next, in a more personalized and context-aware way. That kind of guidance would make the insights even more actionable, especially for teams that don’t have a dedicated DX or productivity function. **What problems is DX solving and how is that benefiting you?** It helps us surface blind spots and collect honest, unbiased feedback directly from engineers—something that’s often hard to capture in day-to-day work. The triage process that follows allows us to prioritize the most impactful items and actually turn insights into action. Every quarter, we use it to benchmark our progress and check if the efforts we put in are paying off. One of the big strengths is how it combines technical data with survey feedback. That mix helps us validate assumptions and see the full picture. It also highlights gaps between teams, which opens up opportunities to share knowledge and support each other. If one team is doing particularly well in a specific area, we can learn from their practices; if another is falling behind, we know where to lend a hand. This kind of visibility not only drives individual team improvements—it helps us raise the overall bar across the entire engineering org. ### 37. Great Integrations—Especially GitHub—for Easy Developer Feedback **Rating:** 4.5/5.0 stars **Reviewed by:** Morten J. | Software Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** February 04, 2026 **What do you like best about DX?** 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 DX?** 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 DX 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. **Official Response from Taylor Bruneaux:** > Morten, glad the GitHub integration is working well and that actor identification is adding value. The API error code feedback is specific and useful. A 422 with no context is a real pain point for developers and I'll make sure that gets in front of the right people. Appreciate you flagging it clearly. ### 38. Effortless Quarterly Dev Surveys that need some refinement terms for special use cases **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Online Media | Mid-Market (51-1000 emp.) **Reviewed Date:** January 21, 2026 **What do you like best about DX?** 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 DX?** 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 DX 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. ### 39. DX Nails It: Insightful Surveys, Perfect UX, and Powerful Dashboards **Rating:** 5.0/5.0 stars **Reviewed by:** Stefano M. | Senior front-end developer, Mid-Market (51-1000 emp.) **Reviewed Date:** January 17, 2026 **What do you like best about DX?** 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. 😍 **What do you dislike about DX?** To be honest: nothing, I think the platform is perfect as it is at the moment **What problems is DX solving and how is that benefiting you?** Getting high quality, actionable, and quick insights about the devex situation **Official Response from Taylor Bruneaux:** > Stefano! It’s wonderful to hear that your experience with DX has been so positive, from the research and UX to the depth of our dashboards. We're thrilled that the platform is helping you turn that ocean of data into meaningful insights for your team. ### 40. A steady, practical way to talk about developer experience at the leadership level **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Financial Services | Mid-Market (51-1000 emp.) **Reviewed Date:** January 15, 2026 **What do you like best about DX?** 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. **What do you dislike about DX?** 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 DX solving and how is that benefiting you?** Overall, it’s been a reasonable addition to how we think about developer experience at scale. **Official Response from Taylor Bruneaux:** > It’s great to hear that the platform is helping you ground those high-level leadership talks in something more structured than just stories. We really value your perspective on keeping the human element front and center rather than letting the numbers drive every decision. ### 41. Limited Usefulness Due to Incomplete Data **Rating:** 2.0/5.0 stars **Reviewed by:** Stefan K. | Mid-Market (51-1000 emp.) **Reviewed Date:** April 16, 2026 **What do you like best about DX?** I like that I get a weekly message on Slack which includes some of the things my team does. **What do you dislike about DX?** DX is not including vital information that would make it actually useful for me. It only looks at PRs, which is not the whole picture. Some of my team members might go an entire week without submitting a PR and then are just omitted from the report completely. That's not useful to me. **What problems is DX solving and how is that benefiting you?** I get a weekly Slack message with some team activities, but vital information is missing. DX only looks at PRs, ignoring other aspects of my team's work, which isn't helpful for comprehensive monitoring. **Official Response from Taylor Bruneaux:** > Hi Stefan—thank you so much for taking the time to share this feedback. First and foremost, we completely agree with you: PR throughput is not the whole picture. If a tool only measures code commits, it misses the deep architectural work and the strategic thinking that happens between those pull requests. It’s understandable why a report that omits team members during their "deep work" weeks wouldn't feel useful to you as a manager. The full DX platform is built specifically to move beyond raw PR counts through things like: -- TrueThroughput: Our AI-powered engine that looks at the actual complexity and value of work, rather than just the number of PRs or commits. --The DX Core 4: Our framework that balances DORA and SPACE metrics with qualitative Developer Experience data to ensure "quiet" weeks of high-impact work are still recognized. --Comprehensive dashboards: Include sprint predictability, R&D allocation, and bottleneck analysis that spans the entire lifecycle. I’ve shared your feedback directly with your customer team. They will be reaching out to ensure you have full visibility into these broader capabilities and to help customize your reporting so it reflects the true output of your team. ### 42. Engineering Intelligence, backed by an excellent Support Team **Rating:** 5.0/5.0 stars **Reviewed by:** Michael M. | Backend Developer, Mid-Market (51-1000 emp.) **Reviewed Date:** January 14, 2026 **What do you like best about DX?** 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. **What do you dislike about DX?** 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. **What problems is DX 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. **Official Response from Taylor Bruneaux:** > Thanks Michael! It is great to hear that the partnership with our team and the high survey engagement have been so valuable for your organization. We appreciate the honest feedback about integration flexibility and the need for more consistent industry benchmarks; we're focused on making those insights easier to interpret so you can feel even more confident in your decision-making. ### 43. DX Delivers Powerful Insights and Excellent Support, with Room for Improved Data Navigation **Rating:** 5.0/5.0 stars **Reviewed by:** Scott S. | VP, Platform Engineering, Mid-Market (51-1000 emp.) **Reviewed Date:** October 14, 2025 **What do you like best about DX?** DX is an amazing product; it provides deep insights into the productivity and performance of our engineering teams right out of the box. And has also served as a platform to help drive several efficiency initiatives. It's easy to use and was very simple to get up and running. The customer support has been phenomenal, both the account and engineering teams have been very engaged with us throughout. We often use DX metrics reviews in our management meetings and within teams as well. **What do you dislike about DX?** While SQL support is available; I would love to see even more native tooling to help with navigating data easier. Would like the ability to unlock even more value by enabling quick/easy access regardless of skill. **What problems is DX solving and how is that benefiting you?** We monitor typical DORA and other Platform Engineering related metrics; we have also driven good DX usage within our teams so that Managers leverage it in their weekly standups with their teams to review team health metrics as well as reviewing quarterly developer experience surveys. ### 44. Excellent support and actionable engineering insights **Rating:** 5.0/5.0 stars **Reviewed by:** Eva C. | Progam Manager, Mid-Market (51-1000 emp.) **Reviewed Date:** October 08, 2025 **What do you like best about DX?** What I like most about DX is how quickly we were able to get value from it - it was up and running within weeks and gave us immediate visibility across our engineering teams. During our POC, we saw a 100% survey response rate, the highest we’ve ever seen. I also appreciate how it blends DORA metrics with real-time feedback to provide a complete view of developer experience. The built-in industry benchmarks help us understand where we stand relative to peers, and the proactive alerts with recommendations are a valuable bonus. We also had an excellent experience with the DX team - our customer success manager, account manager, and program manager were all incredibly responsive and helpful throughout the setup. **What do you dislike about DX?** While DX offers custom reporting, there’s a bit of a learning curve to fully tailor it to different stakeholder needs. As we’re still early in our adoption, we’re also building up historical data, so long-term trends will take time to develop. **What problems is DX solving and how is that benefiting you?** Before DX, I spent too much time piecing together metrics and survey feedback manually. Now, I get a unified, high-level view with actionable insights - saving time and making it easier to support our teams effectively. ### 45. Unique Productivity Insights with a Clean, Intuitive UX **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Hospital & Health Care | Enterprise (> 1000 emp.) **Reviewed Date:** May 12, 2026 **What do you like best about DX?** Provides visibility into engineering productivity that's otherwise hard to measure. The mix of the qualitative and quantative measurement seems unique. It's a clean UX/UI **What do you dislike about DX?** Integration with other tools takes forever. Also the pricing is pretty expensive for where we are in our journey as a company. **What problems is DX solving and how is that benefiting you?** DX is helping us measure developer experience: productivity and job-specific sentiment. The benefit is being able to identify friction points (slow builds, unclear priorities, meeting load) and prioritize investments that actually improve how engineers work **Official Response from Taylor Bruneaux:** > The friction point identification use case you described is exactly what we built this for. Slow builds, unclear priorities, meeting load — these are the things developers feel every day but that rarely show up in traditional engineering metrics. Combining qualitative and quantitative signal is what makes them visible. Appreciate the honest feedback on integrations and pricing. Both noted. I recommend reaching out to your account team to review both of these items. ### 46. Transformative insights and tooling for modern engineering teams **Rating:** 4.5/5.0 stars **Reviewed by:** Daniel F. | Senior Director of Engineering, Mid-Market (51-1000 emp.) **Reviewed Date:** October 07, 2025 **What do you like best about DX?** DX has been incredibly easy to use and integrate into our existing workflows. Their support team is consistently responsive and proactive, and the pace at which they ship meaningful improvements is impressive. Beyond the product itself, what really sets DX apart is their thought leadership in developer experience and productivity. The content, research, and frameworks they share have been hugely valuable in shaping how we approach developer experience at Paddle, and in my own understanding of what good looks like in this space. **What do you dislike about DX?** There’s not much to dislike. The only limitation we’ve hit is that the Linear integration isn’t yet as full-featured as the JIRA one, but I know it’s something they’re actively improving. **What problems is DX solving and how is that benefiting you?** DX gives us clear visibility into how efficiently our engineering department is operating — where work is flowing smoothly, and where bottlenecks or friction points exist. It helps us move beyond anecdotal feedback and gut feel by providing data-driven insights into developer productivity and experience. It’s also made it far easier to communicate how engineering is performing to our executive team, using concrete metrics rather than just vibes. ### 47. Rich developer feedback at scale **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Human Resources | Enterprise (> 1000 emp.) **Reviewed Date:** December 19, 2025 **What do you like best about DX?** DX provides a single, trusted view of developer experience by combining rich, quarterly survey feedback with signals from our delivery tools. We don’t just see what’s happening, we understand why. With team-level visibility and benchmarks, the platform enables easy triage of issues, prioritization of investments, and tracking of progress without resorting to individual surveillance. The wealth of survey data (structured drivers plus free-text insights) consistently reveals the real friction in our day-to-day (think CI reliability, code review flow, and time for deep work) and converts that into an actionable roadmap. **What do you dislike about DX?** One of the challenges we've had is integrating our systems-level data into the platform. This is largely due to our years of bespoke internal implementations and the challenge of retrofitting them into something that DX can use. However, it does mean that we have yet to start using the entirety of the platform to its full potential. **What problems is DX solving and how is that benefiting you?** DX provides us with a unified, trusted view by combining system telemetry (cycle time, deployments, code review flow) with quarterly survey signals, allowing us to see both what’s happening and why it’s happening. By giving us team-level insights with industry benchmarks, our managers and ICs are now triaging friction in their teams, prioritizing investments, and tracking progress responsibly. This has allowed us to focus at a company level on higher-order concerns that are impacting multiple teams, and giving us the visibility into these problems that we've historically not been able to see across a large organization. ### 48. Great Infographics and Multiple Services in One Platform **Rating:** 4.0/5.0 stars **Reviewed by:** Alexandros A. | Head of Technology, Casino, Enterprise (> 1000 emp.) **Reviewed Date:** May 14, 2026 **What do you like best about DX?** infographics and merge of different services in 1 platform **What do you dislike about DX?** support and AI are the 2 areas you can improve **What problems is DX solving and how is that benefiting you?** performance monioring, and multiple integrations in 1 platform. it helps with efficiency and quick healthcheck view of the teams. **Official Response from Taylor Bruneaux:** > Appreciate you sharing this, Alexandros. Having performance monitoring and integrations consolidated in one place is core to what we're going for, so glad that's landing for your team. Noted on support and AI. Both are areas we care about getting right. I'll have our team reach out to your champion to learn more about your thoughts here. ### 49. Unified Insights and Outstanding Support Elevate Developer Experience **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Mid-Market (51-1000 emp.) **Reviewed Date:** December 09, 2025 **What do you like best about DX?** DX serves as our primary platform for gathering data about developer experience and productivity. DX has provided us with a single access point and a unified view for data from different platforms. The ease of filtering and slicing by teams and attributes has helped us better understand the performance of different teams. The snapshot feature has enabled us to drive multiple efficiency initiatives and produce measurable impact on developer experience and velocity. Another key feature is the ability to compare our metrics to similar organizations, which has helped us better understand areas that require improvement and simplified our reporting. These initiatives have been supported by the continuous assistance from the excellent DX Team throughout implementation and beyond. The team is always ready to answer our questions and has helped us align multiple reports to fit our needs. **What do you dislike about DX?** The default defect ratio reporting uses a different methodology than our internal innovation and defect tracking processes. While the current approach works for us, we're looking forward to an upcoming feature that will allow us to customize reporting to better align with our specific tracking methods. **What problems is DX solving and how is that benefiting you?** DX solved our developer experience measurement and tracking problem. It allows us to make informed decisions and drive efficiency projects based on data. We can clearly track which initiatives are working and which aren't, enabling us to iterate quickly. This capability has been particularly critical for measuring the impact of our various GenAI for Engineering initiatives. DX integrated seamlessly with our toolchain and provided the metrics we needed to accurately capture ROI on these investments. Another key benefit has been gathering accurate feedback from engineering teams specifically about the development process. In the past, company-wide surveys were a constant struggle to capture this information effectively. The targeted comments from engineering teams have already helped us reshape various internal processes and prioritize improvements that matter most to developers. ### 50. Effortless Survey Creation, Minor Slack Integration Hiccups **Rating:** 3.5/5.0 stars **Reviewed by:** Eric Q. | Enterprise (> 1000 emp.) **Reviewed Date:** April 14, 2026 **What do you like best about DX?** I like that I can see and create surveys very easily with DX. It's very quick to add additional questions, and it's easy for me to add survey respondents I want to send the survey out to, which saves me time. **What do you dislike about DX?** Instead of using my own Slack account to send out surveys, I'd rather have a bot that sends out the surveys because it takes over my entire Slack DM box. **What problems is DX solving and how is that benefiting you?** DX allows me to capture survey responses easily, helping us understand customer pain points and successes effectively. **Official Response from Taylor Bruneaux:** > Hi Eric—we really appreciate the feedback! It’s great to hear that creating and targeting surveys has been such a time-saver for you. We also hear you on the Slack DM experience—we actually have a few different ways to configure how surveys are sent, so I’ve surfaced this to your account and program management teams. They’ll be reaching out to help you find the best setup for your workflow. Thanks for helping us improve! - [View DX pricing details and edition comparison](https://www.g2.com/products/dx-platform/reviews?section=pricing&secure%5Bexpires_at%5D=2026-06-01+00%3A41%3A40+-0500&secure%5Bsession_id%5D=5dd8073e-c08c-4023-b3d8-d2e22e31baf2&secure%5Btoken%5D=00f25c21f84d8a62b1ca22aad146c8ac2de33ce5661f6d68a73aa1459140f7ce&format=llm_user) ## DX Integrations - [Amazon Q](https://www.g2.com/products/amazon-web-services-aws-amazon-q/reviews) - [Amazon Web Services AI](https://www.g2.com/products/amazon-web-services-ai/reviews) - [Amp](https://www.g2.com/products/amp-code-amp/reviews) - [Argo CD](https://www.g2.com/products/argo-cd/reviews) - [Asana](https://www.g2.com/products/asana/reviews) - [Azure](https://www.g2.com/products/hopem-azure/reviews) - [Azure DevOps Server](https://www.g2.com/products/azure-devops-server/reviews) - [Azure Pipelines](https://www.g2.com/products/azure-pipelines/reviews) - [Azure Portal](https://www.g2.com/products/azure-portal/reviews) - [Backstage](https://www.g2.com/products/backstage/reviews) - [Bitbucket](https://www.g2.com/products/bitbucket/reviews) - [BugSnag](https://www.g2.com/products/bugsnag/reviews) - [Buildkite](https://www.g2.com/products/buildkite/reviews) - [Buildkite](https://www.g2.com/products/buildkite-buildkite/reviews) - [Checkmarx](https://www.g2.com/products/checkmarx/reviews) - [Checkmarx Codebashing](https://www.g2.com/products/checkmarx-codebashing/reviews) - [CircleCI](https://www.g2.com/products/circleci/reviews) - [Claude](https://www.g2.com/products/claude-2025-12-11/reviews) - [Claude Code](https://www.g2.com/products/anthropic-claude-code/reviews) - [Claude Code](https://www.g2.com/products/claude-code/reviews) - [Claude for Slack](https://www.g2.com/products/claude-for-slack/reviews) - [ClickUp](https://www.g2.com/products/clickup/reviews) - [Codecov](https://www.g2.com/products/codecov/reviews) - [Confluence](https://www.g2.com/products/confluence/reviews) - [Confluence](https://www.g2.com/products/statpro-confluence/reviews) - [Copilot](https://www.g2.com/products/copilot-software-ltd-copilot/reviews) - [Coralogix](https://www.g2.com/products/coralogix/reviews) - [Cursor](https://www.g2.com/products/cursor/reviews) - [Datadog](https://www.g2.com/products/datadog/reviews) - [Dora Studio: Turn Your Ideas into Stunning Motion Graphics](https://www.g2.com/products/dora-studio-turn-your-ideas-into-stunning-motion-graphics/reviews) - [Dynatrace](https://www.g2.com/products/dynatrace/reviews) - [Firebender](https://www.g2.com/products/firebender/reviews) - [FireHydrant](https://www.g2.com/products/firehydrant-firehydrant/reviews) - [Gerrit](https://www.g2.com/products/gerrit/reviews) - [Git](https://www.g2.com/products/git/reviews) - [GitHub](https://www.g2.com/products/github/reviews) - [GitHub Copilot](https://www.g2.com/products/github-copilot/reviews) - [GitLab](https://www.g2.com/products/gitlab/reviews) - [Google Calendar for Confluence](https://www.g2.com/products/google-calendar-for-confluence/reviews) - [Google Cloud APIs](https://www.g2.com/products/google-cloud-apis/reviews) - [Google Workspace](https://www.g2.com/products/google-workspace/reviews) - [Harness Platform](https://www.g2.com/products/harness-platform/reviews) - [incident.io](https://www.g2.com/products/incident-io/reviews) - [Jenkins](https://www.g2.com/products/jenkins/reviews) - [Jira](https://www.g2.com/products/jira/reviews) - [Jira Service Management](https://www.g2.com/products/jira-service-management/reviews) - [Kubernetes](https://www.g2.com/products/kubernetes/reviews) - [Kubernetes](https://www.g2.com/products/american-cloud-kubernetes/reviews) - [LaunchDarkly](https://www.g2.com/products/launchdarkly/reviews) - [Linear](https://www.g2.com/products/linear/reviews) - [Microsoft Entra ID](https://www.g2.com/products/microsoft-entra-id/reviews) - [Microsoft Outlook](https://www.g2.com/products/microsoft-outlook/reviews) - [Microsoft Teams](https://www.g2.com/products/microsoft-teams/reviews) - [New Relic](https://www.g2.com/products/new-relic/reviews) - [Opsgenie](https://www.g2.com/products/opsgenie/reviews) - [PagerDuty](https://www.g2.com/products/pagerduty/reviews) - [Rollbar](https://www.g2.com/products/rollbar/reviews) - [Rootly](https://www.g2.com/products/rootly/reviews) - [Sentry](https://www.g2.com/products/sentry/reviews) - [ServiceNow Cloud Management](https://www.g2.com/products/servicenow-cloud-management/reviews) - [ServiceNow IT Asset Management](https://www.g2.com/products/servicenow-it-asset-management/reviews) - [ServiceNow IT Service Management](https://www.g2.com/products/servicenow-it-service-management/reviews) - [Shortcut](https://www.g2.com/products/shortcut/reviews) - [Slack](https://www.g2.com/products/slack/reviews) - [Slack Connector for Jira](https://www.g2.com/products/slack-connector-for-jira/reviews) - [Snyk](https://www.g2.com/products/snyk/reviews) - [SonarQube](https://www.g2.com/products/sonarqube-2026-02-03/reviews) - [SonarQube](https://www.g2.com/products/sonarqube/reviews) - [SonarQube](https://www.g2.com/products/kurian-sonarqube/reviews) - [Sumo Logic](https://www.g2.com/products/sumo-logic/reviews) - [Vercel](https://www.g2.com/products/vercel/reviews) - [Windsurf](https://www.g2.com/products/exafunction-windsurf/reviews) - [Wiz](https://www.g2.com/products/wiz-chat-wiz/reviews) ## DX Features **Functionality** - Repository Integration - Analytics and Trends - Productivity Updates **Management** - Historical Data Consolidation - Data Context - Testing Integration **Value Analysis** - Metric Relevance - Insight - Impact Predictions - Report Generation **Value Management** - Planning Tools - Communication Tools - Control ## Top DX Alternatives - [Jellyfish](https://www.g2.com/products/jellyfish-2025-10-22/reviews) - 4.5/5.0 (427 reviews) - [Swarmia](https://www.g2.com/products/swarmia/reviews) - 4.4/5.0 (294 reviews) - [LinearB](https://www.g2.com/products/linearb/reviews) - 4.6/5.0 (79 reviews)