How I find problems to solve as a staff engineer
Engineers debating how to operate at “staff” level focus less on finding any problem and more on choosing high‑leverage ones, often by spotting recurring pain points, root causes, and organizational bottlenecks rather than just assigned tickets. Many note that this kind of impact depends heavily on company context: in some large, infrastructure-heavy or bottom‑up cultures it’s expected and rewarded, while in more top‑down, product‑driven or bloated organizations it’s constrained by politics, lack of autonomy, and misaligned incentives. There’s broad agreement that real seniority involves prioritization, cross-team influence, and sometimes saying no to visible but low‑value work, even as layoffs, title inflation, and AI are reshaping what “staff+” means in practice.
Problem Finding vs Prioritization
- Many say “finding problems” is trivial; the real challenge is prioritizing among a huge backlog and being comfortable letting low-value issues languish.
- High leverage work is often about spotting patterns across many small complaints and solving a shared root cause.
- Others note the chicken‑and‑egg issue: if you don’t provide a timely solution, teams build their own workarounds and won’t later migrate to your “proper” solution.
What “Staff+” Work Looks Like
- Common view: staff engineers should focus on:
- Problems too hard or too cross-cutting for juniors to own.
- Architectural or systemic fixes that remove whole classes of bugs.
- Org-wide or multi-team issues, not just local bug queues.
- Several emphasize delegation: if you can fix a task in a day, it’s often better to let others do it and reserve your time for hard-to-identify, ambiguous problems.
- Impact is often measured as:
- Speeding up others (removing friction, papercuts).
- Stopping bad or over-engineered projects before they ship.
Autonomy, Organizational Culture, and Politics
- Strong split on trends:
- Some report declining engineer autonomy, more top‑down product control, heavier process, and promotion driven by optics.
- Others claim the opposite over long careers: more bottom‑up influence now than decades ago.
- Many say staff+ work inevitably includes politics: building sponsorship, trading favors, navigating incentives, and fitting work into roadmaps.
- Several note that without supportive leadership or the right reporting line (e.g., to a director), staff+ behavior is hard or punished.
Incentives, Metrics, and “Done”
- Misaligned incentives (deadline pressure vs outage risk) push engineers to ship half‑finished migrations or incomplete work.
- Some treat tickets/points as “CYA” against future metric‑driven layoffs, even if current managers claim not to care.
Careers, Titles, and Skepticism
- Titles like “staff engineer” are seen as highly inconsistent across companies; some dismiss title‑centric essays as navel‑gazing.
- Others argue the mindset—owning ambiguous, impactful problems—is valuable regardless of title.
- A few suspect the article’s prose might be AI-generated, citing stylistic tics, and criticize cliché language like “superpower.”