Giving Hard Feedback to Seniors With More Experience Than You
Authority comes from title, obedience doesn't. A conversation structure that preserves relationships and changes behavior.
Topic guide
Leading engineering teams in practice: communication, feedback that accelerates growth, people development, and leading distributed teams.
4 topics · 23 articles
Explaining technical decisions to the team and to the business.
Authority comes from title, obedience doesn't. A conversation structure that preserves relationships and changes behavior.
Boards don't care about Kubernetes. They care about risk, cost, and deadlines. Translating technical roadmaps into business language.
Engineering, product, and business fight for the same week with different numbers. A cross-roadmap review, a shared impact matrix, and a decision record put them in one room.
Three managing-up rituals for staff engineers: a two-line update every two weeks, risk logged before the fire, and a decision ask with a deadline.
A one-page strategy structure: the constraint, a dated decision, rejected alternatives, 90 days of delivery, and a review written in the file itself.
Feedback that accelerates growth and a culture that holds the team together.
Every decision routing through you means a team that stops when you leave. Mentorship systems that build independent deciders.
Burnout rarely shows up as a cry for help. It shows up as worse code, declined meetings, and untaken vacations.
Teams that punish failure start hiding failure. Blameless post-mortems turn incidents into defenses against repetition.
Whoever stays works double while waiting for their own layoff. A 90-day plan to stabilize the remaining team.
Seniors accept a counteroffer when they stop deciding. Hold them with a new problem, a decision that leaves a mark, and a peer at their level.
Incident actions with an owner and a 30-day deadline, the old list reviewed every meeting, a focus on system causes, and the lesson published company-wide.
Hiring, growing, and organizing engineers from junior to senior.
What the Levels.fyi 2025 report publishes on the total compensation of engineers in the US, by level, and what it does not answer about engineering managers.
Code gets rewritten. Teams don't. People and process assessment predicts post-acquisition success better than any repo audit.
Whiteboard algorithms measured memorization. Candidates use AI at home and companies redesigned processes. What works now.
An OKR nobody checks after planning season is theater. Three tests separate real objectives from performance.
Selling engineering services abroad multiplies revenue 5x in dollars. Timezone, English, and compliance requirements nobody mentions.
AI now does the work that trained juniors. Companies that skip redesigning progression run out of seniors by 2030.
Leading remotely with async communication and clear structure.
Remote teams fail through slow decisions and lost context. Written protocols fix both.
An internal platform team pays off when five or more squads solve the same infrastructure problems in parallel. Below that, fixed cost with no return.
Lines of code and velocity died as metrics. What to measure when part of the code comes from a machine.
A team of six names a tech lead with no written scope and ends up with four frameworks for one problem. Written scope, review against a standard, and one senior per domain prevent it.
A founding CTO who still ships code full-time becomes the bottleneck: pull requests waiting, decisions queued, architecture nobody else explains. The signals, the work that sits with the CTO, and a 90-day transition in three phases.
Going from 10 to 50 engineers takes squads by domain, an internal platform team, a written decision guide, and a standing 15% capacity reserve for maintenance. The structure that changes speed within weeks and the metrics that show whether the product improved.
When you want your main job to be developing people, not systems. Solid technical experience helps (many people switch after 5+ years as an IC), but motivation matters more than tenure.
A manager usually leads 4 to 8 people well; a director, 2 to 4 managers. Beyond that, 1:1s and follow-up become a formality.
Be specific, private, and actionable. Describe the behavior and its impact, agree on the next step, and follow up over the next weeks.
Weekly, for 30 to 60 minutes. Every two weeks works with more senior people, as long as the meeting is not cancelled often.
Write down decisions, announcements, and proposals. Talk live about careers, conflicts, and sensitive topics.