Career Engineering Footguns¶
Mistakes that stall your career, tank your interviews, or cost you tens of thousands in lifetime earnings.
1. Listing every technology you've ever touched¶
Your resume has 40 technologies in the skills section. The interviewer asks about Kafka — you used it once in a tutorial three years ago. Now you're exposed as someone who inflates their resume. Trust evaporates instantly.
Fix: Only list technologies you can discuss at interview depth. Split into "proficient" and "familiar" if needed. If you can't troubleshoot it in production, it's "familiar" at best. Five skills you own are worth more than forty you've touched.
2. Saying "we" for everything in interviews¶
"We built the monitoring stack." "We migrated to Kubernetes." "We automated the deployment pipeline." The interviewer has no idea what YOU did. Were you the architect, a contributor, or someone who attended the meetings?
Fix: Use "I" for your specific contributions: "I designed the alerting rules and built the Grafana dashboards. The team collectively migrated 30 services over three months — I owned the networking and ingress layer." Give credit to the team AND be specific about your role.
3. No numbers on your resume¶
"Managed Linux servers." "Improved deployment process." "Reduced downtime." How many servers? Improved by how much? Reduced from what to what? Without numbers, your resume reads like a generic job description, not a record of impact.
Fix: Quantify everything. Count servers, measure time saved, calculate cost reduction, track incident frequency. If you don't have exact numbers, estimate conservatively and say "approximately." "Managed approximately 500 RHEL servers" beats "managed Linux servers" every time.
4. Staying in a role where you've stopped learning¶
You're comfortable. The systems are stable. You know every quirk of the infrastructure. You haven't learned anything new in two years. Meanwhile, the industry moved from Docker Compose to Kubernetes to service mesh to platform engineering. You're now two generations behind.
Fix: Set a learning alarm. If you can't name something significant you learned in the last six months, start your homelab, pursue a certification, or start looking for a role that stretches you. Comfort is the career killer.
5. Accepting the first salary offer¶
The company offers $130K. You say "that sounds great" and accept. The role was budgeted for $150K. You just left $20K/year on the table — that's $100K over five years, before compounding.
Fix: Always negotiate. Even "Is there flexibility on the base salary?" signals that you know your worth. Research market rates on levels.fyi before the conversation. The worst they can say is "this is our best offer" — they won't rescind it because you asked.
6. Burning bridges when you leave¶
You're frustrated, underpaid, or mistreated. You quit in a blaze of truth-telling, send the angry Slack message, skip the two-week notice. Three years later, the hiring manager at your dream company calls your old boss for a reference.
Fix: Leave professionally regardless of how you feel. Give proper notice. Document your work for your successor. Thank your colleagues. The ops community is small. Your reputation follows you.
7. Over-preparing for the wrong interview format¶
You memorize LeetCode problems for an SRE interview that's actually about system design and incident response. Or you prepare architecture diagrams for a role that gives you a live troubleshooting exercise. You walk in prepared for the wrong test.
Fix: Ask the recruiter exactly what the interview process looks like. "What format are the technical interviews? Coding, system design, troubleshooting, or a mix?" Then prepare for what they actually test. If they won't tell you, prepare breadth over depth.
8. Ignoring the job description's red flags¶
"Fast-paced environment" (chaotic, no process). "Wear many hats" (understaffed). "Rockstar engineer" (they want one person to do three people's jobs). "Unlimited PTO" (no PTO tracking means social pressure to never take time off). You take the job anyway because the salary is good.
Fix: Read between the lines. Ask pointed questions in the interview: "How large is the ops team?" "What's the on-call rotation?" "How many production incidents per month?" "What's the average tenure on this team?" High turnover on the team you're joining is the loudest red flag.
9. Not practicing your outage stories¶
You have five years of great incident response experience. In the interview, you blank. You ramble. You can't remember the details. Your best war stories come out as vague, unfocused narratives. The interviewer thinks you lack depth.
Fix: Write down your top 5 outage stories in STAR format before every interview cycle. Practice telling them out loud. Time yourself — each story should be 2-3 minutes. Include: the symptom, your diagnostic process, what you specifically did, the outcome, and what you changed to prevent recurrence.
10. Treating the interview as a one-way evaluation¶
You answer every question but ask none. You don't evaluate the team, the infrastructure, the management, or the culture. You accept the offer and discover the on-call rotation is 1-in-2 with no escalation path, the "Kubernetes migration" is a pipe dream, and the CTO thinks SRE means "the team that gets paged."
Fix: An interview is bidirectional. Prepare 5-10 questions that reveal the real working conditions. Ask them to every person you meet. Pay attention to how they answer — hesitation, vagueness, and eye-rolling from current employees are data points. You're interviewing them as much as they're interviewing you.