My journey into Mainframe wasn’t something I planned — it’s something I discovered.
I studied Computer Science at the University of North Florida. Like many students, my early work experience wasn’t in tech at all — my first part-time job was serving ice cream, and I also worked in food and retail throughout high school. At the time, I was just focused on gaining experience and figuring out my path, and Mainframe wasn’t on my radar.
Everything changed during the fall semester of my senior year when I took a COBOL for FinTech course. That was my first real exposure to the Mainframe. To be honest, I didn’t know anything about it — I didn’t even know what COBOL was at the time. But what immediately intrigued me was the misconception surrounding Mainframe technology. So many people think it’s outdated or going away, yet the reality is the opposite — it’s still critical, still evolving, and still growing.
My first steps into Mainframe were very hands-on. I worked with the 3270 interface and completed IBM Z Xplore badges to build my foundational knowledge. Early on, I faced a lot of challenges — especially just understanding how COBOL worked and navigating the environment. I spent a lot of time going back and forth between documentation, trial and error, and trying to make sense of errors.
One moment that really stands out was during a COBOL project using Zowe. I kept running a job over and over again, only to be met with ABEND errors each time. It was frustrating, but also a turning point. When I finally figured out what was going wrong and got it to run successfully, something clicked. That experience taught me persistence and helped build my confidence.
A huge part of my growth came from the people around me. My professor, Scott Piersall — who is also an IBM Champion — played a significant role in guiding me. He helped me work through challenges and better understand the concepts. My classmates were also an important support system. We collaborated, shared ideas, and helped each other troubleshoot when things didn’t work. That sense of community made a big difference in my learning experience.
Today, I work as an Associate Systems Engineer at Software AG. Since I’m early in my career, I’m gaining exposure to a variety of technologies and products related to the Mainframe, including COBOL, JCL, and 3270. What excites me most is how much there still is to learn. Every day, I discover something new about the Mainframe ecosystem, and it keeps me motivated and curious.
Looking back, one thing I wish I had done differently is starting earlier. I wish I had been exposed to Mainframe technology earlier in my college career, because there is so much opportunity in this space.
For anyone considering Mainframe, my advice is simple: learn as much as you can and get involved. Take advantage of training programs, pursue internships, and attend Mainframe conferences if you can. The community is incredibly welcoming, and there is so much knowledge to gain from the people in it. Whether you’re just starting out or making a career shift, there’s a place for you here.
It doesn’t matter if you’re one year into your career or thirty — your journey has value. And sometimes, the best paths are the ones you never planned to take.