CloudTalk: Bend the Ear of an Engineer

Nick Bitzer cut his teeth as a ReadyTalk engineer three years ago when he began on the Q/A and release team. Now, he’s responsible for maintaining backend reliability that makes our ReadyTalk products possible. He’s armed with an acute sense of our tech DNA, and a sleeve tattoo of a steamship anchor repping his Florida roots.

Q: What was your most memorable day at ReadyTalk?

A: The first day I got here. Haha seriously. It was a great introduction to the company culture and my whole team. Definitely a whirlwind of events that day. My first impression was how inviting and welcoming everyone was. Also, sometimes the formalities of meeting managers can seem awkward and forced on your first day. It was NOT that way at ReadyTalk. My questions were heard and answered, I was able to meet even the highest level directors and C-level executives. The access to people and resources was really an eye opener. I definitely felt the culture was dropped in my lap on day one. Plus, we crushed it at happy hour that evening, so that didn’t hurt either. It did hurt the next day.   

Q: What’s your most unpredictable type of work day?

A: The catch 22 is that the bad or difficult days are the most rewarding. Once in awhile, unforeseen production issues may cause a hiccup and I have to get up early to put out a fire. It just happens, as with any other service on the market. Even though these events are high pressure, I do enjoy solving the problem and identifying why something went wrong. I think that’s when I’m at my best because my teammates and I need a resolution ASAP.

Q: Even though you work on the backend in engineering, how does your work affect customers?

A: Since I’ve worked on a lot of our bug fixes and product enhancements, I enjoy acting on the concerns of our customers and delivering additions to our services. In this case, the engineering team works with the customer care department to remedy different components, or to stay competitive in the market by adding product features. This was especially true when I worked on the release team because we were building automation that verified our products. We pushed out the changes every six weeks so that definitely kept us busy. This relates to ongoing projects that reflect the voice of the customer, so it might not always impact my day-to-day flow. Rather, the bigger picture across the company as we get feedback about maximizing the user experience.

Q: I noticed that you have an exposed tattoo. Does that make it hard getting a table at a nice restaurant?

A: No. Absolutely not. It helps.

Share this:

Blog posts by author

Justin McHeffey

Justin McHeffey

Justin is the product marketing manager for ReadyTalk’s Webinar and Webcast lines of business. He loves enabling marketing professionals with strategies to raise brand awareness and generate leads through cloud-based presentations. When he’s not talking vertical use cases, you’ll find him fly fishing, camping, skiing, or getting pulled into a wikihole about planets and stars.

Similar Articles:
CloudTalk: Shred the WebiGnar Carving through the epic trees at Vail you’ll find Connor McKeown — a self-proclaimed weekend warrior with a yen for the Colorado outdoors. On any given powder day, skiing is his full-time job. However, between snowstorms we have him and his team to thank for their steadfast engineering and infrastr...
Legacy Systems and How to Move... Just about every company has them: legacy systems. They may be part of the architecture -- the very infrastructure, at the heart of your company's IT road map, too. But what if these platforms are actually hurting your company's performance? What is a legacy system? Legacy systems are old, u...