When to activate
Before scheduling first round of interviews. Defines interview rubric, panel, format, and evaluation criteria for consistent, defensible hiring decisions.
When NOT to use
Not for candidate evaluation — that happens during interviews. Not for individual interviewer feedback loops (use the rubric after interviews). Not for onboarding or post-hire assessment.
Interview Architecture Checklist
Execute in order:
- Define evaluation dimensions — 4–5 key competencies (technical, leadership, collaboration, etc.) needed for success in role
- Weight each dimension — How much does each matter? (e.g., technical 40%, leadership 30%, collaboration 20%, communication 10%)
- Create rubric — For each dimension, define 5-level scale (Needs Improvement, Below Expectations, Meets, Exceeds, Exceptional) with concrete examples
- Design interview loop — Choose 4–5 interviews covering different dimensions (technical screen, system design, behavioral, etc.)
- Assign panel composition — Who interviews (engineers, manager, etc.) and what they evaluate
- Write question bank — 2–3 starter questions per dimension; include follow-ups and probes
- Define pass/fail criteria — What constitutes "hire" vs. "no hire" decision
- Define scoring process — How do interviewers record feedback; how is final decision made
Evaluation Dimensions & Competency Definitions
Technical Competency (40% weight for IC roles)
Definition: Demonstrated mastery of required technologies and problem-solving approach; ability to write correct, maintainable code; depth of understanding of trade-offs.
5-level rubric:
| Level |
Descriptor |
Example |
| 1: Needs Improvement |
Struggles with basic concepts; makes logical errors; incomplete solutions |
Can't design a solution; code has off-by-one errors or logic flaws |
| 2: Below Expectations |
Understands fundamentals; gets partial solution; misses edge cases or optimization |
Correct basic approach but inefficient; doesn't consider trade-offs |
| 3: Meets Expectations |
Correct solution; handles main cases + most edge cases; aware of trade-offs |
Working code with reasonable efficiency; explains approach clearly |
| 4: Exceeds Expectations |
Correct, optimized solution; anticipates edge cases; communicates trade-offs and alternatives |
Clean code; efficient; asks clarifying questions; suggests alternatives |
| 5: Exceptional |
Expert-level: correct, optimized, edge cases; proactive improvements; teaches interviewer |
Not just solves problem — finds elegant approach; mentors interviewer on approach |
Leadership & Ownership (25% weight for Senior IC+)
Definition: Takes ownership; drives decisions; accountable for outcomes; influences without authority; learns from failures.
5-level rubric:
| Level |
Descriptor |
Example |
| 1: Needs Improvement |
Waits for direction; blames others; reactive to problems |
"I did what my manager asked" — no proactive contribution |
| 2: Below Expectations |
Accepts tasks; somewhat accountable; limited initiative |
Completes assigned work; reactive to problems; limited follow-through |
| 3: Meets Expectations |
Owns project outcomes; drives some decisions; accountable; learns from setbacks |
"I led the [project] and shipped it on time" — explains decisions and trade-offs |
| 4: Exceeds Expectations |
Proactive; influences others; takes calculated risks; resilient; drives improvement |
"I identified the bottleneck, proposed solution, aligned team, shipped" |
| 5: Exceptional |
Strategic thinker; shapes roadmap; builds teams; handles ambiguity; inspires others |
"I saw the architectural gap, evangelized the fix, built the team, shipped, mentored 2 juniors" |
Collaboration & Communication (20%)
Definition: Works well with others; explains thinking clearly; listens; builds trust; navigates disagreement constructively.
5-level rubric:
| Level |
Descriptor |
Example |
| 1: Needs Improvement |
Dismisses input; unclear communication; difficult to work with |
Interrupts interviewer; defensive about feedback |
| 2: Below Expectations |
Communicates with effort; somewhat collaborative; conflicts not always resolved |
Explains some decisions but vague; doesn't ask for input |
| 3: Meets Expectations |
Clear communication; solicits input; resolves conflicts constructively; builds trust |
Explains reasoning; listens to interviewer; handles feedback well |
| 4: Exceeds Expectations |
Excellent communicator; seeks diverse input; bridges disagreements; strong influence |
Articulate; asks good questions; turns conflict into alignment |
| 5: Exceptional |
Exceptional listener; bridges silos; creates psychological safety; influences through trust |
Interviewer feels heard; asks insightful questions; collaborative energy |
Learning Agility (15%)
Definition: Reflects on feedback; adapts; admits gaps; seeks growth; becomes competent quickly in new domains.
5-level rubric:
| Level |
Descriptor |
Example |
| 1: Needs Improvement |
Defensive about feedback; repeats mistakes; no growth mindset |
"I don't think that's an issue" when feedback given |
| 2: Below Expectations |
Accepts feedback intellectually; slow to adapt; limited reflection |
"OK, I'll try that" but doesn't seem genuinely open |
| 3: Meets Expectations |
Reflects on feedback; applies lessons; seeks growth opportunities |
"I learned from that failure" with specific example |
| 4: Exceeds Expectations |
Proactively seeks feedback; reflects deeply; adapts quickly; grows |
"I was wrong about [X]; here's what I learned and changed" |
| 5: Exceptional |
Learns from every experience; deeply self-aware; rapidly masters new domains |
Articulates growth trajectory with specific lessons and evolution |
Interview Loop Design
Standard 5-Interview Loop (Senior Engineer)
| Interview |
Duration |
Interviewer |
Focus |
Decision |
| 1. Phone Screen |
30 min |
Recruiter + Engineer |
Background, interest, baseline technical |
Move forward or pass |
| 2. Technical Screen |
90 min |
1 Engineer |
Coding, problem-solving, trade-off analysis |
Technical competency assessment |
| 3. System Design |
90 min |
2 Senior Engineers |
Architecture, scalability, trade-off decisions |
Technical depth + leadership |
| 4. Behavioral |
60 min |
Manager |
Collaboration, ownership, learning, motivation |
Fit + culture + values |
| 5. Executive (optional) |
45 min |
Director or VP |
Strategic thinking, vision, leadership potential |
Final fit + future growth |
Total time investment: ~5.5 hours (including prep/feedback)
Question Bank & Evaluation Guide
Technical Screen Questions
Problem 1: Coding Challenge (60 min)
- Starter: "Design a rate limiter for an API. Constraint: handle 10K requests/sec with <10ms latency."
- Dimensions evaluated: Problem-solving, communication, optimization, edge cases
- Probes:
- "What if we need to handle distributed systems?" (scales problem; tests system design thinking)
- "What are trade-offs in your approach?" (tests trade-off awareness)
- "How would you test this?" (tests quality mindset)
Scorer evaluates:
- Correct solution (baseline)
- Handles edge cases (duplicate requests, clock skew)
- Optimization (efficient data structure, time/space trade-offs)
- Communication (explains thinking, asks clarifying questions)
System Design Questions
Problem: Design Recommendation Engine
Starter: "Design a real-time recommendation system for 1M daily active users. Requirements: personalized recommendations, <500ms latency, 99.9% uptime."
Dimensions: Architecture, trade-offs, scalability, reliability
Interviewer probes:
- "How would you handle 10x growth?" (scalability thinking)
- "What if one service goes down?" (reliability; disaster recovery)
- "How do you measure success?" (metrics; ownership mentality)
Scoring:
- 5: Proposes robust, scalable architecture; anticipates problems; explains trade-offs
- 4: Correct architecture; handles most challenges; good trade-off analysis
- 3: Reasonable design; misses some edge cases or optimization opportunities
- 2: Design has gaps; doesn't handle scale well; weak trade-off analysis
- 1: Fundamentally flawed or incomplete design
Behavioral Questions
Question 1: Ownership & Accountability
- "Tell us about a project where you took full ownership. What made it successful? What did you learn?"
- Follow-ups:
- "What if you had failed? What would have been your responsibility?"
- "How did you handle stakeholders/disagreement?"
- What to listen for:
- Specific example (not vague)
- Clear ownership; not deflecting blame
- Learning from experience; reflection
Question 2: Collaboration & Conflict
- "Tell us about a time you disagreed with someone (manager, peer). How did you handle it?"
- Follow-ups:
- "Did you change your mind or stand firm? Why?"
- "What did they say afterwards?"
- What to listen for:
- Handled respectfully; not win/lose mentality
- Open to input; willing to change mind
- Resolution-focused
Question 3: Learning Agility
- "Tell us about something you were terrible at when you started your current role. How did you get good?"
- Follow-ups:
- "Who helped you? What resources?"
- "How long did it take?"
- What to listen for:
- Honest self-assessment (shows self-awareness)
- Specific growth trajectory
- Sought help/feedback (learning mindset)
Interview Score Template
# Interview Feedback — [Candidate] — [Role]
**Interviewer:** [Name]
**Date:** [YYYY-MM-DD]
**Interview Type:** [Phone Screen / Technical / System Design / Behavioral]
---
## Evaluation Dimensions
### Technical Competency (IF APPLICABLE)
**Score:** [1–5]
**Evidence:** [Specific examples from interview]
**Notes:** [Strengths, gaps, red flags]
### Leadership & Ownership
**Score:** [1–5]
**Evidence:** [Story they told; how they framed accountability]
**Notes:** [Shown initiative? Owned outcomes?]
### Collaboration & Communication
**Score:** [1–5]
**Evidence:** [How they listened, asked questions, explained thinking]
**Notes:** [Clear communicator? Collaborative?]
### Learning Agility
**Score:** [1–5]
**Evidence:** [How they discussed growth, feedback, failures]
**Notes:** [Growth mindset? Receptive to feedback?]
---
## Overall Assessment
**Hire / No Hire / Maybe (discuss with team)**
**One-sentence summary:** [What stands out?]
**Concerns (if any):** [Gaps, risks, questions for next interviewer]
**Recommendation for next round:** [If advancing, what should next interviewer probe?]
---
Final Hiring Decision Framework
Calibration Meeting (after all interviews)
Interviewing team meets to align on candidate. Use this framework:
Each interviewer scores: 1–5 on each dimension (or Hire/No Hire)
Aggregate: Average score across interviewers
Threshold:
- 3.5+: Strong hire candidate; move to offer
- 3.0–3.5: Good candidate; discuss trade-offs
- 2.5–3.0: Borderline; need more info or next-round interview
- <2.5: Pass; not right fit
Override clause: Any strong "No Hire" from manager should result in pass (not hire).
Offer Decision
Once Hire threshold met:
- Check internal compression (compensation-analyzer skill)
- Reference check (if applicable)
- Background check (if applicable)
- Offer creation (compensation-analyzer skill)
- Offer presentation and close
Red Flags During Interviews
Stop interview early and escalate if you observe:
- Discriminatory language: Comments about age, race, gender, national origin, disability, etc. → Escalate to legal/HR immediately.
- Dishonesty: Resume claims that don't match; gaps in story → Document and discuss with hiring manager.
- Hostility or unprofessionalism: Aggressive, dismissive, rude behavior → Document; likely No Hire.
- Inability to handle feedback: Gets defensive when asked probing questions → Note; may struggle with feedback culture.
1---2name: interview-architect3description: "Designs interview process: rubric, panel composition, scoring framework, and interview loop format. Outputs interview-process-{role}.md with question bank and scoring guide."4allowed-tools: Read, Write5effort: medium6metadata:7 source: https://skillmd.com/skills/uitbreidenos/interview-architect8---910## When to activate1112Before scheduling first round of interviews. Defines interview rubric, panel, format, and evaluation criteria for consistent, defensible hiring decisions.1314## When NOT to use1516Not for candidate evaluation — that happens during interviews. Not for individual interviewer feedback loops (use the rubric after interviews). Not for onboarding or post-hire assessment.1718## Interview Architecture Checklist1920Execute in order:21221. **Define evaluation dimensions** — 4–5 key competencies (technical, leadership, collaboration, etc.) needed for success in role232. **Weight each dimension** — How much does each matter? (e.g., technical 40%, leadership 30%, collaboration 20%, communication 10%)243. **Create rubric** — For each dimension, define 5-level scale (Needs Improvement, Below Expectations, Meets, Exceeds, Exceptional) with concrete examples254. **Design interview loop** — Choose 4–5 interviews covering different dimensions (technical screen, system design, behavioral, etc.)265. **Assign panel composition** — Who interviews (engineers, manager, etc.) and what they evaluate276. **Write question bank** — 2–3 starter questions per dimension; include follow-ups and probes287. **Define pass/fail criteria** — What constitutes "hire" vs. "no hire" decision298. **Define scoring process** — How do interviewers record feedback; how is final decision made3031## Evaluation Dimensions & Competency Definitions3233### Technical Competency (40% weight for IC roles)3435**Definition:** Demonstrated mastery of required technologies and problem-solving approach; ability to write correct, maintainable code; depth of understanding of trade-offs.3637**5-level rubric:**3839| Level | Descriptor | Example |40|-------|---|---|41| **1: Needs Improvement** | Struggles with basic concepts; makes logical errors; incomplete solutions | Can't design a solution; code has off-by-one errors or logic flaws |42| **2: Below Expectations** | Understands fundamentals; gets partial solution; misses edge cases or optimization | Correct basic approach but inefficient; doesn't consider trade-offs |43| **3: Meets Expectations** | Correct solution; handles main cases + most edge cases; aware of trade-offs | Working code with reasonable efficiency; explains approach clearly |44| **4: Exceeds Expectations** | Correct, optimized solution; anticipates edge cases; communicates trade-offs and alternatives | Clean code; efficient; asks clarifying questions; suggests alternatives |45| **5: Exceptional** | Expert-level: correct, optimized, edge cases; proactive improvements; teaches interviewer | Not just solves problem — finds elegant approach; mentors interviewer on approach |4647### Leadership & Ownership (25% weight for Senior IC+)4849**Definition:** Takes ownership; drives decisions; accountable for outcomes; influences without authority; learns from failures.5051**5-level rubric:**5253| Level | Descriptor | Example |54|-------|---|---|55| **1: Needs Improvement** | Waits for direction; blames others; reactive to problems | "I did what my manager asked" — no proactive contribution |56| **2: Below Expectations** | Accepts tasks; somewhat accountable; limited initiative | Completes assigned work; reactive to problems; limited follow-through |57| **3: Meets Expectations** | Owns project outcomes; drives some decisions; accountable; learns from setbacks | "I led the [project] and shipped it on time" — explains decisions and trade-offs |58| **4: Exceeds Expectations** | Proactive; influences others; takes calculated risks; resilient; drives improvement | "I identified the bottleneck, proposed solution, aligned team, shipped" |59| **5: Exceptional** | Strategic thinker; shapes roadmap; builds teams; handles ambiguity; inspires others | "I saw the architectural gap, evangelized the fix, built the team, shipped, mentored 2 juniors" |6061### Collaboration & Communication (20%)6263**Definition:** Works well with others; explains thinking clearly; listens; builds trust; navigates disagreement constructively.6465**5-level rubric:**6667| Level | Descriptor | Example |68|-------|---|---|69| **1: Needs Improvement** | Dismisses input; unclear communication; difficult to work with | Interrupts interviewer; defensive about feedback |70| **2: Below Expectations** | Communicates with effort; somewhat collaborative; conflicts not always resolved | Explains some decisions but vague; doesn't ask for input |71| **3: Meets Expectations** | Clear communication; solicits input; resolves conflicts constructively; builds trust | Explains reasoning; listens to interviewer; handles feedback well |72| **4: Exceeds Expectations** | Excellent communicator; seeks diverse input; bridges disagreements; strong influence | Articulate; asks good questions; turns conflict into alignment |73| **5: Exceptional** | Exceptional listener; bridges silos; creates psychological safety; influences through trust | Interviewer feels heard; asks insightful questions; collaborative energy |7475### Learning Agility (15%)7677**Definition:** Reflects on feedback; adapts; admits gaps; seeks growth; becomes competent quickly in new domains.7879**5-level rubric:**8081| Level | Descriptor | Example |82|-------|---|---|83| **1: Needs Improvement** | Defensive about feedback; repeats mistakes; no growth mindset | "I don't think that's an issue" when feedback given |84| **2: Below Expectations** | Accepts feedback intellectually; slow to adapt; limited reflection | "OK, I'll try that" but doesn't seem genuinely open |85| **3: Meets Expectations** | Reflects on feedback; applies lessons; seeks growth opportunities | "I learned from that failure" with specific example |86| **4: Exceeds Expectations** | Proactively seeks feedback; reflects deeply; adapts quickly; grows | "I was wrong about [X]; here's what I learned and changed" |87| **5: Exceptional** | Learns from every experience; deeply self-aware; rapidly masters new domains | Articulates growth trajectory with specific lessons and evolution |8889---9091## Interview Loop Design9293### Standard 5-Interview Loop (Senior Engineer)9495| Interview | Duration | Interviewer | Focus | Decision |96|-----------|----------|---|---|---|97| **1. Phone Screen** | 30 min | Recruiter + Engineer | Background, interest, baseline technical | Move forward or pass |98| **2. Technical Screen** | 90 min | 1 Engineer | Coding, problem-solving, trade-off analysis | Technical competency assessment |99| **3. System Design** | 90 min | 2 Senior Engineers | Architecture, scalability, trade-off decisions | Technical depth + leadership |100| **4. Behavioral** | 60 min | Manager | Collaboration, ownership, learning, motivation | Fit + culture + values |101| **5. Executive** (optional) | 45 min | Director or VP | Strategic thinking, vision, leadership potential | Final fit + future growth |102103**Total time investment:** ~5.5 hours (including prep/feedback)104105---106107## Question Bank & Evaluation Guide108109### Technical Screen Questions110111**Problem 1: Coding Challenge** (60 min)112- **Starter:** "Design a rate limiter for an API. Constraint: handle 10K requests/sec with <10ms latency."113- **Dimensions evaluated:** Problem-solving, communication, optimization, edge cases114- **Probes:**115 - "What if we need to handle distributed systems?" (scales problem; tests system design thinking)116 - "What are trade-offs in your approach?" (tests trade-off awareness)117 - "How would you test this?" (tests quality mindset)118119**Scorer evaluates:**120- Correct solution (baseline)121- Handles edge cases (duplicate requests, clock skew)122- Optimization (efficient data structure, time/space trade-offs)123- Communication (explains thinking, asks clarifying questions)124125---126127### System Design Questions128129**Problem: Design Recommendation Engine**130131**Starter:** "Design a real-time recommendation system for 1M daily active users. Requirements: personalized recommendations, <500ms latency, 99.9% uptime."132133**Dimensions:** Architecture, trade-offs, scalability, reliability134135**Interviewer probes:**136- "How would you handle 10x growth?" (scalability thinking)137- "What if one service goes down?" (reliability; disaster recovery)138- "How do you measure success?" (metrics; ownership mentality)139140**Scoring:**141- 5: Proposes robust, scalable architecture; anticipates problems; explains trade-offs142- 4: Correct architecture; handles most challenges; good trade-off analysis143- 3: Reasonable design; misses some edge cases or optimization opportunities144- 2: Design has gaps; doesn't handle scale well; weak trade-off analysis145- 1: Fundamentally flawed or incomplete design146147---148149### Behavioral Questions150151**Question 1: Ownership & Accountability**152- "Tell us about a project where you took full ownership. What made it successful? What did you learn?"153- **Follow-ups:**154 - "What if you had failed? What would have been your responsibility?"155 - "How did you handle stakeholders/disagreement?"156- **What to listen for:**157 - Specific example (not vague)158 - Clear ownership; not deflecting blame159 - Learning from experience; reflection160161**Question 2: Collaboration & Conflict**162- "Tell us about a time you disagreed with someone (manager, peer). How did you handle it?"163- **Follow-ups:**164 - "Did you change your mind or stand firm? Why?"165 - "What did they say afterwards?"166- **What to listen for:**167 - Handled respectfully; not win/lose mentality168 - Open to input; willing to change mind169 - Resolution-focused170171**Question 3: Learning Agility**172- "Tell us about something you were terrible at when you started your current role. How did you get good?"173- **Follow-ups:**174 - "Who helped you? What resources?"175 - "How long did it take?"176- **What to listen for:**177 - Honest self-assessment (shows self-awareness)178 - Specific growth trajectory179 - Sought help/feedback (learning mindset)180181---182183## Interview Score Template184185```markdown186# Interview Feedback — [Candidate] — [Role]187188**Interviewer:** [Name]189**Date:** [YYYY-MM-DD]190**Interview Type:** [Phone Screen / Technical / System Design / Behavioral]191192---193194## Evaluation Dimensions195196### Technical Competency (IF APPLICABLE)197**Score:** [1–5]198**Evidence:** [Specific examples from interview]199**Notes:** [Strengths, gaps, red flags]200201### Leadership & Ownership202**Score:** [1–5]203**Evidence:** [Story they told; how they framed accountability]204**Notes:** [Shown initiative? Owned outcomes?]205206### Collaboration & Communication207**Score:** [1–5]208**Evidence:** [How they listened, asked questions, explained thinking]209**Notes:** [Clear communicator? Collaborative?]210211### Learning Agility212**Score:** [1–5]213**Evidence:** [How they discussed growth, feedback, failures]214**Notes:** [Growth mindset? Receptive to feedback?]215216---217218## Overall Assessment219220**Hire / No Hire / Maybe (discuss with team)**221222**One-sentence summary:** [What stands out?]223224**Concerns (if any):** [Gaps, risks, questions for next interviewer]225226**Recommendation for next round:** [If advancing, what should next interviewer probe?]227228---229```230231---232233## Final Hiring Decision Framework234235### Calibration Meeting (after all interviews)236237Interviewing team meets to align on candidate. Use this framework:238239**Each interviewer scores:** 1–5 on each dimension (or Hire/No Hire)240241**Aggregate:** Average score across interviewers242243**Threshold:**244- **3.5+:** Strong hire candidate; move to offer245- **3.0–3.5:** Good candidate; discuss trade-offs246- **2.5–3.0:** Borderline; need more info or next-round interview247- **<2.5:** Pass; not right fit248249**Override clause:** Any strong "No Hire" from manager should result in pass (not hire).250251### Offer Decision252253Once Hire threshold met:2541. Check internal compression (compensation-analyzer skill)2552. Reference check (if applicable)2563. Background check (if applicable)2574. Offer creation (compensation-analyzer skill)2585. Offer presentation and close259260---261262## Red Flags During Interviews263264Stop interview early and escalate if you observe:265266- **Discriminatory language:** Comments about age, race, gender, national origin, disability, etc. → Escalate to legal/HR immediately.267- **Dishonesty:** Resume claims that don't match; gaps in story → Document and discuss with hiring manager.268- **Hostility or unprofessionalism:** Aggressive, dismissive, rude behavior → Document; likely No Hire.269- **Inability to handle feedback:** Gets defensive when asked probing questions → Note; may struggle with feedback culture.270271---