Engineering Manager 1:1s for Senior ICs: A Template That Actually Develops People

Engineering manager 1:1s with senior individual contributors are categorically different from 1:1s with junior engineers. With juniors, the manager has things to teach, tasks to assign, work to review, growth to direct. With senior ICs — staff, principal, distinguished engineers — the manager often knows less about the technical work than the IC does. The 1:1 either becomes a status update (which the senior IC resents) or it becomes nothing (which the senior IC also resents). Neither produces development.

This post walks through the 1:1 template that actually develops senior engineers.

What senior ICs actually need from 1:1s#

Senior ICs have already mastered the basics. They don’t need their manager teaching them how to write code, how to design systems, or how to interact with stakeholders. They need different things:

Career direction. Senior IC careers branch — deep technical specialization, breadth across multiple domains, technical leadership, hybrid IC/management paths. The 1:1 is where the manager helps the IC navigate the branch.

Organizational context. Senior ICs need to understand company strategy, engineering organization politics, leadership thinking, market dynamics. Information their manager has and they don’t.

Sounding board. Senior ICs make hard technical and strategic decisions. They benefit from someone smart who can ask good questions and help them think through their reasoning.

Promotion advocacy. When promotions are decided in committees, the manager’s advocacy matters. The 1:1 is where the manager builds the case to advocate for.

Removing organizational friction. Senior ICs hit organizational obstacles — alignment with other teams, resource conflicts, decision processes. The manager has authority and relationships the IC doesn’t.

Recognition and feedback. Even senior ICs benefit from explicit recognition of good work and direct feedback on areas to improve.

The template#

Through multiple client engagements, we’ve converged on a four-section template for senior IC 1:1s.

Section 1: Strategic context (5-10 minutes). Manager shares what’s happening at the company, engineering org, or broader market that the IC should know about. Particularly important for ICs who are heads-down on technical work and don’t have natural access to leadership conversations.

Section 2: Current work check-in (10-15 minutes). Not a status update. A conversation about what the IC is finding interesting, where they’re stuck, what they want to talk through. The manager listens more than talks. Specific questions: “What’s the most interesting thing you’re working on? What’s the most frustrating? Is there anything where you’d value my perspective?”

Section 3: Career and development (10-15 minutes). Periodic — not every week, but every few weeks. Topics: what does the IC want their career to look like in 2-5 years? What capabilities are they building? Where does their current work fit into that trajectory? What promotion criteria are they working against?

Section 4: Manager asks and feedback (5-10 minutes). The manager shares what they need from the IC and provides direct feedback. Often the harder part — managers who only do positive reinforcement don’t develop senior engineers.

The questions that actually work#

A few questions consistently produce useful 1:1 conversation with senior ICs.

“What’s the most interesting problem you’ve thought about this week?” Opens conversation about substantive work without making it a status update.

“What’s a decision you’re trying to make where my perspective might help?” Positions the manager as a sounding board rather than a status-collector.

“What would you do differently if you were running this team?” Surfaces senior ICs’ organizational perspectives, which managers often need to hear.

“What’s stopping you from doing what you think we should do?” Identifies organizational friction the manager might be able to help remove.

“Where do you want to be in 18 months?” Surfaces career direction without putting the IC on the spot about specific next steps.

What to avoid#

Several patterns consistently undermine senior IC 1:1s.

Status update format. Senior ICs work on substantive things; reducing the conversation to “what are you working on this week” is insulting.

Generic career framework. “Tell me about your goals” without context produces generic answers. The conversation should be specific.

Withholding context. Managers who treat organizational information as need-to-know fail their senior ICs. Senior ICs need to understand what’s happening to make good decisions.

Avoiding hard feedback. Senior ICs are professionals; they want direct feedback. Soft-pedaling concerns is patronizing.

Skipping 1:1s. When the manager cancels 1:1s, the message is “you’re not important enough.” Even with senior ICs who don’t need weekly hand-holding, regular 1:1s should hold.

The promotion conversation#

A specific challenge: discussing promotion. The pattern that works:

Be honest about timing. If promotion is realistic in the next cycle, say so. If it’s not, explain what would need to change.

Be specific about criteria. Promotion criteria at senior IC levels are often fuzzy. The 1:1 is where the manager translates vague criteria into specific evidence the IC can build.

Be honest about advocacy. The manager’s advocacy matters in promotion committees. If the manager would advocate, say so. If they have reservations, say what they are.

Don’t promise what you can’t deliver. Promotion is committee decision; the manager doesn’t unilaterally control it. Pretending otherwise creates distrust later.

Where pdpspectra fits#

Our architecture practice works with engineering leadership on management practice. 1:1 quality is one of several engineering-management capabilities we help develop.

Related reading: the engineering hiring distributed scale post, the career ladders post, and the quarterly engineering reviews post.

---

Senior IC 1:1s reward deliberate design. Talk to our team about your engineering operating model.