💬

Communication, Influence & Collaboration Topics

Communication skills, stakeholder management, negotiation, and influence. Covers cross-functional collaboration, conflict resolution, and persuasion.

Clear Written and Verbal Communication

The foundational skill of expressing ideas clearly, concisely, and accurately in both speech and writing. Covers structuring a message for the audience, avoiding jargon and ambiguity, and confirming shared understanding. This is the general-purpose communication competency that most interviews probe before diving into role-specific scenarios.

26 questions

Presentation and Storytelling

Constructing and delivering a persuasive, audience-tailored narrative for a presentation, live demo, or technical or design review. This is a construction-and-delivery skill: draft the outline, script, or pitch for an upcoming or hypothetical talk, defend it under live questions, or walk through a demo, rather than narrate a specific story from the candidate's own completed past work (STAR-style behavioral storytelling is covered elsewhere). Covers structuring a narrative arc (problem framing, evidence, so-what, ask), tailoring the same core message and level of detail across different audiences in the room, opening hooks and scene-setting anecdotes, choosing and framing a slide or visual to support one point, pacing and time-boxing a talk or live demo, and handling live Q&A, pushback, or an on-the-spot failure. Distinct from deep translation of one specific dataset, metric, or model result for stakeholders, and from recounting a completed project's actual story after the fact.

95 questions

Communicating Data and Analytical Findings

Turning analysis, metrics, and model results into clear insights and recommendations for a decision-making audience. Covers framing the 'so what', choosing the right visualization, quantifying uncertainty, and avoiding misleading interpretations. Focused on the analyst-to-stakeholder handoff where numbers must drive action.

11 questions

Building Trust and Credibility

Establishing yourself as trustworthy and credible with teammates, stakeholders, and skeptical audiences. Covers earning trust through consistency and transparency, demonstrating expertise, communicating with conviction, and building credibility with both technical and non-technical audiences. Especially important when advice or research must be believed and acted on.

19 questions

Technical Writing and Documentation

The craft of producing durable, reference-quality written artifacts and keeping them accurate: READMEs and quick-start guides, design docs, RFCs and technical proposals, runbooks and deployment guides, model cards, datasheets and data dictionaries, bug reports and reproducible examples, postmortem write-ups, handoff documents, pull request descriptions, code comments, release notes, experiment reports, and knowledge-base articles. Covers structure and information design, writing for a specific audience and for future readers (including plain language and accessibility), templates and style standards, docs-as-code workflows with CI checks, testing of examples and snippets, documentation review and quality checks, versioning and freshness checks on the documents you own, keeping sensitive data out of docs, and measuring whether documentation works. Architecture decision records, API reference docs, PRDs and PR/FAQs, and live presentations are covered elsewhere.

21 questions

Explaining Technical Concepts to Non-Technical Audiences

Translating complex technical topics, trade-offs, and decisions into language that business stakeholders, customers, or leadership can act on. Covers choosing the right level of abstraction, using analogies and visuals, and connecting technical detail to business impact without oversimplifying. Central to any role that sits between deep technical work and a non-engineering audience.

17 questions

Structured Behavioral Storytelling

The craft of narrating a candidate's own past experience in a clear, structured way, typically using the STAR or STARR framework (Situation, Task, Action, Result, and optionally Reflection). This topic tests narration technique itself: selecting which real story to lead with and why, compressing or expanding the same story to fit a stated time limit (for example a 30-second elevator pitch versus a 3-minute panel answer), adapting the same story for a different audience (executive, technical peer, or interview panel), phrasing individual contribution clearly (avoiding 'we' when the interviewer wants 'I'), turning raw material such as a resume bullet or rough notes into a structured narrative, diagnosing what is wrong with a weak sample answer and rewriting it, staying structured when an interviewer interrupts or probes mid-story, and explaining, applying, or critiquing the STAR or STARR framework itself. It does not cover the underlying technical or interpersonal substance of the story being told (the specific incident, decision, or project); that substance belongs to role-specific topics on ownership, incident response, leadership, persuasion, or the relevant technical domain, even when a question happens to say 'use STAR format.' It also does not cover constructing or delivering a live presentation, demo, pitch deck, or business case for a hypothetical or forward-looking scenario aimed at an audience such as executives, customers, or cross-functional stakeholders; that belongs to presentation and storytelling topics. It does not cover the open-ended 'tell me about yourself' or resume-walkthrough genre; that belongs to career-narrative topics. It does not cover judging which achievement or project is impressive enough to belong in a portfolio, or quantifying the value of the achievement itself; that belongs to achievement-and-portfolio topics.

27 questions