Template Overview

Appointing a Chief Technology Officer is among the most consequential executive decisions a company undertakes. The CTO Executive Interview Evaluation template structures rigorous panel assessments across systems vision, R&D budget stewardship, high-retention culture creation, and executive board alignment in plain Markdown.

Markdown Template Structure

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

---
title: "CTO Executive Evaluation: [[Candidate Name]]"
date: [YYYY-MM-DD]
panel_lead: "[[CEO / Lead Independent Director]]"
candidate: "[[Candidate Name]]"
current_title: "[[Current VP Engineering / CTO]]"
interview_stage: "Final Executive Panel & Board Review"
overall_recommendation: "[Strong Hire / Hire / Re-Evaluate / No Hire]"
tags: [hiring, executive-search, cto, leadership, evaluation]
---

# Chief Technology Officer Executive Evaluation — [[Candidate Name]]

## 1. Executive Competency Rubric
| Evaluation Dimension | Weight | Observed Score (1-5) | Key Candidate Evidence |
|---|---|---|---|
| **Architectural Vision & Moats** | 25% | [Score] | Demonstrated depth in local-first systems & neural efficiency |
| **Capital Allocation & Economics** | 25% | [Score] | Managed $25M+ R&D budget; optimized cloud compute margins |
| **Organizational Scaling & Talent**| 25% | [Score] | Scaled engineering from 40 to 220 while maintaining culture |
| **Executive Board Presence** | 25% | [Score] | Articulated complex technical risk to non-technical directors |

## 2. In-Depth Scenario Inquiries & Responses
- **Managing Technical Debt vs Product Velocity:**
  - *Candidate Stance:* How the candidate balances foundational re-platforming with commercial product deadlines.
- **Crisis Response & System Availability:**
  - *Observed Philosophy:* Track record during Sev-0 outages and major infrastructure failures.

## 3. Cultural Alignment & Leadership Presence
- **Engineering Philosophy:** Alignment with blameless accountability and sovereign, local-first computing.
- **Reference Checks:** Synthesis of confidential executive backdoor references.

## 4. Final Panel Recommendation & Compensation Framing
- **Consensus Verdict:** [Strong Hire / Hire / No Hire]
- **Target Compensation Package:** Base salary, equity allocation, and performance milestone framing.
- [ ] [[Panel Lead]] Convene formal board compensation committee review.

Filled Real-World Example

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

---
title: "CTO Executive Evaluation: Dr. Julian Thorne"
date: 2026-10-10
panel_lead: "[[Robert Sterling (CEO)]]"
candidate: "[[Dr. Julian Thorne]]"
current_title: "[[VP Infrastructure, Kite Networks]]"
interview_stage: "Final Board Panel"
overall_recommendation: "Strong Hire"
tags: [hiring, executive-search, cto, leadership, evaluation]
---

# CTO Executive Evaluation — Dr. Julian Thorne

## 1. Panel Findings
Robert Sterling and the executive committee evaluated Dr. Thorne. The panel commended Dr. Thorne's mastery of client-side compiler pipelines and proven ability to maintain 85% gross margins through on-device computing architectures.

## 2. Cultural Fit
Dr. Thorne demonstrated exceptional humility, deep empathy for developer tooling ergonomics, and complete philosophical alignment with our private Markdown vault architecture.

## 3. Recommendation
Unanimous recommendation to extend formal offer for the CTO position.

When to Use and When to Avoid

When to Use

  • Use during final-stage executive interview panels for CTO, VP Engineering, or Head of Research candidates.
  • Use to calibrate feedback across CEO, board directors, and technical fellows.
  • Use to maintain a confidential record of executive candidate evaluations.

When to Avoid

  • Avoid for junior or mid-level software engineering interviews.
  • Avoid for non-technical executive roles.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Summarize the CTO executive interview panel discussion:
1. Extract candidate evaluations across architectural vision, capital allocation, and team scaling.
2. Outline specific candidate examples provided regarding technical debt and engineering leadership.
3. Record final panel scoring, hiring recommendations, and agreed compensation guidance.
Output in clean, structured Markdown.

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

Frequently Asked Questions

What core competencies does this CTO evaluation template cover?

It assesses architectural vision, engineering capital allocation, executive presence, organizational scaling, and technological moat defense.

Why is local Markdown critical for executive hiring evaluations?

Candidate evaluations at the C-suite level involve extreme market sensitivity. Storing notes locally prevents premature leaks and protects candidate confidentiality.

How does Oyma support executive search panels?

Oyma transcribes panel interviews on-device with zero cloud exposure, synthesizing candidate responses without external API calls.