09 DevOps Engineer
What is it Like Being a DevOps Engineer & Team Lead
On this episode of the Unboxing Careers Podcast, we unbox the career of a DevOps engineer and team lead.
Guest: Todd Cretacci is a Lead DevOps Engineer and team lead at KeyBank. With a high-level understanding of infrastructure services, he’s recognized for designing and delivering high performing systems while showing passion for performance and teamwork. In his day-to-day work, Todd helps the delivery of architect level solutions to complex problems in different corporate environments such as call centers, service providers and financial institutions.
Connect with Todd:
Connect with Todd on Linkedin
Listen: Spotify | Apple Podcasts | Amazon Music
What Does a DevOps Engineer Really Do? Inside the Career of a Lead DevOps Engineer
When people hear the term “DevOps engineer,” they often picture someone quietly coding in a dark room, surrounded by servers and energy drinks. The reality is much more dynamic, collaborative, and mentally demanding than that stereotype suggests.
As a Lead DevOps Engineer and Team Lead at KeyBank, Todd Cretacci works on the infrastructure that keeps major banking applications running. His role centers around supporting and building Kubernetes clusters in Google Cloud and in company data centers. In simple terms, that means designing and maintaining the systems that allow applications to run efficiently, securely, and at scale. Instead of focusing only on writing code, DevOps engineers often focus on the environment that code runs in.
If you are curious about technology but unsure whether DevOps is a fit, this post will walk through what the day-to-day experience actually feels like, what pressures come with the job, and who tends to thrive in this kind of role.
What Does a DevOps Engineer Actually Do Day to Day?
At a high level, DevOps engineers manage infrastructure. In this case, that means building, upgrading, migrating, and supporting Kubernetes clusters that host critical banking applications. When an application runs slowly or breaks, DevOps is often involved in diagnosing whether the issue is infrastructure-related.
On a weekly basis, the job is a mix of project work and problem-solving. Right now, that includes setting up entirely new infrastructure, which involves coordinating timelines, collaborating with project managers, and ensuring hardware, networking, and application layers all come together on schedule. In a large company environment, everything is time-boxed and scheduled. Deadlines are real.
A typical week includes:
Project meetings to track infrastructure build-outs
Troubleshooting sessions with internal teams
Reviewing timelines and milestones for migrations
Diagnosing application performance issues
Incremental improvements to systems
One surprising reality is how meeting-heavy the role can be. In busy project phases, meetings can take up 60 to 70 percent of the week. Even in calmer periods, it is often close to 50 percent. DevOps is not just technical isolation work. It is collaboration-heavy and communication-driven.
If you dislike meetings or struggle with cross-team coordination, this role may feel more draining than expected.
How Todd Found DevOps After Starting Somewhere Else
One of the most relatable parts of this career story is that it did not start in computer science.
In high school, Todd was focused on automotive technology. He studied engines, collision work, and mechanics. It was interesting, but there was never a deep internal drive toward it. That lack of long-term clarity eventually caused some panic midway through college when he realized he did not want to work in auto technology for life.
Technology became appealing as the internet expanded in the 1990s. By reading constantly, building skills independently, and starting in a call center job, he gradually moved into computer repair and server work. Over time, he developed a broad infrastructure background.
The move into DevOps itself happened later in his career. After years of server and infrastructure work, he felt stagnant. The work was fine, the people were great, but there was no longer a sense of challenge. When he heard about a cloud-focused DevOps team willing to train motivated employees, that internal spark returned. That feeling of butterflies was the signal that it was time to pivot.
The takeaway is not that you must know your career at 18. It is that paying attention to curiosity and challenge levels matters. Feeling stagnant long-term can be a sign that growth is needed.
What Work Life Balance Really Feels Like in DevOps
Remote work is common in this field. Todd has worked remotely for over a decade, and his current role is fully remote. From the outside, remote work can look easy. In reality, it requires discipline. Without a commute, there is no natural decompression period between work and home life. The laptop is always nearby. There is always one more ticket to finish, one more issue to resolve.
The emotional tradeoff is subtle but important. The flexibility is incredible. Doctor appointments, errands, and family needs are easier to manage. But without clear boundaries, work can bleed into evenings. The biggest lesson here is the importance of intentionally shutting off. Closing the laptop at a defined time matters. Without that separation, stress can build quietly.
DevOps can also be stressful during infrastructure migrations or large-scale projects. Deadlines are firm. Systems are critical. The work supports real customers. If you thrive under pressure and enjoy solving complex problems, that stress can feel energizing. If you need predictability and low urgency, it may feel draining.
The Personality Traits That Fit DevOps Engineering
DevOps requires more empathy than many people expect.
When internal teams report problems, it is not enough to say, “That is not my issue.” Applications run across multiple layers, including network, security, infrastructure, and code. Being able to think holistically about how all those pieces interact is essential.
Successful DevOps engineers often demonstrate:
Systems-level thinking
Patience when troubleshooting
Comfort asking questions
Adaptability during constant change
Professionalism during company-driven decisions
A major misconception is that asking questions signals weakness. In reality, it is critical for growth. DevOps environments change constantly. New tools replace old ones. Infrastructure evolves. Nobody knows everything.
The key is asking thoughtful questions, not lazy ones. Do research first, then collaborate.
Another major trait is separating personal emotion from professional change. Software gets replaced. Security rules tighten. Processes shift. Reacting negatively can create stress and damage a professional reputation. Rolling with the punches is part of long-term sustainability in this field.
What High School and College Students Should Focus On
DevOps is broad. It includes coding, infrastructure, cloud architecture, automation pipelines, and more. Rather than obsessing over one specific programming language, it may be more helpful to identify what role within technology feels exciting.
Companies often hire for mindset and train for tools. A background in infrastructure, some coding exposure, and curiosity go a long way. In high school, it helps to:
Make a list of interests and revisit it
Talk to working professionals
Explore different tech roles before committing
Think intentionally about post-graduation options
In college, extracurricular involvement matters more than many students realize. Clubs, collaborative projects, and networking opportunities build perspective and relationships that textbooks cannot provide.
When interviewing, genuine interest stands out. Researching the company, asking thoughtful questions, and showing enthusiasm often separates candidates more than perfect technical knowledge.
The Stress and Excitement of Constant Change
DevOps is never stagnant.
Continuous improvement and continuous delivery mean systems are always evolving. Tools change. Processes improve. Teams shift approaches. That can be overwhelming at first. Entering DevOps can feel like drinking from a fire hose.
The key is focusing on your assigned piece first. Master your current responsibilities before trying to absorb everything at once. Growth becomes manageable when taken step by step. The constant change can feel stressful. It can also be energizing. For people who love learning and adapting, it keeps the job fresh.
Closing
Technology careers are rarely linear. This one certainly was not. What stands out most is the willingness to pivot, keep learning, and stay curious even after decades in the field. DevOps is demanding, but for the right personality, it offers challenge, growth, and the satisfaction of keeping critical systems running smoothly behind the scenes.
If you enjoy solving puzzles, thinking in systems, and working collaboratively under pressure, this could be a path worth exploring.
Career Snapshot: Is DevOps Engineering Right for You?
You may thrive if you:
Enjoy solving complex, layered problems
Like learning new tools constantly
Can stay calm under deadline pressure
Communicate well across teams
Are comfortable with continuous change
You may struggle if you:
Prefer predictable, repetitive tasks
Dislike meetings and collaboration
Take organizational changes personally
Avoid asking questions
Need clear separation without setting boundaries
Core tradeoffs and emotional realities:
Flexibility of remote work versus difficulty unplugging
Constant learning versus constant change stress
High-impact infrastructure work versus heavy meeting time
Collaboration demands versus independent focus time
DevOps Engineer Career FAQs
What does a DevOps engineer do in simple terms?
A DevOps engineer manages the infrastructure that allows applications to run efficiently and securely. Instead of focusing only on writing code, they build, upgrade, and support systems like Kubernetes clusters that host applications. They troubleshoot performance issues, collaborate with other teams, and ensure systems scale properly.
Do you need a computer science degree to become a DevOps engineer?
A computer science background can be helpful, but it is not the only path. DevOps careers can evolve from infrastructure roles, hands-on technical experience, and continuous self-learning. Many companies value adaptability, problem-solving ability, and mindset just as much as formal credentials.
Is DevOps engineering stressful?
DevOps can be stressful during large migrations or infrastructure changes because deadlines are firm and systems are critical. However, for people who enjoy solving complex problems and working collaboratively, that pressure can feel energizing rather than overwhelming. Much of the stress comes from constant change and responsibility.
What personality traits help someone succeed in DevOps?
Successful DevOps engineers tend to think holistically about systems, stay adaptable when tools and processes change, and communicate well with other teams. Empathy is important because internal teams rely on DevOps for support. Being willing to ask thoughtful questions and continuously learn is essential for long-term success.
Is remote work common in DevOps, and what is work-life balance like?
Remote work is common in DevOps roles. The flexibility can be a major benefit, especially for family life. However, without a commute or physical separation from the office, it can be harder to mentally shut off. Setting clear boundaries and intentionally closing the laptop at the end of the day is critical for maintaining balance.
Other Technology & Engineering (STEM) Careers
Listen on: Spotify | Apple Podcasts | YouTube | Amazon Music
Interested in being a guest or partnering with us? Contact us here.