Internship Conversion Evaluation
Structured end-of-internship evaluation rubric assessing project deliverables, growth velocity, and full-time return offers in Markdown.
Template Overview
Converting high-performing engineering interns into full-time employees is a critical talent pipeline for high-velocity teams. The Engineering Internship Conversion Evaluation template provides an equitable, standardized framework for evaluating intern capstone projects, code review quality, learning curves, and full-time return offer decisions 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: "Internship Conversion Review: [[Intern Name]]"
date: [YYYY-MM-DD]
manager: "[[Engineering Manager]]"
mentor: "[[Senior Engineer Mentor]]"
intern: "[[Intern Candidate Name]]"
university_grad_date: "[MM/YYYY]"
internship_term: "[Summer 2026 / 12-Week Term]"
conversion_recommendation: "[Extend Full-Time Offer / Re-Evaluate / No Return Offer]"
tags: [hiring, internship, conversion, early-career, evaluation]
---
# Engineering Internship Conversion Evaluation — [[Intern Name]]
## 1. Capstone Project Scope & Deliverables
- **Project Title:** [[Intern Capstone Project Name]]
- **Shipped Functionality:** Concrete deliverables merged to production (e.g., automated remark plugins, test pipelines).
- **Code Quality & PR Craftsmanship:** Adherence to repo conventions, unit testing rigor, and documentation.
## 2. Core Competency & Velocity Matrix
| Evaluation Criteria | Expected Intern Level | Observed Candidate Demonstration | Rating (1-5) |
|---|---|---|---|
| **Technical Independence** | Completes tasks with mentor guidance | Autonomously resolved AST node traversal bugs | [Score] |
| **Learning Velocity** | Absorbs feedback across code reviews | Refactored PRs quickly without repeated comments | [Score] |
| **Collaboration & Communication** | Engages actively in agile ceremonies | Proactively surfaced blockers during daily standups | [Score] |
| **Engineering Curiosity** | Understands broader systems context | Researched SQLite FTS5 tokenizers beyond project scope| [Score] |
## 3. Mentor & Peer Feedback Synthesis
- **Mentor Summary:** Strengths demonstrated and recommended areas for growth during the initial full-time year.
- **Team Collaboration:** Cultural integration and team dynamic contribution.
## 4. Conversion Decision & Offer Recommendation
- **Return Offer Decision:** [Approved Full-Time / Approved Second Internship / No Offer]
- **Target Role & Band:** Associate Software Engineer (L1 / L2).
- [ ] [[Engineering Manager]] Submit formal return offer paperwork to University Recruiting.
Filled Real-World Example
Here is a realistic example demonstrating how this template captures actual deliberations:
---
title: "Internship Conversion: Maya Lin"
date: 2026-10-10
manager: "[[Devin Zhao]]"
mentor: "[[Liam O'Connor]]"
intern: "[[Maya Lin]]"
university_grad_date: "05/2027"
internship_term: "Summer 2026 (12 Weeks)"
conversion_recommendation: "Extend Full-Time Offer"
tags: [hiring, internship, conversion, early-career, evaluation]
---
# Engineering Internship Conversion Evaluation — Maya Lin
## 1. Project Impact
Maya successfully engineered the Markdown table column auto-formatting algorithm, shipping 18 merged pull requests with 98% test coverage.
## 2. Velocity & Independence
Liam O'Connor noted that by Week 6, Maya was operating with the independence of a mid-level engineer, proactively optimizing time complexity from O(N^2) to O(N log N).
## 3. Verdict
Unanimous recommendation to extend an Associate Software Engineer return offer upon university graduation.
When to Use and When to Avoid
When to Use
- Use at the conclusion of a summer or semester-long software engineering internship.
- Use to evaluate intern project deliverables, learning velocity, and team collaboration.
- Use to establish an equitable record for full-time return offer allocation.
When to Avoid
- Avoid for experienced Senior or Staff engineer hiring panels.
- Avoid for casual mid-term check-in chats.
On-Device AI Integration
Summarize your recording in Oyma with this local instruction:
Summarize the internship conversion evaluation meeting:
1. Outline intern capstone project deliverables, code quality assessments, and shipped features.
2. Group mentor feedback on technical independence, learning velocity, and team collaboration.
3. Record the final conversion decision, proposed full-time role level, and next steps.
Output in clean, structured Markdown.
Your data remains securely on your Mac with zero cloud exposure.
Frequently Asked Questions
What is the purpose of an internship conversion evaluation?
To determine whether an engineering intern has demonstrated the technical capability, velocity, and culture fit required for a full-time return offer.
How does local Markdown help manage intern performance reviews?
Markdown templates link directly to the intern's shipped PRs, project specs, and mentor evaluations within your vault, keeping reviews organized and private.
How does Oyma assist intern conversion debriefs?
Oyma transcribes mentor and manager conversion calls locally on your Mac, capturing objective feedback with zero cloud exposure.
Write internship conversion evaluation in plain Markdown.
Store notes in your local vault, transcribe meetings on-device, and retain 100% data sovereignty.