Solved: What are the signs of a good company to work for?

#devops #programming #tutorial #cloud

🚀 Executive Summary

TL;DR: Engineers often prioritize tech stacks and perks over culture, leading to toxic workplaces. This guide provides a framework—interview reconnaissance, digital footprint analysis, and a 90-day litmus test—to identify critical green and red flags, ensuring a healthy engineering environment.

🎯 Key Takeaways

A healthy engineering culture conducts blameless postmortems, focusing on systemic failures and implementing concrete process improvements (e.g., CODEOWNERS, mandatory approval steps in CI/CD pipelines) rather than assigning individual blame.
Good companies actively manage technical debt with a clear plan, integrating its resolution alongside new feature development, rather than perpetually de-prioritizing it.
Be wary of job descriptions demanding ‘expertise’ in a vast array of competing technologies for limited experience, as this often signals an immature, chaotic organization seeking an underpaid miracle worker.

As a Senior DevOps Engineer, I’ve learned that a healthy engineering culture is more valuable than any flashy perk. This is my field guide to identifying the green flags of a great company before you sign the offer letter, and recognizing the red flags that tell you to run.

Beyond the Paycheck: A DevOps Engineer’s Field Guide to Spotting a Good Company

I still remember the 3 AM page. It was for prod-db-cluster-01, the main transactional database for a previous employer. A “routine” migration script, pushed to production at 10 PM on a Friday by a desperate project manager, had gone horribly wrong. The rollback failed. The backups were three days old. For the next 72 hours, a handful of us slept at the office, fueled by bad coffee and pure adrenaline, manually rebuilding tables. The worst part? The postmortem wasn’t about the failed process or the lack of testing; it was a witch hunt to find who to blame. That’s when I learned the most important lesson of my career: the tech stack doesn’t matter if the culture is broken. No salary is worth that.

The “Why”: Why We End Up in Bad Jobs

Let’s be honest. We get so focused on the technical interview—solving LeetCode problems, explaining the nuances of Kubernetes networking, or whiteboarding a CI/CD pipeline—that we forget something crucial: we’re interviewing them as much as they’re interviewing us. The root cause of landing in a toxic environment is often a failure to vet the company’s culture. We see a big salary, hear about “unlimited PTO,” and get excited about the tech, ignoring the subtle (and sometimes not-so-subtle) warnings that signal a dysfunctional workplace. This guide is about building a framework to look past the sales pitch and see the reality.

Strategy 1: The Interview Reconnaissance

This is your first and best chance to gather intelligence. Don’t just answer questions; ask pointed ones. Their answers—and how they answer—will tell you everything. Forget “What’s the company culture like?”. That’s a softball. Get specific.

“Can you describe your on-call process and what a typical on-call week looks like?” – If they don’t have a clear answer, or it sounds like one person is a single point of failure, that’s a huge red flag. A good answer involves clear rotations, escalation policies, and a focus on reducing pages over time.
“Tell me about the last major outage. What was the postmortem process like, and what changed as a result?” – This is the money question. You’re listening for one word: “blameless.” If they name names or talk about “human error,” run. A good company talks about systemic failures and the concrete steps they took to improve the system (e.g., “We realized our Terraform plan wasn’t being peer-reviewed for that module, so we added a CODEOWNERS file and a mandatory approval step in the Jenkins pipeline.”).
“How does the team prioritize technical debt versus new feature development?” – Every company has tech debt. A good one has a plan to manage it. A bad one pretends it doesn’t exist or constantly de-prioritizes it until everything is on fire.

Pro Tip: Always ask to speak to a peer-level engineer on the team you’d be joining, without a manager present. Ask them what the most frustrating part of their job is. Their candor will be invaluable.

Strategy 2: The Digital Footprint Analysis

Before you even get to an interview, you should be doing your homework. A company’s public-facing presence can reveal a lot about its internal health.

Start by looking for these signals. I’ve put them in a table to make it clear what to look for and what to avoid.


Green Flags (Signs of Health)	Red Flags (Signs of Trouble)
Engineers are active on tech blogs or speak at conferences. It shows the company invests in its people.	Glassdoor reviews are either 5-star perfection or 1-star rants. Look for the balanced 3 and 4-star reviews for the truth.
Open source projects are maintained. Pull requests and issues are handled professionally.	The job description is a laundry list of every technology under the sun for a non-senior role.
The company’s LinkedIn shows reasonable employee tenure (1.5+ years). People are sticking around.	High turnover, especially in the engineering department. Check LinkedIn to see if people flee after less than a year.

And please, be wary of the “Rockstar” job description. If you see something like this, it’s a sign they don’t know what they want and will probably burn you out.

Job Title: DevOps Ninja / SRE Rockstar

We need a 10x engineer to own our entire infrastructure. Must be an expert in:
- Kubernetes, Docker, AWS, GCP, Azure
- Terraform, Ansible, Pulumi, Chef
- Jenkins, GitLab CI, CircleCI, ArgoCD
- Python, Go, Bash, Ruby, Java
- Prometheus, Grafana, ELK Stack, Datadog

Must be willing to work hard and play hard! 3+ years experience required.

Warning: A role asking for “expertise” in 20 different, often competing, technologies for only 3 years of experience is a sign of a deeply immature or chaotic organization. They aren’t looking for an engineer; they’re looking for a miracle worker they can underpay.

Strategy 3: The 90-Day Litmus Test

This is the “nuclear option,” but it’s really a mindset. The probation period is a two-way street. Your first three months are the final, most critical phase of the interview. You have to be willing to walk away if you discover you were sold a lie.

What to watch for in your first 90 days:

Onboarding: Is it a structured process with documentation, access granted on day one, and a clear plan? Or are you thrown into the deep end and told to “figure it out”? A chaotic onboarding reflects a chaotic company.
Psychological Safety: When someone on your team makes a mistake—like running a terraform apply that brings down a staging environment—what happens? Is it a learning opportunity for the team, or does the person get reprimanded? A culture of fear kills innovation and reliability.
Documentation: Is internal documentation valued, maintained, and accessible? Or is all critical knowledge stored in the heads of a few “heroes”? A company that documents its processes is a company that can scale and is resilient to people leaving.

The “nuclear” part is having the courage to say, “This isn’t a good fit,” and activating your network to find a new role. It feels drastic, but it’s far better than letting a toxic job destroy your mental health and passion for this field. We build resilient systems for a living; it’s time we started demanding the same resilience from the companies we work for.