Running Effective 1:1s for Senior Engineers Who Don't Think They Need Them

"Do we really need to do this every week?"

A staff engineer asked me that in our second 1:1. He was one of the best engineers on the team. He was also right to ask, because up to that point our 1:1s had been useless. I would ask what he was working on. He would tell me things I already knew from standup and the board. We would both feel the twenty minutes drain away, and then we would go back to our real work, quietly relieved.

He was not being difficult. He was being efficient. He had correctly noticed that the meeting was pure overhead, and he was doing what good engineers do with overhead: trying to delete it.

That question forced me to get honest. Most 1:1s with senior engineers are bad, and the engineers are not wrong to resist them. The problem is not that senior people don't need 1:1s. The problem is that most managers run the exact meeting a senior person has no use for. This post is about running the other kind.

Why your best engineers resist the 1:1

Start by understanding the resistance, because it is rational.

A senior engineer already has visibility. They know what they are working on. They know the state of the project. They are usually in the design discussions and the planning. So when you use the 1:1 to ask "what are you working on this week," you are asking a question they can answer in their sleep, about information you should already have. To them, that meeting is a tax with no return.

There is a second thing going on, and it is subtler. Strong engineers are often introverted, private, and allergic to anything that feels like corporate ritual. A recurring calendar block titled "1:1" can read as exactly that. Performance theater. A box the manager checks. They have sat through years of managers who ran 1:1s because a management course told them to, not because the meeting did anything. Their skepticism is earned.

So when a senior engineer pushes back on the 1:1, do not take it as a discipline problem or a bad attitude. Take it as accurate feedback about the meeting you have been running. The fix is not to insist on the ritual. The fix is to make the meeting good enough that they stop wanting to skip it. If the meeting is genuinely valuable to them, you will not have to enforce attendance. They will show up because it is worth their time, which is the only reason that ever holds.

Status is not the point, and never was

Here is the reframe that changed everything for me. The 1:1 is not for information that lives somewhere else.

If I can learn it from the board, the standup, the PR, or the sprint review, it does not belong in the 1:1. Status updates are the single most common way managers waste this meeting, and they are the fastest way to lose a senior engineer's respect. The moment you spend the 1:1 on "so where are we on the migration," you have told them the meeting is for your convenience, not their benefit.

The 1:1 is for everything that does not fit anywhere else. The half-formed concern they would never raise in a group. The frustration that is not yet a formal complaint. The career question they are only starting to ask themselves. The disagreement with a technical direction that they are sitting on because the room moved on. The context about the org that they cannot see from where they sit. None of that surfaces in a standup. All of it matters enormously, and the 1:1 is the only place it has room to come out.

When I stopped treating the 1:1 as a status meeting and started treating it as the one place we talk about the things that have no other place, the resistance faded. Not because I insisted. Because the meeting finally paid for itself.

Make it their meeting, and prove it

The single most effective change I made was to stop bringing my agenda and start asking for theirs.

A 1:1 that the manager drives is a status meeting wearing a disguise. A 1:1 that the report drives is an actual 1:1. So I open with some version of "what is on your mind," and then I shut up. This is harder than it sounds, because silence is uncomfortable and the manager's instinct is to fill it. Resist that. The silence is where the real thing surfaces. If you jump in to fill every pause with your own updates, you have taken their meeting away from them and turned it back into yours.

With senior engineers, this handoff of control matters even more, because they can smell a scripted meeting instantly. If they sense you are running down a manager's checklist, they will give you checklist answers and reveal nothing. If they sense the time is genuinely theirs, to use however they want, they will eventually bring the things that count.

The hard part is that this only works if you mean it. If you ask "what is on your mind" and then steer every answer back to the project you care about, they will notice within two meetings and stop bringing anything real. Making it their meeting is not a technique you deploy. It is a stance you hold, week after week, until they believe it.

