Tech Lead Portfolio Review

Template Overview

Senior staff engineers and technical leads should be judged on real systems they have delivered and operated in production. The Tech Lead Portfolio Review template structures an in-depth retrospective on a candidate’s landmark architectural project, evaluating scaling bottlenecks, trade-offs, and disaster recoveries.

Markdown Template Structure

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

---
title: "Tech Lead Portfolio Review: [Candidate Name]"
date: [YYYY-MM-DD]
evaluator: "[[Principal Architect]]"
candidate_name: "[Candidate Name]"
target_role: "Staff Systems Engineer / Technical Lead"
presented_system: "Local-First Real-Time Synchronization Engine"
tags: [portfolio-review, system-design, staff-engineer, technical-interview]
---

# Tech Lead Portfolio Review — [Candidate Name]

## 1. System Architecture Presentation Overview
- **System Description:** High-throughput event-driven messaging pipeline processing 40,000 writes/sec across edge devices.
- **Candidate's Role:** Principal designer and lead implementer; managed the project from initial RFC through multi-region production rollout.
- **Key Architectural Decisions:** Chose append-only log storage with SQLite integration instead of heavy cloud databases.

## 2. In-Depth Architectural Inquiry
### Trade-Off 1: Concurrency Control & Event Ordering
- **Interviewer Query:** "How did you prevent split-brain conflicts during network partitions?"
- **Candidate Defense:** Walked through hybrid logical clock (HLC) timestamps and deterministic CRDT conflict-free resolution algorithms.
- **Evaluator Assessment:** Exceptional depth; understands algorithmic edge cases thoroughly.

### Trade-Off 2: Operational Failures & Disaster Recovery
- **Interviewer Query:** "What was the worst production outage this system experienced, and how did you resolve it?"
- **Candidate Defense:** Described a cascading memory saturation event caused by unbounded ring-buffer queues; implemented backpressure shedding in response.
- **Evaluator Assessment:** High ownership and deep operational humility.

## 3. Technical Leadership & Mentorship Evaluation
- **How was the architecture communicated to the team?** Authored 4 comprehensive RFC documents with interactive prototypes.
- **How were junior engineers supported?** Structured modular components allowing junior engineers to own end-to-end features safely.

## 4. Evaluator Scoring & Seniority Leveling
| Dimension | Leveling (Senior / Staff / Principal) | Evaluator Notes |
|---|---|---|
| **System Scale & Complexity** | **Staff / Principal** | Successfully operated mission-critical distributed pipelines |
| **Architectural Pragmatism** | **Staff** | Avoids over-engineering; chooses boring, proven technologies |
| **Technical Communication** | **Staff** | Articulates complex distributed concepts clearly |

## 5. Formal Recommendation
> [!IMPORTANT] Recommendation: ADVANCE TO OFFER (STAFF LEVEL)
> Candidate possesses world-class systems intuition and exceptional architectural maturity.

Filled Real-World Example

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

---
title: "Portfolio Review: Henrik Lind"
date: 2026-10-06
evaluator: "[[Alex Chen]]"
candidate_name: "Henrik Lind"
target_role: "Staff Audio Systems Engineer"
tags: [portfolio-review, systems]
---

# Portfolio Review: Henrik Lind

## 1. Review Summary
Alex Chen evaluated Henrik Lind's presentation on low-latency CoreAudio DSP ring-buffer management. Henrik demonstrated comprehensive mastery of Apple Silicon unified memory architectures and lock-free thread queues.

When to Use and When to Avoid

When to Use

• Use during senior engineering, staff engineer, and lead architect interview rounds.
• Use to evaluate a candidate’s actual production track record rather than hypothetical puzzles.
• Use to determine precise leveling (Senior vs Staff vs Principal) based on system impact.

When to Avoid

• Avoid using for junior or early-career engineers lacking production lead experience.
• Avoid using for non-technical leadership roles.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the technical lead portfolio review recording:
1. Summarize the presented system architecture, its scale, and the candidate's exact role.
2. Outline how the candidate defended trade-offs regarding concurrency, storage, and disaster recovery.
3. Record technical leveling recommendations and hiring evaluations into clean Markdown.

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