On Being a Senior Engineer (2012)

Reactions to the Article

• Some see the opening “younger generation” framing as off-putting and dismissive; others argue that the generational quote is just a hook and the rest is still valuable and timeless.
• Several readers say the piece helped them diagnose friction with colleagues labeled “senior” but behaving differently than the article’s ideal.

What “Senior Engineer” Should Mean

• Strong emphasis on ownership: taking responsibility for systems, trade‑offs, incident response, estimates, and communicating with stakeholders.
• Senior vs. staff/principal often distinguished by scope and risk: larger systems, longer time horizons, more cross‑team or company‑wide impact.
• Some stress that senior ICs should still write code; “promotion away from coding” into meetings and slideware is seen as a common but bad pattern.
• Others argue that the whole “senior” label is mostly for HR or insecure egos; actual impact and craftsmanship matter more than titles.

Titles, Levels, and the Job Market

• Debate over defining seniority by years of experience vs. demonstrated skills and impact.
  • One camp: time-based bands align better with external market expectations and reduce internal calibration complexity.
  • Counterpoint: time alone promotes mediocrity and misses fast-growers or long‑tenured mid‑level engineers.
• Concern that withholding “junior/senior” titles can harm employees when job-hopping, effectively creating “handcuffs.”
• Big-company “terminal levels” turn “senior” into a de facto “safe to keep” label rather than a craft-based distinction.

Estimation, Risk, and Trade‑offs

• Some dislike the article’s stance that avoiding estimates shows lack of seniority, calling it unrealistic and blaming individuals instead of process.
• Others say the key is not perfect prediction but taking responsibility, decomposing work, and clearly expressing uncertainty.
• Seniority is linked to making explicit trade‑offs (speed vs. quality, uptime vs. cost) and avoiding over‑engineering expensive, low‑impact work.

Communication, Influence, and Politics

• Multiple comments tie level to the ability to convince others and influence outcomes, not just technical output.
• High “level” is framed as marginal impact on company outcomes (likened to sports metrics like WAR).
• Tension emerges for technically strong engineers who dislike or struggle with communication; some feel forced to switch focus from tech to “soft skills.”

Skill, Competence, and Gatekeeping

• One subthread argues many “senior” web developers can only assemble boilerplate and lack core language and protocol understanding; others see this as elitist gatekeeping and misaligned with most job needs.
• Broader agreement that genuine seniority combines technical depth, breadth across the stack, and the ability to reduce chaos for others—though exact thresholds remain contested and context‑dependent.