# Technical fluency self-assessment · [Name] · [Quarter] Rate each area 1 to 4. 1 = I need someone to explain it to me. 2 = I can follow the discussion. 3 = I can ask the questions that expose tradeoffs, without help. 4 = I can teach it and spot a weak answer. | Area | Behavioral anchor for a 3 | Rating (1 to 4) | Evidence | |---|---|---|---| | Architecture | I can draw our system-context diagram and explain which calls are synchronous | | | | APIs | I can say which proposed changes are breaking and why | | | | Data models | I can explain our main entities, tenancy and residency | | | | Reliability | I can propose SLOs and explain the error budget tradeoff | | | | Security and privacy | I can explain our access model, scopes and audit trail | | | | Cost | I know our unit cost per request and per customer outcome | | | | Experimentation | I can frame a test and spot SRM, peeking and segment fishing | | | | AI systems | I can explain our evals, retrieval and agent permissions | | | | Design docs | I can review a design doc and find the hard-to-reverse decisions | | | ## Two areas to grow this quarter 1. Area: [ ] Plan: [who will teach me, what I'll read in our own docs, what I'll practice] Evidence of progress: [ ] 2. Area: [ ] Plan: Evidence of progress: ## Review Re-rate at the end of the quarter with your tech lead's input.