How to Prepare for a Skip-Level Meeting

ملخص

Pixel shares practical advice for preparing for a skip-level meeting with your manager’s manager. Bring specific examples of what is working and slowing the team down, answer questions honestly, raise concerns thoughtfully, and ask about departmental priorities and decision-making.

DEV Community

Your Manager's Manager Has Booked a Skip Level Meeting With You

A thirty minute invitation appears in your calendar. It is from your manager's manager, the head of engineering, and the title just says catch up. You have spoken to her twice, both times in a lift. Your first thought is that something is wrong. Almost certainly nothing is. Many managers run skip level meetings, where they talk directly to people two levels below them. They do it to hear how things really feel on the ground, without everything being filtered through their managers first. It is usually a routine part of their job, and they may be meeting everyone on your team. So prepare, but lightly. Think of two or three things you would genuinely like her to know. Something that is working well and deserves credit. Something that slows the team down and that she might be able to change. Perhaps one question about where the department is heading. Write them down so you do not go blank. Expect open questions. What is getting in your way? What would you change if you could? How is the team doing? Answer them honestly and specifically. Our releases take two days because the test environment is shared with three other teams is far more useful to her than things are a bit slow sometimes. Be careful with one thing. If you have a problem with your own manager, a skip level meeting can feel like the moment to raise it. It can be, but think it through first. If you have not said it to your manager directly, it will usually be fairer, and work better, to do that first. Complaints that arrive from above without warning tend to damage trust on every side. If the problem is serious, or you have already tried, say so plainly and calmly, and stick to what happened rather than how you feel about the person. Use some of the time to learn, too. Ask what she is worried about this year, or what she wishes engineers understood about how decisions are made. You will rarely get a more direct view of the bigger picture. Afterwards, tell your manager the meeting happened and roughly what you talked about. No secrets, no surprises. That keeps everyone comfortable with the next one. – Asael Shinder
How to Prepare for a Skip-Level Meeting
Powered by Readybot.io

الأحدث من Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …

Why a Java HPA Got Stuck at 20 Kubernetes Pods

Pixel shares how a Spring Boot pricing service autoscaled to 20 Kubernetes pods and stayed there because the JVM retained committed heap memory after traffic …