Behavioral / BQ Question Pack (Staff & Senior)

Recurring behavioral prompts across recent loops, especially at Staff level. LinkedIn's bar is explicit about *leadership narrative depth* — interviewers flag when a Staff candidate's stories sound like Senior-IC work. Bring two-to-three multi-quarter, cross-functional stories with quantified business impact for each top theme. Requirements Recurring prompt themes (every loop hits 2–3 of these): Unblocking yourself from the critical path — a story where you removed yourself as a bottleneck. Driving a quality improvement — concrete defect / latency / cost-reduction with numbers. Influencing a design decision without authority — cross-team negotiation, not "I told my team". Cross-team conflict — disagreement with another team's tech lead or PM; the resolution path. Tight deadline with prioritization trade-offs — what you de-scoped, what you cut, what shipped. Mentoring / growing others — an explicit Staff-bar signal. A project that failed or under-delivered — what you learned and the mechanism change you drove afterward. Status-quo improvement — something you changed about how the org operates (review process, code-quality tooling, on-call rotation, etc.). Vision / direction-setting — what you would build in this org's space. Notes Leveling rubric (from observed feedback): Staff narrative must center on mechanism change — a process, system, or pattern you introduced that persists. Single-project execution stories cap at Senior. Senior narrative is project-scoped — solid execution, cross-team collaboration, technical decision-making. IC4 / mid narrative is feature-scoped — your slice of a project plus a tight ownership story. Common downlevel mechanism: BQ feedback "below Staff bar on leadership narrative". The fix is to lead with the scope of influence and the persistent mechanism, not the technical depth of any one project. The behavioural rounds are not a checkbox exercise — interviewers probe (why did you choose X, what would you have done differently, who else did you talk to). Have 5–8 minutes of follow-up depth per story rather than one polished 90-second pitch. Preparation Map 2–3 stories per theme above; the same story can hit two themes if the depth is genuine. For each story, quantify business impact (latency saved, revenue, headcount unblocked, defect rate). For Staff candidates, drill the mechanism change angle — what changed in how the team operates after your project, not just what shipped. Pre-write a 90-second elevator version of each story, then practice the unstructured 5-minute Q&A. The host-manager / tech-experience round is graded for narrative fluency and project ownership — the same stories apply, but expect 10-minute walkthroughs rather than 2-minute summaries.