Picture this: it's 3 am on a quiet Sunday. As a DevOps Engineer SRE, you're engrossed in the cool glow of your terminal, which has been your only companion for the last couple of hours. East Coast customers are starting to wake up and notice the site is down. After combing through release notes and logs, you discover a recently activated code path that bypasses pooled connections. A simple mistake, yet costly. With quick thinking, you deactivate the problematic feature flag, pacify the database, and breathe a sigh of relief as graphs return to normal.

Job done, you update the incident log and signal to your team that you'll be in late to catch up on much-needed sleep. Come morning, your peers applaud you. "Fantastic work, Alex! When do you even sleep?!"

You're the hero, right? With a vigilant eye on your Grafana dashboards and a readiness to jump in at odd hours, you've become the company's silent guardian. And while it may seem like you're doing all the heavy lifting, the seed of resentment begins to take root. You start to believe you're undervalued and overworked.

The Blind Spots

In our tale, the protagonist perceives their nocturnal interventions as proof of their indispensability. But let’s reframe the narrative and pose some critical questions:

1. Alerts and Accountability: Why didn’t the alerts reach anyone else? Reliable alerting systems are a foundational aspect of sound technical infrastructure. If only one person is noticing and reacting, there's a flaw in the system that needs addressing.

2. Team Dynamics: Why were you the lone ranger? Tech is a team sport, and working in isolation, especially under stress, can be counterproductive.

3. Processes and Protocols: Who altered the feature flag, and was it documented? Unplanned changes can lead to chaos. Proper change management protocols are essential.

4. Learning Opportunities: After each incident, what did the team and company learn? Postmortems aren’t about blame but growth. Without understanding and addressing root causes, history is bound to repeat itself.

5. Work-Life Balance: Is such a demanding relationship sustainable or even equitable? Burnout is real. By always being "on" you're setting yourself up for fatigue and potential health issues.

Building Sustainable Habits

To ensure you don’t fall into the hero trap:

1. Delegate and Trust: Share responsibilities. Trust that your teammates can and should handle issues too.

2. Prioritize Self-care: Recognize the importance of downtime. There's a diminishing return on effort, especially when tired.

3. Open Communication: Foster a culture where concerns are raised. If you're consistently noticing issues others aren't, discuss it.

4. Document Everything: Whether it's a minor fix or a major overhaul, ensure changes are documented for team visibility.

5. Revisit and Revise: Regularly review and update protocols, ensuring they reflect the current needs and challenges of the team.

Being proactive is commendable. However, when it morphs into a hero complex, it can strain both the individual and the team. The key is balance, ensuring you're an asset without sidelining the broader team or undermining processes.

I write weekly articles on tech, business, and entrepreneurship. Consider subscribing if you’d like to read more from me.

Having spent a decade in the tech world, I sometimes find myself reflecting on the dizzying journey. From a high school graduate in a rural Midwestern town to a technical lead at a FAANG, the path has been unexpected, to say the least. Alongside big names, I've also dipped my toes in the vibrant waters of startups and other large enterprises.

But let’s hit pause on my story. Instead, I want to address a question I’m often posed: "How did you break into tech?" From dear friends to casual acquaintances and even digital connections, I've been approached for advice by people across the spectrum: some with Computer Science degrees, others college-bound, and some, like me, without any formal higher education.

Their anticipation often turns into a thousand yard stare as I delve deep into the details. Yet, I firmly believe these insights could be invaluable to many. So here's a distilled version of my advice, tailored for readers like you.

Tech's appetite for talent has been insatiable, and indications are this trend will persist. But brace yourself; the field can be fierce. Many roles get filled internally before ever seeing the light of a job board. Intra-company moves are a norm, so don’t get misled by public listings. My golden rule? Network relentlessly. LinkedIn is your friend, and so are job platforms like Dice and Indeed. Cast your net wide.

Skill 1: Mastering Interviews

Kickstart by sending out your nascent resume far and wide. You may soon find yourself inundated with outreach. Embrace every opportunity, regardless of its initial appeal. I quickly discerned a typical sequence: initial outreach, non-technical recruiter phone screen, technical staff phone discussion, followed by a mix of phone or in-person technical interviews. Becoming familiar with how to communicate during an interview is critical.

Skill 2: Efficient Note-Taking

Companies often grapple with similar challenges using identical technologies. While on my first interview spree, I jotted down every piece of information. Anything unfamiliar? I'd earmark it for post-interview study. The process evolved me. By the end, I had accumulated a hefty collection of notes, practically a cheat sheet for any interview topic.

Skill 3: Embracing Failure

Brace for rejection. Even seasoned tech veterans face it. There's a myriad of reasons behind a 'no', and many are beyond your grasp. After almost a hundred setbacks, I finally started cracking on-site interviews. Interestingly, as I grew accustomed to the looming shadow of failure, I began to relax during crucial interviews. And guess what? It worked. Offers started trickling in, and to think it all began with a rural kid that had a smattering of freelance web development gigs.

I sincerely hope this offers you a roadmap and gears you up for the exhilarating trek ahead. Best of luck on your journey!

Subscribe now