Template Overview

Progressing beyond Senior Engineer requires developing cross-organizational technical vision, sponsoring other engineers, and influencing business leadership. The Staff+ Engineering Growth Mentorship template provides a structured coaching framework for cultivating executive presence, strategic RFC leadership, and sustainable technical governance.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Staff+ Mentorship: [[Mentor Name]] & [[Mentee Name]]"
date: [YYYY-MM-DD]
mentor: "[[Principal Architect Name]]"
mentee: "[[Senior / Staff Engineer Name]]"
focus_area: "Organizational Influence & Architectural RFCs"
career_horizon: "[Staff / Senior Staff / Principal Target]"
tags: [mentorship, staff-plus, engineering-leadership, career-growth]
---

# Staff+ Engineering Growth Mentorship — [YYYY-MM-DD]

## 1. Strategic Focus & Leverage Assessment
- **Where are you spending your time?**
  - Coding & PR reviews vs System architecture vs Cross-team alignment.
  - Energy audit: Identifying high-leverage vs draining activities.
- **Current Architectural Sphere of Influence:** [Single Team / Department / Organization-Wide]

## 2. Technical RFC & Vision Scaffolding
- **Active Technical RFC:** Reviewing [[RFC Document Title]].
- **Stakeholder Alignment Strategy:** How to navigate skepticism from conflicting teams.
- **Anticipating Failure Modes:** Ensuring architectural proposals address operational maintainability and cost reality.

## 3. Sponsorship & Multiplier Effect
- **Who are you mentoring?** Active sponsorship of junior and mid-level engineers.
- **Setting Culture:** Promoting blameless incident culture and rigorous engineering documentation.

## 4. Growth Goals & Action Plan
- [ ] [[Mentee Name]] Refactor RFC executive summary to lead with business risk rather than syntax preferences.
- [ ] [[Mentee Name]] Present systems architecture teardown at the upcoming engineering all-hands.
- [ ] [[Mentor Name]] Provide feedback on draft promotion packet criteria.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Staff+ Mentorship: Elena Rostova & Tariq Mansoor"
date: 2026-10-10
mentor: "[[Dr. Elena Rostova]]"
mentee: "[[Tariq Mansoor]]"
focus_area: "Cross-Team Architectural Consensus"
career_horizon: "Senior Staff Promotion Target"
tags: [mentorship, staff-plus, engineering-leadership, career-growth]
---

# Staff+ Engineering Growth Mentorship — Elena & Tariq

## 1. Leverage Audit
Tariq noted that he is currently spending 40% of his week reviewing routine feature PRs. Elena recommended delegating routine review ownership to Senior engineers on the team to carve out 15 dedicated weekly hours for the Core ML quantization architecture roadmap.

## 2. RFC Sponsorship
Reviewed Tariq's draft for on-device logit biasing. Elena advised adding an explicit section comparing unified memory bandwidth consumption on 8 GB MacBook Air configurations to address product management concerns.

## 3. Action Items
- Tariq will revise the memory constraints section in [[RFC-402]] by Tuesday.
- Elena will sponsor Tariq's presentation to the Architecture Review Board next Thursday.

When to Use and When to Avoid

When to Use

  • Use during bi-weekly or monthly coaching sessions with Staff, Principal, and aspiring Senior engineers.
  • Use to scaffold architectural RFCs, cross-team consensus building, and technical vision documents.
  • Use to evaluate engineering leverage, delegation strategies, and promotion readiness.

When to Avoid

  • Avoid for routine sprint standups or bug fixing syncs.
  • Avoid for new-hire onboarding checklists.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Summarize the Staff+ engineering mentorship discussion:
1. Extract insights on engineering leverage, time allocation, and architectural scope.
2. Detail feedback provided on technical RFC proposals and stakeholder alignment strategies.
3. List explicit coaching commitments, writing assignments, and next milestones.
Output in clean, structured Markdown.

Your data remains securely on your Mac with zero cloud exposure.

Frequently Asked Questions

What differentiates Staff+ mentorship from standard engineering 1-on-1s?

Staff+ mentorship focuses on multi-team architectural strategy, organizational influence, executive communication, and setting company-wide technical standards.

How does local Markdown support long-term engineering career tracking?

Markdown notes link directly via wikilinks to RFC proposals, ADR architecture records, and promotion dossiers within your personal vault.

How does Oyma protect private career strategy discussions?

Oyma transcribes coaching sessions locally with on-device Whisper, ensuring sensitive promotion discussions remain private.