Statements from the following verified business professionals were used to create this chart:
Title |
Company Size |
Industry |
Response |
|
Software Engineer |
Global 500 |
Professional Services |
- Inability to easily troubleshoot and determine the root cause of build, test and CI failures including flaky tests
- Difficulty communicating build details between teams and collaborating when troubleshooting failures
|
|
Build/Release Engineer |
Medium Enterprise |
Computer Software |
- Insufficient observability of analytics on build and test performance and regressions, failure trends, and productivity bottlenecks
- Cost impacts from an inefficient build and test process and tooling infrastructure
|
|
Software Engineer |
Medium Enterprise |
Computer Software |
- Too much time spent waiting on build and test feedback either locally or during CI
- Inability to easily troubleshoot and determine the root cause of build, test and CI failures including flaky tests
- Difficulty communicating build details between teams and collaborating when troubleshooting failures
- Cost impacts from an inefficient build and test process and tooling infrastructure
|
|
Build/Release Engineer |
Small Business |
Computer Services |
- Too much time spent waiting on build and test feedback either locally or during CI
- Inability to easily troubleshoot and determine the root cause of build, test and CI failures including flaky tests
- Insufficient observability of analytics on build and test performance and regressions, failure trends, and productivity bottlenecks
- Difficulty communicating build details between teams and collaborating when troubleshooting failures
- Time-to-market impacts from an inefficient build and test process and tooling infrastructure
|
|
Mobile Platform Engineer |
Medium Enterprise |
Food |
- Too much time spent waiting on build and test feedback either locally or during CI
- Inability to easily troubleshoot and determine the root cause of build, test and CI failures including flaky tests
- Insufficient observability of analytics on build and test performance and regressions, failure trends, and productivity bottlenecks
- Managing the growth of build and test cycles as the codebase grows
|
|
Engineering Manager |
Large Enterprise |
Telecommunications Services |
- Too much time spent waiting on build and test feedback either locally or during CI
- Inability to easily troubleshoot and determine the root cause of build, test and CI failures including flaky tests
- Difficulty communicating build details between teams and collaborating when troubleshooting failures
- Managing the growth of build and test cycles as the codebase grows
|
|
Android Engineer |
Medium Enterprise |
Consumer Products |
- Too much time spent waiting on build and test feedback either locally or during CI
- Inability to easily troubleshoot and determine the root cause of build, test and CI failures including flaky tests
- Insufficient observability of analytics on build and test performance and regressions, failure trends, and productivity bottlenecks
- Cost impacts from an inefficient build and test process and tooling infrastructure
- Time-to-market impacts from an inefficient build and test process and tooling infrastructure
|
|
Software Engineer |
Medium Enterprise |
Computer Software |
- Too much time spent waiting on build and test feedback either locally or during CI
- Inability to easily troubleshoot and determine the root cause of build, test and CI failures including flaky tests
- Insufficient observability of analytics on build and test performance and regressions, failure trends, and productivity bottlenecks
- Difficulty communicating build details between teams and collaborating when troubleshooting failures
- Managing the growth of build and test cycles as the codebase grows
- Cost impacts from an inefficient build and test process and tooling infrastructure
- Time-to-market impacts from an inefficient build and test process and tooling infrastructure
|
|
Engineering Manager |
Large Enterprise |
Food |
- Insufficient observability of analytics on build and test performance and regressions, failure trends, and productivity bottlenecks
- Difficulty communicating build details between teams and collaborating when troubleshooting failures
|
|
Software Engineer |
Medium Enterprise |
Telecommunications Equipment |
- Too much time spent waiting on build and test feedback either locally or during CI
- Insufficient observability of analytics on build and test performance and regressions, failure trends, and productivity bottlenecks
- Difficulty communicating build details between teams and collaborating when troubleshooting failures
- Managing the growth of build and test cycles as the codebase grows
- Difficulty achieving success with DevOps initiatives due to existing friction in the development process
- Time-to-market impacts from an inefficient build and test process and tooling infrastructure
|