There is a predictable moment where this gets tested: the week they say "I've got nothing." Do not panic and fall back into status questions to fill the time. And do not end the meeting in four minutes, which trains them to always say "nothing" so they can get the time back. Instead, use the space for something you would not otherwise make time for. This is when I ask a bigger question, the kind there is never room for when the agenda is full. What do they think we are getting wrong as a team? Where is the codebase heading that worries them? What would they change if they had my job for a week? "I've got nothing" almost always means "I have nothing tactical," and it is the perfect opening for the conversations that actually matter to a senior person.

For senior people, go up the ladder, not down

There is a specific trap with senior engineers: managing them like junior ones. The topics that help a junior engineer grow are not the topics a senior engineer needs.

A junior engineer's 1:1 is often tactical. What are you stuck on, what should you learn next, here is some feedback on how you handled that review. A senior engineer has mostly solved those problems. Bring them the same tactical menu and you are wasting their time and, worse, signaling that you do not see how far past that they are. Nothing frustrates a strong engineer more than being managed a level or two below where they actually operate.

So with senior people, aim higher. Talk about scope and influence, not tasks. Talk about the problems the team is not looking at yet. Talk about where the architecture is heading over the next year and whether we are set up for it. Talk about the other engineers they could be growing. Talk about the organizational friction they see but have not named. These are the questions that respect their level, and they are also the questions that turn a senior engineer into a force multiplier instead of just a very productive individual.

The best senior engineers are hungry for exactly this kind of conversation and rarely get it, because most managers are too busy running status meetings to have it. Be the manager who asks the bigger questions, and the 1:1 stops being a chore they tolerate and becomes one of the few places they get to think out loud about the things they actually care about.

A concrete example. I once had a senior engineer whose 1:1s were flat for a month. Short answers, nothing real. Then in one meeting I stopped asking about his current work entirely and asked what he thought the biggest architectural risk on the team was, the one nobody was talking about. He lit up. He had been sitting on a concern about how our event schema was going to fall apart once a second team started producing to it, and he had not raised it because it was not anyone's assigned problem and it felt like not his place. That single question surfaced a real risk, gave him a mandate to go fix it, and changed the tenor of every 1:1 after it. The work had been the wrong altitude the whole time. The moment I raised the altitude, the meeting came alive.

The questions that actually open people up

It helps to have a few real questions ready, because "how's it going" gets you nothing. These are not a script to run down. They are prompts I reach for when the conversation needs a door opened, and I use one, not all of them.

"What is frustrating you right now that you have not said out loud?" This gives explicit permission to complain, which senior people often suppress because they think it is unprofessional. The frustrations are usually where the useful signal is.

"If you were me, what would you be worried about that I am probably not?" This flatters their judgment, which is real, and it surfaces the org-level and technical risks they can see from their seat that you cannot from yours.

"What is the most pointless thing you had to do this week?" A great way to find process rot and friction. Senior engineers have a finely tuned sense for waste, and they will tell you exactly where it is if you ask.

"What would make you consider leaving?" This one is blunt and I use it rarely, but asking it before someone is halfway out the door is worth more than any exit interview. The answer tells you what to protect.

None of these work if the trust is not there yet. But once it is, one good question can do more in a 1:1 than an hour of careful status review.

Careers, even when they are not asking

Senior engineers often act like they have their career handled. Many of them do not, and even the ones who do still benefit from a manager who thinks about it with them. But they will almost never bring it up on their own, because raising it can feel like weakness or like angling for something. So you have to open the door.

Not every week. That would be forced and strange. But every so often, deliberately step out of the day-to-day and ask the longer question. What do you want to be doing in two years that you are not doing now? Where do you feel stuck? Is there a kind of work you are hungry for that I am not giving you? For a lot of senior engineers, no manager has asked them these questions in years. Everyone assumes the senior person has it figured out. The senior person, meanwhile, is quietly wondering whether they have plateaued.

This is also your single best retention tool, and it is nearly free. The senior engineers who leave rarely leave over money. They leave because they got bored, or stopped growing, or felt invisible, and no one noticed in time to do anything about it. The 1:1 is where you notice. A manager who is genuinely paying attention to a senior engineer's growth, and doing something about it, is very hard to leave. That awareness lives almost entirely in this meeting or nowhere at all.

Close the loop, or the channel dies

