Build Beyond Belief · Nathaniel Young
Free self-assessmentThe AI-Native Engineer Checklist
A 20-minute self-assessment for experienced engineers who want to know whether they are actually becoming AI-native or just using better autocomplete.
Score yourself honestly
For each section, give yourself a score from 0 to 3.
0 means you have not touched it. 1 means you have tried it. 2 means you use it sometimes. 3 means it is part of how you ship real work.
If you score 0 or 1 in two or more sections, you are probably still treating AI like a tool you visit instead of a workflow you own.
1. Tool fluency
Can you move between chat, repo-aware tools, IDE assistants, terminal workflows, docs, and code review without losing context?
- I know when to use chat versus IDE assistance
- I can give an AI tool the right project context safely
- I can ask for changes without accepting nonsense
- I know the limits of the tool I am using
2. Workflow fluency
Can you use AI across the full engineering loop, not just code completion?
- Planning and task breakdown
- Scaffolding and refactoring
- Debugging and root-cause analysis
- Tests, docs, release notes, and handoff
3. Production judgment
Can you keep senior-engineer standards while moving faster?
- I can identify failure modes in AI-generated work
- I can design checks, evals, or tests around risky outputs
- I understand cost, latency, privacy, and maintainability tradeoffs
- I do not ship code just because the model sounded confident
4. Career leverage
Can you turn AI fluency into visible value at work or in your portfolio?
- I have shipped a useful AI-assisted artifact I can explain
- I can show before and after impact
- I can teach the workflow to another engineer
- I have a clear story for why this makes me more valuable
5. 8-week project selection
Do you know what you would build first if you had focused support?
- The project is useful to my real work or career direction
- The scope is small enough to ship in 8 weeks
- The result can be demoed, measured, or explained
- The project teaches a reusable workflow, not just a one-off trick
What your score means
0 to 5: You are exposed. You may be aware of the tools, but they are not part of how you ship.
6 to 10: You are experimenting. The next step is turning scattered usage into a repeatable workflow.
11 to 15: You are adapting. You likely need a focused artifact that proves the skill publicly or internally.
16 to 20: You are becoming AI-native. The next step is scale, reliability, and teaching the workflow to others.
If this surfaced a gap, map it
The Refactor Assessment is a $500 diagnostic session where we turn this checklist into a concrete 8-week build plan.
You leave with an AI leverage map, three candidate projects ranked by value and feasibility, a tool stack recommendation, and the shortest useful path forward.
Send this to your inbox
You will get this checklist and a short weekly note on practical AI-native building. No fluff. Unsubscribe anytime.