Behavioral Interview Question Bank
200+ behavioral interview questions organized by 12 core competencies, complete with STAR framework templates, graded example answers, and interviewer scoring rubrics. Built for software engineers, engineering managers, and tech leads preparing for FAANG-level behavioral rounds.
Key Features
- 200+ curated questions across 12 competency categories
- STAR framework templates with fill-in-the-blank structure for every question
- 30 fully written example answers rated Good / Great / Outstanding
- Interviewer scoring rubric — understand how you're being evaluated
- Role-specific question sets for IC, tech lead, and manager tracks
- Red flag guide — common mistakes that tank behavioral rounds
Competency Categories
| Category | Questions | Difficulty |
|---|---|---|
| Leadership & Influence | 22 | ★★★ |
| Conflict Resolution | 18 | ★★★ |
| Project Management | 20 | ★★ |
| Technical Decision-Making | 16 | ★★★ |
| Cross-Team Collaboration | 15 | ★★ |
| Failure & Learning | 18 | ★★★ |
| Customer Obsession | 14 | ★★ |
| Innovation & Creativity | 12 | ★★ |
| Mentorship & Growth | 15 | ★★ |
| Ambiguity & Adaptability | 16 | ★★★ |
| Ownership & Accountability | 20 | ★★ |
| Communication | 14 | ★★ |
Sample Content
Example Question: Conflict Resolution
"Tell me about a time you disagreed with a senior engineer's technical decision."
STAR Template:
- Situation: We were building [project type] and the tech lead proposed [technology/approach]. I believed [alternative] was better because [reason].
- Task: I needed to [express my view / propose alternative / find compromise] without undermining the team lead's authority.
- Action: I [gathered data / built a prototype / scheduled a 1:1] to demonstrate my perspective. Specifically, I [concrete steps taken].
- Result: We ultimately [outcome]. The relationship [improved / stayed strong] and I learned [key takeaway]. Metrics: [quantifiable impact].
Example Answer (Rated: Great):
"On a data pipeline migration, the tech lead wanted to use a custom orchestration framework. I had experience with similar migrations and believed Apache Airflow would reduce our delivery timeline by 40%. Rather than debating in a group meeting, I scheduled a 1:1, built a small proof-of-concept over a weekend showing both approaches side-by-side, and presented the tradeoffs objectively. The tech lead appreciated the data-driven approach, and we agreed on Airflow with some custom operators. We delivered two weeks ahead of schedule, and the tech lead later told me he valued how I handled the disagreement."
Example Question: Failure & Learning
"Describe a project that failed. What was your role, and what did you learn?"
STAR Template:
- Situation: Our team was tasked with [project goal] on a [timeline]. I was the [role].
- Task: I was responsible for [your specific ownership area].
- Action: I [specific actions — what went wrong and what you did about it]. When we realized [the failure point], I [corrective action taken].
- Result: The project [outcome]. I learned [specific lesson]. Since then, I've [how you applied the lesson]. For example, [concrete change you made].
Example Answer (Rated: Outstanding):
"I led a migration from on-prem PostgreSQL to a managed cloud database. I underestimated the data volume and didn't run a full-scale dry run — just tested with 10% of data. On migration day, the job ran 8x longer than expected, causing 6 hours of downtime versus our planned 2-hour window. I immediately communicated to stakeholders, set up a status page, and parallelized the migration across 4 workers to recover. Afterward, I wrote a postmortem, established a 'full-scale rehearsal' requirement for all migrations, and created a runbook template the team still uses. The experience taught me that optimism isn't a strategy — testing at production scale is non-negotiable."
Red Flags to Avoid:
- Blaming others entirely
- Choosing a trivial "failure" (typo in an email)
- Not showing what you learned
- Being vague about your specific contribution
Example Question: Leadership & Influence
"Tell me about a time you had to lead without formal authority."
Sample Questions in This Category:
- How did you convince skeptical stakeholders to adopt a new technology?
- Describe a time you rallied a team during a crisis.
- Tell me about influencing a product decision as an engineer.
- How did you drive alignment across teams with competing priorities?
- Describe leading a cross-functional initiative.
Interviewer Scoring Rubric
DIMENSION POOR (1) GOOD (3) OUTSTANDING (5)
─────────────────────── ───────────────── ────────────────── ──────────────────
Situation clarity Vague, rambling Clear context Concise, relevant
Action specificity "We did..." "I specifically..." Detailed own actions
Result impact No metrics Some quantification Strong metrics + learning
Self-awareness Defensive Acknowledges gaps Proactive growth shown
Communication Disorganized Structured (STAR) Engaging, concise
Relevance to role Generic story Role-adjacent Directly applicable
The Story Matrix: Map Stories to Competencies
Leader Conflict Failure Technical Collab Ownership
Story 1 (DB
migration) ✓ ✓ ✓ ✓
Story 2 (Cross-
team API) ✓ ✓ ✓
Story 3 (Prod
incident) ✓ ✓ ✓
Story 4 (Mentor
junior eng) ✓ ✓
Goal: Cover all 12 competencies with 8-10 stories.
Each story should map to 3-4 competencies.
Study Plan
| Week | Focus | Daily Time |
|---|---|---|
| 1 | Draft 5 personal STAR stories covering top competencies | 45 min |
| 2 | Practice Leadership, Conflict, Failure categories aloud | 30 min |
| 3 | Practice Technical Decision-Making, Ownership | 30 min |
| 4 | Mock interviews — record yourself and review | 45 min |
Practice Tips
- Build a story bank first. Write down 8-10 strong stories from your career. Map each story to 3-4 different competencies.
- Use the 2-minute rule. Answers should be 90-120 seconds. Practice with a timer.
- Quantify everything. "Improved performance" → "Reduced p99 latency from 800ms to 120ms."
- Prepare a failure story you're proud of. The best failure stories show self-awareness and growth.
- Record yourself. Watch for filler words, rambling, and missing the "Result" section.
Contents
-
src/— Question bank organized by competency (Markdown + YAML) -
examples/— 30 fully written STAR answers with ratings -
docs/— Scoring rubrics and interviewer perspective guide
This is 1 of 11 resources in the Interview Prep Pro toolkit. Get the complete [Behavioral Interview Question Bank] with all files, templates, and documentation for $19.
Or grab the entire Interview Prep Pro bundle (11 products) for $199 — save 30%.
Top comments (0)