Jellyfish links developer sentiment to performance

The free survey is a wedge that helps Jellyfish move from measuring output to explaining why output changes. The product already pulls commits, pull requests, issue changes, calendar events, and payroll data into one model of engineering work. Adding a lightweight sentiment layer lets a manager see whether slower delivery comes from low morale, weak documentation, painful code review, or tool friction, instead of just seeing a red metric on a dashboard.

• Jellyfish uses the survey to ask engineers about concrete pain points like test automation, documentation, context switching, code review, tools, and release process, then tracks those answers over time. The company has positioned DevEx as a way to pair subjective feedback with the same operational data already flowing through its core product.
  2 jellyfish 3 jellyfish 4 jellyfish
• This matters competitively because developer experience surveys are becoming part of the engineering intelligence stack, not a separate HR exercise. Atlassian moved directly into this lane with its September 18, 2025 acquisition of DX, combining survey feedback with delivery and workflow data inside Jira, Bitbucket, and Compass.
  1 sacra 5 atlassian
• Compared with LinearB, which leans toward workflow automation and coaching bots, and Swarmia, which centers on dashboards, alerts, and working agreements, Jellyfish is using DevEx to strengthen its pitch to engineering leaders who want a fuller read on team health, delivery performance, and budget allocation in one system.
  1 sacra 6 sacra 7 sacra

The category is heading toward a single operating layer for engineering, where cost, speed, AI usage, and developer sentiment are analyzed together. As larger platforms bundle these capabilities, free survey tools will keep working as low friction entry points, but the real value will come from tying team feelings to planning, finance, and delivery decisions across the whole engineering org.