Career¶
20 cards — 🟢 7 easy | 🟡 9 medium | 🔴 4 hard
🟢 Easy (7)¶
1. What is the Impact Formula for writing resume bullet points?
Show answer
[Action verb] + [what you built/changed] + [quantified result]. Quantified results include time saved, scale, reliability, cost, risk, and speed.2. What does the STAR method stand for in behavioral interviews?
Show answer
Situation (set context), Task (your responsibility), Action (what you did), Result (quantified outcome).3. What is "title arbitrage" in the ops job market?
Show answer
The same work can carry different titles at different companies with vastly different pay. A "Senior SysAdmin" at one company may do identical work to a "DevOps Engineer" at another for 60% of the salary. Search across all equivalent titles when job hunting.4. What five topics should a productive 1:1 with your manager cover?
Show answer
Priorities (what matters most right now), blockers (what is slowing you down), feedback (specific and actionable), expectations (are they clear?), and growth (skills, projects, career direction).5. Why should you raise problems with your manager early rather than waiting?
Show answer
Problems become more expensive and political when hidden. Early disclosure gives more options for resolution and builds trust. Waiting until a problem is a crisis limits everyone's choices.6. Why are "dumb" questions often the most valuable to ask?
Show answer
They expose hidden assumptions that everyone else takes for granted. They accelerate learning by cutting through jargon and forcing clear explanations. Senior engineers who ask basic questions often uncover real issues.7. Is managing the relationship with your manager partly your responsibility?
Show answer
Yes. Proactively sharing status, asking for clarity on expectations, bringing solutions along with problems, and requesting specific feedback are all your job. A good manager-report relationship requires effort from both sides.🟡 Medium (9)¶
1. Name three things that should NOT appear on an ops engineer's resume.
Show answer
Microsoft Office proficiency, an unfiltered dump of every technology ever touched (curate instead), and generic objectives statements like "Seeking a challenging role."2. How can ops engineers demonstrate competence when their work is behind a corporate firewall?
Show answer
Homelab documentation on public GitHub, blog posts/write-ups, open-source contributions (even small PRs), hands-on certifications (CKA, RHCE), conference talks or meetup presentations, and sanitized architecture diagrams with company details redacted.3. What five components beyond base salary should you negotiate in total compensation?
Show answer
Signing bonus, annual bonus or equity, remote work allowance, training budget or conference attendance, and on-call compensation.4. What differentiates a Staff engineer from a Senior engineer in the ops career ladder?
Show answer
The differentiator is not deeper technical skill but broader organizational influence. Staff engineers don't just solve problems — they identify which problems are worth solving. The transition requires influencing architecture across teams.5. Why is "how am I doing?" a poor way to ask for feedback?
Show answer
It is too vague to produce useful answers. Better: ask about specific recent work, a particular skill, or a concrete situation. "What could I have done differently on the X project?" produces actionable feedback.6. Why is understanding your manager's priorities important for your own success?
Show answer
Your work is evaluated in the context of team and organizational goals, not in a vacuum. Aligning your efforts with your manager's priorities makes your contributions visible and valued.7. When is deep under-the-hood understanding most valuable?
Show answer
During debugging hard problems, when depending on leaky abstractions, when designing durable systems, and when making real tradeoffs instead of cargo-cult choices. Surface knowledge breaks down at these moments.8. Why does reading dependency source code change your confidence as an engineer?
Show answer
It replaces guesses about behavior with evidence. You stop depending on incomplete documentation and develop the ability to answer your own questions. Even partial source reading dramatically improves debugging and design decisions.9. What does writing a design doc force you to do?
Show answer
Think precisely about constraints, make assumptions explicit, discuss tradeoffs openly, and build shared understanding with your team. Design docs prevent expensive mid-build discoveries.🔴 Hard (4)¶
1. What are the three types of technical interview patterns for ops roles, and what approach should you take for each?
Show answer
(1) Architecture Whiteboard: start with requirements, draw diagram, explain trade-offs, mention failure modes/scaling/observability/security. (2) Troubleshooting Scenario: think aloud, start from user-facing symptom, work through the stack systematically. (3) Live Coding/Config: start with skeleton, get it working, then add production concerns like error handling, idempotency, and security.2. Transform this weak resume bullet into an impact-focused one: "Managed 1,500 Linux servers across three data centers."
Show answer
Reduced manual provisioning effort by 40% across a 1,500-server fleet through Ansible automation, cutting new server deployment from 4 hours to 25 minutes. The key is adding the action, the method, and the quantified result."3. Why is applying to 100 jobs with the same resume an anti-pattern, and what is the better approach?
Show answer
Each application should have a tailored resume matching keywords and highlighting the most relevant experience for that specific role. Five tailored applications beat fifty generic ones. Most senior ops roles are filled through referrals, so building a human network through meetups, Slack communities, and open-source contributions is more effective than mass applying.4. What study habits accelerate building deep expertise?