skills/values-behavioral-interview/SKILL.md
Coaches behavioral and values-fit interview preparation with negative framing, deep follow-ups, introspection, and mission alignment. Use for culture-fit rounds, Anthropic behavioral prep, failure stories, and self-awareness drilling. Activate on "behavioral interview", "values interview", "culture fit", "tell me about a failure". NOT for coding interviews, system design, resume writing, or technical deep dives.
npx skillsauth add curiositech/windags-skills values-behavioral-interviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Preparation system for behavioral and values-fit interview rounds at mission-driven AI companies, with particular depth on Anthropic's approach. These rounds are NOT standard "tell me about a time" STAR interviews. They go deeper: negative framing, 5-6 layers of follow-up, genuine self-awareness testing, and mission alignment probing.
The core insight: interviewers are not listening to your story. They are listening to how you think about your story.
Use for:
NOT for:
senior-coding-interview)ml-system-design-interview)cv-creator)career-biographer)anthropic-technical-deep-dive)mindmap
root((Values Interview))
Failure & Learning
Project failures
Wrong decisions
Missed signals
Recovery process
Conflict & Disagreement
Manager disagreements
Peer conflicts
Technical debates
Escalation decisions
Mission & Motivation
Why this company
Why AI safety
Long-term vision
Personal connection
Self-Awareness & Growth
Blind spots
Feedback received
Changed opinions
Working style
Ethics & Trade-offs
Competing priorities
Uncomfortable decisions
Integrity tests
Gray areas
Ambiguity & Uncertainty
Incomplete information
Changing requirements
No right answer
Comfort with unknown
Every strong values interviewer drills past your prepared surface answer. Expect 5-6 levels of depth on a single story. If your preparation only covers levels 1-3, you will be exposed.
flowchart TD
S["Surface<br/><i>'Tell me about a failure'</i>"] --> C
C["Context<br/><i>'What was the situation exactly?'</i>"] --> D
D["Decision<br/><i>'What did you decide to do and why?'</i>"] --> T
T["Tradeoff<br/><i>'What did you sacrifice? What was the cost?'</i>"] --> M
M["Meta-Reflection<br/><i>'What did that teach you about yourself?'</i>"] --> W
W["Worldview<br/><i>'How did that change how you approach similar situations?'</i>"]
style S fill:#e8e8e8,stroke:#333,color:#000
style C fill:#d0d0d0,stroke:#333,color:#000
style D fill:#b8b8b8,stroke:#333,color:#000
style T fill:#a0a0a0,stroke:#333,color:#000
style M fill:#888888,stroke:#333,color:#fff
style W fill:#505050,stroke:#333,color:#fff
Preparation rule: For every story in your bank, you must have a prepared (but natural) answer at each level. If you can only get to level 3, the story is not ready.
| Level | What Interviewer Probes | What Strong Answers Include | |-------|------------------------|-----------------------------| | Surface | Can you identify a relevant experience? | Specific, time-bounded story with stakes | | Context | Do you understand the forces at play? | Multiple stakeholders, constraints, timeline pressure | | Decision | Did you act with agency? | Clear reasoning, alternatives considered, ownership | | Tradeoff | Do you acknowledge costs? | What was lost, who was affected, what you would do differently | | Meta-Reflection | Do you know yourself? | Genuine insight about a pattern, tendency, or blind spot | | Worldview | Has experience shaped your judgment? | A principle or heuristic you now carry forward |
Extend the standard STAR framework with Learning -- the layer that separates good answers from memorable ones.
| Component | Standard STAR | STAR-L Extension | |-----------|--------------|------------------| | Situation | What happened | Same, but include emotional state and stakes | | Task | What was your job | Same, but include why it mattered and to whom | | Action | What you did | Same, but include what you considered and rejected | | Result | What happened | Same, but include costs and unintended consequences | | Learning | (missing) | What changed in how you think, decide, or lead |
Situation: "In Q3 2024, our team shipped a recommendation model that
performed well in A/B tests but created filter bubbles we
didn't measure for..."
Task: "As the tech lead, I owned the decision to ship or revert,
with $2M/quarter in projected revenue on the line..."
Action: "I proposed a middle path -- keep the model but add diversity
constraints. My manager wanted to ship as-is. I escalated to
the VP with a one-page analysis of downstream risks..."
Result: "We shipped with constraints. Revenue impact was 60% of the
unconstrained model. My manager was frustrated for weeks.
The VP later cited it as the right call when a competitor
got press coverage for their filter bubble problem..."
Learning: "I learned that I default to quantitative arguments when the
real issue is values-based. The revenue comparison was a
crutch. The stronger argument was 'this is who we want to
be as a company.' I now lead with values framing when the
decision involves user welfare."
Build a bank of 8-12 stories that cover the full question category spread. Each story should be adaptable to multiple question types.
| # | Category | Example Prompt | What It Tests | |---|----------|---------------|---------------| | 1 | Genuine project failure | "Tell me about something that failed" | Accountability, learning from loss | | 2 | Manager/leadership disagreement | "When did you disagree with your boss?" | Courage, judgment, conflict style | | 3 | Changed a deeply held opinion | "When were you wrong about something important?" | Intellectual humility, growth | | 4 | Ethical trade-off | "When did you face a values conflict at work?" | Moral reasoning, integrity | | 5 | Mentorship through difficulty | "Tell me about helping someone through a hard time" | Empathy, patience, investment in others | | 6 | Operated in extreme ambiguity | "When did you have to act without enough information?" | Comfort with uncertainty, judgment | | 7 | Someone else was right, you were wrong | "When did a teammate's idea prove better than yours?" | Ego management, collaborative instinct | | 8 | Mission motivation | "Why do you want to work on AI safety?" | Authenticity, depth of conviction |
See references/story-bank-template.md for the full template with adaptation notes and follow-up preparation.
Values interviews at mission-driven companies deliberately use negative framing. They ask about failures, weaknesses, and conflicts -- not to trap you, but to see how you metabolize difficulty.
Direct negative: "Tell me about a time you failed." Inverted positive: "What's something you're still not great at?" Third-person probe: "What would your harshest critic say about you?" Counterfactual: "If you could redo one decision, which would it be?" Conflict escalation: "Tell me about a time you fundamentally disagreed with leadership."
The goal is prepared but genuine -- you have thought deeply about your stories, but you are not performing them.
Novice: Reframes every failure as a success. "My biggest weakness is that I care too much" or "The project failed but I was the one who caught it." Every negative story has an immediately positive outcome with no genuine discomfort. Expert: Names a real failure with real consequences, then describes the specific learning without minimizing the damage. Sits with the discomfort of the failure before moving to resolution. Example: "We lost the client. That was on me. It took me three months to understand why my instinct was wrong." Detection: Count the ratio of negative-to-positive beats. If every story follows the pattern [bad thing] -> [but actually good thing], the candidate has not done the real introspective work.
Novice: Stories sound scripted, hitting STAR beats mechanically. Same vocal energy for every question. Cannot deviate from the prepared narrative when asked an unexpected follow-up angle. "As I mentioned..." callbacks to previous structure. Expert: Has prepared structure but delivers with natural variation. Pauses to think when follow-ups go deeper than expected. Acknowledges when a question surfaces something they had not considered: "That's a good question -- I haven't thought about it from that angle." Detection: Ask a follow-up that is 90 degrees off their narrative. A rehearsed candidate will redirect back to their prepared story. A genuine candidate will engage with the new angle, even if it means admitting uncertainty.
Novice: Every story features them as the protagonist who saves the day, solves the problem, or has the critical insight. No story features them learning from a peer, being wrong, or changing their mind based on someone else's input. Expert: Credits others specifically ("Sarah's insight about the cache invalidation pattern was better than my original approach"). Describes collaborative problem-solving where the outcome was better because of multiple perspectives. Includes at least 2-3 stories where someone else was the hero. Detection: Map the character roles across all stories. If the candidate is always the protagonist and never the supporting character, learner, or person who was wrong -- the narrative is self-serving.
Anthropic's behavioral round has distinctive characteristics. See references/anthropic-values-research.md for detailed research.
| Dimension | FAANG Pattern | Anthropic Pattern | |-----------|--------------|-------------------| | Follow-up depth | 2-3 levels | 5-6 levels | | Framing | Balanced positive/negative | Deliberately negative | | What they evaluate | Leadership principles checklist | Genuine self-awareness | | Right answer | Demonstrated LP alignment | No single right answer; authenticity | | Ethics questions | Rare | Central | | "Why here?" weight | Moderate | Very high; mission alignment is load-bearing |
references/story-bank-template.md (8-12 stories)Use references/follow-up-drills.md for structured practice exercises:
Use interview-simulator skill for realistic mock rounds with evaluation.
| File | When to Consult |
|------|----------------|
| references/story-bank-template.md | Building or reviewing your bank of 8-12 career stories with STAR-L structure and adaptation notes |
| references/anthropic-values-research.md | Understanding Anthropic-specific values signals, culture, and what differentiates their behavioral round |
| references/follow-up-drills.md | Practicing deep follow-up handling with structured exercises; the 5 Whys, alternative path, critic, and values conflict drills |
This skill produces:
data-ai
license: Apache-2.0 NOT for unrelated tasks outside this domain.
development
Use when designing caching strategies (cache-aside, write-through, write-behind), implementing distributed locks, building rate limiters, leaderboards, real-time streams (XADD/consumer groups), pub/sub, or tuning eviction policies. Triggers: thundering-herd on cache miss, dogpile on key expiry, Redlock vs SET-NX-PX choice, sliding-window rate limiter, hot-key on a single cluster slot, big-key blowup, MULTI/EXEC across slots, KEYS in production. NOT for Redis Cluster operations/admin (different domain), embedded KV (SQLite, leveldb), in-process LRU caches, or Memcached.
tools
Drawing the `'use client'` boundary correctly in React Server Components apps (Next.js App Router, RSC frameworks) — leaf-pushing, slot composition, serialization rules, and environment poisoning prevention. Grounded in react.dev and Next.js 16 docs.
development
Use when designing rate limiting for an API, choosing between token bucket / sliding window / leaky bucket / fixed window, implementing it in Redis, deciding edge (Cloudflare/Upstash) vs origin enforcement, sizing per-user vs per-IP vs per-endpoint quotas, returning the right 429 response with Retry-After, or fixing the boundary-burst bug in fixed-window limiters. Triggers: 429 too many requests, INCR + EXPIRE, ZADD + ZREMRANGEBYSCORE + ZCARD, X-RateLimit-Remaining header, Cloudflare WAF rate limiting rules, Upstash @upstash/ratelimit, leaky bucket shaping vs policing, distributed rate limiter consistency. NOT for DDoS mitigation specifically (different scale), CAPTCHA / bot management, full WAF design, or per-user quota billing.