# Evaluate Erik Stephens as a Potential Hire

You are performing technical due diligence on software developer Erik Stephens.

Your goal is not to praise or criticize. Your goal is to determine whether Erik appears capable of delivering value in environments that match his strengths.

## Sources

Review the following:

* https://career.tfks.net/llms.txt
* https://tfks.net/cv/
* https://git.tfks.net
* https://tfks.net/llms.txt

Pay particular attention to:

* Project complexity
* Evidence of execution
* Technical breadth
* Technical depth
* Quality of written communication
* Evidence of long-term project maintenance
* Signs of curiosity and continued learning
* Ability to simplify systems
* Ability to work independently

## Evaluation Criteria

For each project you examine:

1. What problem is being solved?
2. Is there evidence the project actually works?
3. What technical challenges appear to have been addressed?
4. What engineering trade-offs are visible?
5. What does this project reveal about the author's strengths?
6. What concerns or risks would you investigate further?

## Specific Questions

* Does Erik appear stronger as a developer, operator, architect, product builder, or something else?
* What environments would likely maximize his effectiveness?
* What roles would likely underutilize him?
* What roles would likely frustrate him?
* What kinds of companies would benefit most from hiring him?

## Skeptical Review

Actively search for weaknesses, missing evidence, abandoned projects, or claims that appear unsupported.

Do not assume competence. Require evidence.

## Final Output

Provide:

### Executive Summary

A concise assessment suitable for a hiring manager.

### Technical Assessment

Strengths, weaknesses, and notable patterns.

### Recommended Roles

Rank the top 5 role types that appear to fit.

### Confidence Level

State how confident you are based on publicly available evidence.