G2

Verified User in Leisure, Travel & Tourism

Mid-Market (51-1000 emp.)

9/18/2026

"Clear Insights into Code Reviews and Developer Experience"

4/5

What do you like best about Swarmia?

What I like best about Swarmia is the visibility it provides into our GitHub pull requests and code review workflow. Its reports make it easier to understand how work moves through development, review, and merging, and to identify where delays may be occurring. Having metrics such as pull request cycle time, time in review, and time to merge gives useful context for understanding the process and spotting opportunities to improve. The ability to explore individual pull requests alongside broader trends makes these insights particularly useful. It helps connect the overall metrics with specific examples, making it easier to investigate bottlenecks and understand why certain changes take longer to move forward. For me, the main value is having a clearer, evidence-based view of our review workflow that can support more focused discussions about improvements. Review collected by and hosted on G2.com.

What do you dislike about Swarmia?

The main area I would like to see improved is the Slack notification experience. Notifications can sometimes feel noisy and repetitive, which reduces their usefulness and can make it harder to distinguish important updates from routine reminders. Swarmia already offers settings to customize notification types, but I would appreciate a more streamlined experience with less repetition and clearer prioritization of items that need attention. Better consolidation of related updates and fewer reminders when there is no meaningful change would make the integration feel more focused. For me, the opportunity is to keep the visibility into ongoing work while reducing the amount of notification noise in Slack. Review collected by and hosted on G2.com.

What problems is Swarmia solving and how is that benefiting you?

Swarmia helps us understand where our engineering workflow can improve. Its reporting on GitHub pull requests and code reviews gives us visibility into how work progresses and where delays occur. Metrics such as pull request cycle time and time in review make it easier to identify potential bottlenecks and give us a concrete starting point for discussing improvements. The developer experience surveys have also been particularly valuable for our engineering teams. They helped surface issues that engineers already recognized in their day-to-day work but had not explicitly raised. Providing a structured way to share feedback helped turn those individual observations into visible areas for improvement. This gives us a clearer understanding of the challenges engineers face and a stronger basis for deciding what needs attention. For me, the main benefit is combining workflow data with feedback from the people doing the work. The pull request insights help highlight where friction may exist, while the surveys provide context that metrics alone cannot capture. Together, they help us identify improvement opportunities with a more complete understanding of both our processes and our engineers’ experiences. Review collected by and hosted on G2.com.