Suggestions
Arjun Iyer
CEO & Co-founder, Signadot
Arjun Iyer is the Co-founder and CEO of Signadot, a company dedicated to transforming the way engineering teams approach testing in cloud-native software development.
He is passionate about 'shifting left' in testing, advocating for bringing testing earlier into the development cycle for improved quality, efficiency, and developer satisfaction.
Arjun's mission with Signadot is to challenge the status quo by providing tools that seamlessly integrate into Kubernetes, enabling proactive and efficient testing methodologies.
His goal is to empower developers to detect and resolve issues sooner, shorten time to market, and cultivate a culture of innovation and excellence within engineering teams.
Arjun Iyer has a diverse educational background, including a Master of Science (M.S.) in Computer Science and Mechanical Engineering from the University of Illinois Urbana-Champaign, a B.Tech in Mechanical Engineering from the Indian Institute of Technology, Kharagpur, and studies in electronics at National College.
In his professional journey, Arjun has held key positions in various organizations, including being the former CEO & Co-Founder of Signadot, Senior Director in Data Science and BusinessIQ at AppDynamics, Senior Engineering Director at Rearden Commerce, Senior Engineer at Shutterfly and Xensource, and a lead engineer at Siebel Systems.
Arjun Iyer is dedicated to building communities where ideas and innovations thrive and invites others to connect with him to explore opportunities for transforming cloud-native software development and embracing the concept of 'shifting left' in testing.
You can book a meeting with Arjun through his calendly link or contact him via email at [email protected] to engage in shaping the future of software development.
Highlights
Ever felt like your shared staging environment is more of a traffic jam than a fast lane?
In the realm of microservices and cloud applications, when multiple developers rely on a single staging environment, things can get messy. Tests overlap, results become unreliable, and the release process slows down—all because everyone's working in the same space. It's like trying to have multiple meetings in one room at the same time.
How can we maintain the realism of testing without the congestion of a shared space? Would love to hear your thoughts.
#stagingenvironments #microservices #cloudnative #developerexperience #devops #platformengineering
After talking to hundreds of VPEs and CTOs, a clear pattern has emerged: dev/test environments are becoming black holes for time and budget.
Companies spend millions on shared DEV, QA, and STAGING environments. And while STAGING might resemble production, lower environments often don’t—and that’s where things start to unravel.
These shared environments lead to constant contention. One team’s testing disrupts another, different microservice versions clash, and it becomes nearly impossible to know what’s truly been tested. By the time issues surface in STAGING, it’s already too late—you’ve hit the bottleneck.
The kicker? Despite the high cost, these environments often fail to deliver the value they promise, and release velocity suffers as a result.
How are you tackling this challenge in your org? I’d love to hear how others are navigating these bottlenecks.
#CloudNative #DevOps #SoftwareTesting #Microservices #DeveloperProductivity #TestEnvironments