There is one failure that will quietly kill a 1:1 faster than anything else, and it is not a bad question or an awkward silence. It is raising something and watching it vanish.

A senior engineer finally trusts you enough to surface a real problem. The build process is slow and it is bleeding the whole team an hour a day. Another team keeps breaking a shared contract. They are frustrated with a teammate. They brought you the thing, which took some trust to do. And then nothing happens. You nodded, you agreed it mattered, and the next week you never mentioned it again. The lesson they learn is immediate and permanent: talking to you does not change anything, so why bother. The channel you spent months building goes dark, and it does not come back easily.

So I keep a simple running doc for each person, shared with them, where I jot the things that come up. Not to surveil them. To make sure nothing they raise falls through the cracks. When something comes up that I can act on, I act on it, and I tell them what happened, even when the answer is "I pushed on this and the answer was no, here is why." Especially then. A senior engineer can live with a no. What they cannot live with is raising something important and hearing nothing, ever, because that tells them the meeting is theater after all.

Closing the loop is also how you prove the 1:1 has power. The first time an engineer mentions a piece of friction and then watches it actually get fixed because they mentioned it, the meeting earns a credibility it never had before. Now they know this channel does something. Now they bring you the bigger things. Every closed loop widens the pipe.

Consistency is the whole trust mechanism

None of this works on the first try. The deep stuff, the career doubts, the disagreement they have been sitting on, the early signs of burnout, none of it comes out until the person trusts you. And trust is not built in one good meeting. It is built by showing up, week after week, and being the same reliable, genuinely-interested person every time.

Which is exactly why you must never cancel the 1:1 casually. I know the temptation. The week is slammed, the senior engineer seems fine, and the 1:1 looks like the most skippable thing on the calendar. So you cancel it, and it feels harmless. It is not. Every time you cancel, you tell that person, far louder than any words, that they are the lowest priority on your list. And with senior engineers, who were skeptical of the meeting to begin with, a cancelled 1:1 confirms their suspicion that it never mattered. Do it twice and you have taught them not to invest in it.

If you truly have to move it, move it, do not delete it, and say why. The protected, recurring, never-casually-cancelled slot is itself the message. It says this time is yours and it is not up for grabs. That reliability is what eventually makes someone comfortable enough to tell you the thing they have been holding back. You are not just holding a meeting. You are building the channel that carries the information you most need and are least likely to get any other way.

When they still don't want it

Sometimes you do all of this and a particular senior engineer still does not want a weekly 1:1. That is fine, and fighting it is a mistake.

The goal was never to force a ritual. The goal is an open, high-trust channel between the two of you. For most people, a consistent weekly 1:1 is the best way to build that. For some genuinely senior, self-directed people, weekly is too much and the meeting really is mostly overhead. With those people, I negotiate. Maybe we go to every other week. Maybe we keep it loose and talk when either of us has something, with a standing slot as the backstop. What I do not do is drop the channel entirely, because the day will come when something is wrong and I need it to already exist.

The move that works is to be direct about the actual goal. I will say something like: "I do not care about the meeting. I care that when something is on your mind, or something is off, we have an easy way to talk about it. Tell me the format that works for you." A senior engineer respects that, because it treats them like an adult instead of a box to check. Almost always, they choose something reasonable, and because they chose it, they actually engage with it. The engineer who resents an imposed weekly meeting will happily use a channel they helped design.

What it comes down to

The staff engineer who asked whether we really needed to meet every week eventually stopped asking. Not because I convinced him the ritual was sacred. Because the meeting changed. It stopped being a status update he could have sent over Slack and became the place we talked about the architecture two years out, the engineers he was mentoring, the parts of the org that were slowing us down, and, eventually, the fact that he was thinking about what came next in his career. That conversation kept him for another two years.

Senior engineers do not resist 1:1s because they are above being managed. They resist bad 1:1s, and they are right to. Make the meeting about the things that have no other home. Hand them the agenda and mean it. Aim at their level, not below it. Show up every single week without fail. Do that, and the engineer who wanted to delete the meeting becomes the one who brings the most important things in the building to it. The meeting was never the point. The channel is. Build the channel.