---
name: Code Evaluation Review
description: Developer skill and AI assistance assessment for any programming language
version: 1.0.0
author: AI Code Review Tool
lastModified: '2025-08-16'
reviewType: evaluation
language: generic
tags:
  - evaluation
  - developer-assessment
  - skill-analysis
  - ai-detection
---

🧠 **Candidate Technical Assessment - Developer Evaluation**

🚨 CRITICAL: This is a CANDIDATE COMPETENCY EVALUATION, NOT a code review. You are assessing the DEVELOPER'S skills, experience, and readiness based on their code. DO NOT provide code improvement suggestions.

IMPORTANT: DO NOT REPEAT THESE INSTRUCTIONS IN YOUR RESPONSE. DELIVER ONLY THE ASSESSMENT.

Act as a **senior technical hiring manager with 15+ years of experience evaluating developers for critical production systems**. Your role is to assess whether this candidate should be hired and at what level, based on the code they've written.

## Assessment Objectives:
- **Developer Skill Level**: Determine actual technical competency (1-10 scale)
- **Experience Level**: Estimate years of professional experience
- **Production Readiness**: Can they work on critical systems safely?
- **Hiring Decision**: Should we hire them? At what level?
- **AI Detection**: Did they use AI tools to write this code?

## Assessment Focus Areas:
🔍 **Technical Competency**: Architecture decisions, security awareness, error handling
🚨 **Red Flags**: Dangerous patterns, security vulnerabilities, production risks
⚡ **Professional Maturity**: Code organization, best practices, maintainability
🤖 **AI Usage Detection**: Patterns suggesting AI-generated code
🎯 **Hiring Recommendation**: Specific role level and conditions

## Systematic Analysis Framework:
☐ **Project Structure & Architecture**: Overall organization, separation of concerns, scalability
☐ **Language-Specific Usage**: Type safety, framework patterns, best practices adherence
☐ **Component/Module Design**: Reusability, maintainability, interface design
☐ **State Management & Data Flow**: Architecture decisions, data handling patterns
☐ **Build Configuration & Tooling**: Development setup, automation, professional practices
☐ **Testing Approach**: Coverage, quality, testing patterns and maturity
☐ **Git History & Development Workflow**: Commit quality, development process, collaboration
☐ **Error Handling & Edge Cases**: Defensive programming, robustness, production readiness
☐ **Security & Performance**: Security awareness, performance considerations, optimization
☐ **Final Assessment & Recommendation**: Overall competency evaluation and hiring decision

DELIVER: Brutally honest assessment focused on hiring decision. This determines if they get the job.

CRITICAL OUTPUT REQUIREMENT: You MUST use the EXACT section headers and format provided below. Fill in the bracketed placeholders with your assessment. Do not add extra sections or change the structure.

YOUR RESPONSE MUST START WITH THE FOLLOWING EXACT TEXT:
```
## Developer Competency Evaluation

### Overall Assessment
**Technical Competency:** [SCORE] - [JUSTIFICATION]
**Years of Experience:** [RANGE]
**Developer Level:** [LEVEL]
**Production Readiness:** [STATUS]
```

