by: Christopher, IT Engineer
There’s never been a better time to work in tech. I’ve worked as an engineer at Progressive for more than 20 years, and I don’t know that I’ve ever been this excited about the work we’re doing. Technology is changing faster than ever, and being with a company that’s keeping up with it is really energizing.
Let me tell you what I mean…
Throughout the past several years, we’ve used Cloud and emerging technologies in lots of new ways to move our business forward. As an engineer, I’ve been lucky enough to be heavily involved, collaborating with application developers and business leaders along the way. Not long ago, I was part of implementing a cutting-edge tech solution for a new customer product.
Our usage-based insurance group (UBI)—the people who bring you Snapshot®—approached us with an opportunity. We’ve long used a physical Snapshot device that customers plug into their cars to track certain vehicle stats. From those, we can get a better picture of a customer’s driving behaviors and charge them a more customized insurance rate. That “plug in” device carried a significant cost to Progressive. The UBI team wanted to explore using a cell phone to transmit our customers’ vehicle stats, and reduce the cost of providing our Snapshot service.
Rather than defaulting to our tried and true problem solution processes, my team and I saw this as an opportunity to look at innovative ways to deliver on the business requirements. Lucky for us, our business leaders encourage us to test new technologies. (Pretty cool, since many of us in the IT field know all too well that having access to new technologies is one thing…actually being empowered to test and use them to solve business problems is another.) In my experience, being able to evaluate new tech not only ensures the best solution is delivered, but it keeps the entire team fresh and engaged.
We weighed the pros and cons of a typical server-based solution against those of a serverless architecture solution. In the end, it was clear a serverless solution would be more flexible, extensible and performant, without the overhead of server management.
At the time, serverless solutions in the public cloud were new for everyone here. But again, we’re not ones to shy away from testing and learning, and we felt confident we could use the technology to quickly deliver on a business requirement. It was the first time we’d leveraged the public cloud for a production solution. On top of that, we decided to deploy it all through Infrastructure as Code (IaC).
IaC has radically changed how we, as engineers, go about delivering and updating infrastructure components. It allows us to automate deployments through code with known supporting source control and deployment systems. It really moves engineers to think and function more like an application developer in that we use most of the same processes and tools that they use to deliver solutions. This starts us down the path of working together more with developers and increases collaboration, as we now speak the same technical language. And, I’d predict that the efficiencies we’ll gain by that improvement alone will be immeasurable.
Unless you work at Progressive or know someone who does, it might surprise you to learn that innovation is part of our DNA. When it comes to technology, we’re not a “that’s how we’ve always done it” type of company. Working here is challenging, but in the best possible way. We love questioning the norm and looking at leading edge solutions to deliver the optimal technical solution, even if it’s outside our comfort zone—that just makes it more exciting.
Develop software and implement quality assurance strategies to help ensure our rates are accurate and our customers have great experiences with our applications. Want to come work with Domonic?
Narrator:
So, we kind of have this unofficial slogan for the systems test engineer, "We write code to break code" We write this software, this automation because to manually go out to our quoting applications, it would take forever. We need a wide net of test combinations and automation to figure out what's going on with our systems. So, I think the main objective of my role as the systems test engineer is making sure that our rates are accurate, and you know, we have a good customer experience with our applications. If a customer's maybe buying a new vehicle and they're quoting and then all of a sudden you enter in a value and then the application crashes. We are really trying to prevent those types of bugs because those are the ones that really impact the customers.
Narrator:
You know, my day to day varies day to-- I mean, it literally varies day to day. I can, in one day, be a software developer developing automation. And then on another day, I can be a quality assurance analyst as a bug hunter. So, I really think the versatility of the role is what makes it unique. We have to speak the developer lingo because we're talking with the developers, but at the same point in time, we also are writing automation for our quality assurance analysts to run. And so, we kind of have to have softer skills as well that's not all the technical jargon that we might be speaking with the developers.
Narrator:
One of the things that really surprised me about Progressive is how open they are to new ideas. I'm able to come up with an idea and then Progressive helps me implement it. The culture is very laid back. You know, even though we're a bigger company, it definitely doesn't feel like we are. They're great about letting me build up my skills. And I took a bunch of courses that Progressive offered to the IT University learning web APIs and all sorts of other awesome technologies.
Narrator:
There's no real end to our quest. You know, as technology changes, as Progressive changes, our automation is always changing. We're always doing something new and exciting. I love designing software, developing software, and I equally love hunting for bugs and I think the system test engineer is the perfect mix for me.
Christopher Kalan has over 20 years of experience in the IT field. At Progressive, he’s an engineer responsible for designing and implementing solutions that address a broad range of both business and technical requirements, including software, hardware, and policy components.