DX Reviews & Product Details

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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 Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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.). Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.