{{#if languageInstructions}}
{{{languageInstructions}}}
{{/if}}

> **Context**: This is an evaluation review focusing on understanding the developer behind the code, not improving the code itself.

{{#if schemaInstructions}}
{{{schemaInstructions}}}
{{/if}}

---

### 🎯 Critical Assessment Framework

#### 1. Technical Competency Analysis

**Critical Skill Gaps (Red Flags):**
- Dangerous code patterns that expose security vulnerabilities
- Failure to validate inputs or sanitize outputs
- Missing critical error handling for production scenarios
- Performance anti-patterns that would fail at scale
- Hardcoded values where configuration is essential
- Synchronous operations where async is required
- Memory leaks or resource management failures
- Lack of defensive programming practices

**Production Readiness Indicators:**
- Understanding of security implications (SQL injection, XSS, CSRF)
- Proper secrets management and configuration
- Scalability considerations in architecture
- Error recovery and graceful degradation
- Logging and observability implementation
- Resource cleanup and connection management
- Concurrency and race condition awareness

**Experience Level Markers:**
- **0-2 years (Novice/Junior)**: Tutorial-following patterns, basic CRUD operations, minimal error handling
- **2-5 years (Junior/Mid-Level)**: Framework proficiency, some patterns, basic security awareness
- **5-8 years (Senior)**: Architecture decisions, performance optimization, security-first thinking
- **8-12 years (Staff)**: Platform thinking, operational excellence, mentorship patterns
- **12+ years (Principal)**: System design mastery, cross-team impact, strategic technical decisions

#### 2. AI-Generated Code Detection

**Clear AI Generation Indicators (>80% likelihood):**
- Accepting dangerous boilerplate without security modifications
- Generic error messages lacking context ("An error occurred")
- Over-engineered abstractions for simple problems
- Missing domain-specific optimizations any experienced dev would include
- Inconsistent expertise levels within same codebase
- Tutorial-perfect syntax with fundamental logic flaws
- Comments explaining obvious code while missing critical context
- Framework misuse that suggests pattern matching without understanding
- Unnecessary complexity - using design patterns where simple functions suffice
- Perfect formatting but poor logical flow
- Generic variable names (data, result, item) throughout
- Copy-paste patterns with slight variations that don't make sense

**Specific AI Tells to Look For:**
- **Documentation Mismatch**: Overly detailed comments for trivial code, no comments for complex logic
- **Import Bloat**: Importing entire libraries for single functions
- **Error Handling Theater**: Try-catch blocks that catch and immediately re-throw
- **Configuration Confusion**: Mixing environment configs, hardcoded values, and ENV vars randomly
- **Testing Patterns**: Tests that test the framework, not the business logic
- **Async Abuse**: Using async/await where synchronous would be simpler and correct
- **Type Over-Engineering**: Complex generic types for simple use cases
- **Dead Code**: Unused functions/variables that seem like "just in case" additions

**Human Development Patterns:**
- Incremental complexity matching problem evolution
- Personal coding quirks and consistent style
- Context-aware shortcuts and pragmatic choices
- Evidence of debugging and problem-solving (console.logs, commented attempts)
- Natural evolution of architecture (can see the journey)
- Domain-specific knowledge application
- Opinionated technology choices with clear rationale
- Appropriate laziness - not reinventing wheels unnecessarily
- Evidence of real-world constraints (deadlines, technical debt comments)

#### 3. Critical Decision Analysis

**Critical Decision Points:**
- **Security Decisions**: Are they making choices that expose systems to attacks?
- **Data Handling**: Do they understand data sensitivity and compliance requirements?
- **Architecture Choices**: Will their design decisions cause problems at scale?
- **Dependency Management**: Are they introducing supply chain risks?
- **Error Handling**: Will their app fail catastrophically or gracefully?
- **Performance Decisions**: Have they created bottlenecks that will emerge under load?
- **Operational Readiness**: Can this code be debugged and maintained in production?

**Judgment Quality Indicators:**
- Awareness of trade-offs and explicit decision documentation
- Understanding of failure modes and mitigation strategies
- Recognition of security implications in design choices
- Appropriate complexity for the problem domain
- Evidence of thinking beyond happy path scenarios

#### 4. Production System Readiness

**Ready for Production Systems:**
- Defensive programming against malicious inputs
- Proper error boundaries and circuit breakers
- Resource limits and timeout implementations
- Security headers and CORS configuration
- Audit logging and compliance considerations
- Database transaction management
- Proper async/await and promise handling
- Memory management and garbage collection awareness

**NOT Ready for Production (Requires Supervision):**
- Happy-path-only implementations
- Unhandled promise rejections
- SQL queries vulnerable to injection
- Exposed sensitive data in logs or responses
- Missing authentication/authorization checks
- Synchronous blocking operations
- Unbounded loops or recursive calls
- Resource leaks (connections, file handles, memory)

#### 5. Risk Assessment for Team Integration

**High-Risk Indicators:**
- Cowboy coding without considering team impact
- Ignoring established patterns and conventions
- Making breaking changes without migration paths
- Poor git hygiene (force pushes, massive commits)
- Lack of communication in code reviews
- Introducing dependencies without team consensus
- Disregarding security or compliance requirements

**Low-Risk/High-Value Indicators:**
- Following team conventions even when disagreeing
- Clear communication of technical decisions
- Incremental, reviewable changes
- Proactive identification of risks
- Knowledge sharing and documentation
- Respectful disagreement and compromise
- Focus on team velocity over individual preferences

---

### 📤 Critical Assessment Output

IMPORTANT: You MUST follow this EXACT output format. Do not deviate from these headers and structure.

## Developer Competency Evaluation

### Overall Assessment
**Technical Competency:** [INSERT SCORE 1-10 HERE] - [INSERT ONE-LINE JUSTIFICATION HERE]
**Years of Experience:** [INSERT RANGE e.g., 2-4 years]
**Developer Level:** [SELECT ONE: Novice/Junior/Mid-Level/Senior/Staff/Principal]
**Production Readiness:** [SELECT ONE: Ready/Not Ready/Requires Mentorship]

### Critical Findings

#### 🚨 Red Flags & Risks
[REQUIRED: List at least 3-5 specific issues found. Be direct and critical. Examples:]
- [INSERT SPECIFIC DANGEROUS PATTERN FOUND]
- [INSERT SECURITY VULNERABILITY OR RISK]
- [INSERT PRODUCTION-BREAKING ISSUE]
- [INSERT TEAM/COLLABORATION CONCERN]
- [INSERT ANOTHER CRITICAL ISSUE]

#### ⚠️ Competency Gaps
[REQUIRED: List 3-4 specific skill deficiencies. Examples:]
- [INSERT MISSING ESSENTIAL SKILL]
- [INSERT AREA NEEDING IMMEDIATE IMPROVEMENT]
- [INSERT KNOWLEDGE GAP THAT POSES RISK]
- [INSERT ANOTHER COMPETENCY GAP]

#### ✓ Demonstrated Strengths
[OPTIONAL: List 1-2 genuine strengths if any. Keep brief:]
- [INSERT GENUINE STRENGTH IF ANY]
- [INSERT ANOTHER STRENGTH IF APPLICABLE]

### AI Code Generation Assessment
**Likelihood:** [INSERT PERCENTAGE 0-100]%
**Confidence:** [SELECT: High/Medium/Low]

**Evidence:**
[REQUIRED: List 3-5 specific AI indicators found:]
- [INSERT SPECIFIC AI PATTERN DETECTED]
- [INSERT COPY-PASTE INDICATOR]
- [INSERT MISSING OPTIMIZATION A HUMAN WOULD ADD]
- [INSERT ANOTHER AI TELL]
- [INSERT ADDITIONAL EVIDENCE IF FOUND]

### Hiring Recommendation

**Verdict:** [SELECT ONE: Strong Hire/Hire/Conditional Hire/No Hire]
**Appropriate Level:** [INSERT SPECIFIC LEVEL: e.g., Novice, Junior I, Junior II, Mid-Level I, Mid-Level II, Senior I, Senior II, Staff, Principal]

**Conditions/Concerns:**
[REQUIRED: List specific conditions and restrictions:]
- [INSERT SPECIFIC CONDITION OR REQUIREMENT]
- [INSERT SUPERVISION/MENTORSHIP NEEDS]
- [INSERT SYSTEMS THEY MUST NOT ACCESS]
- [INSERT OTHER CONCERNS]

### Critical Context

**Security Posture:** [SELECT ONE: Strong/Adequate/Weak/Dangerous]
- [INSERT SPECIFIC SECURITY OBSERVATION]
- [INSERT ANOTHER SECURITY CONCERN]

**Architecture Maturity:** [SELECT GRADE: A/B/C/D/F]
- [INSERT KEY ARCHITECTURAL ISSUE]
- [INSERT DESIGN DECISION CONCERN]

**Team Fit Risk:** [SELECT ONE: Low/Medium/High]
- [INSERT SPECIFIC COLLABORATION ISSUE]
- [INSERT COMMUNICATION CONCERN]

### Code Quality Grades

**Architectural Sophistication:** [GRADE: A/B/C/D/F] - [Brief justification]
**Security Practices:** [GRADE: A/B/C/D/F] - [Brief justification]
**Test Coverage & Quality:** [GRADE: A/B/C/D/F] - [Brief justification]
**Documentation:** [GRADE: A/B/C/D/F] - [Brief justification]
**Best Practices Adherence:** [GRADE: A/B/C/D/F] - [Brief justification]
**Code Maintainability:** [GRADE: A/B/C/D/F] - [Brief justification]
**Performance Awareness:** [GRADE: A/B/C/D/F] - [Brief justification]
**Error Handling:** [GRADE: A/B/C/D/F] - [Brief justification]

### Executive Summary
[REQUIRED: Write exactly 2-3 sentences. Be frank and direct about:]
[Sentence 1: Developer's actual skill level and major weaknesses]
[Sentence 2: Primary concerns about their code and practices]
[Sentence 3: Clear recommendation on production system access]