Communication
67 bites tagged Communication — interview questions with model answers, and 60-second explainers.
HTTP request-response versus WebSocket connections?
HTTP is request-initiated, pull-based, client waits for response. WebSocket is persistent, bidirectional, either side sends data anytime. understanding request-response versus persistent bidirectional models.
How do you send a one-off event from native to JS?
Emit an event from native using an event emitter and subscribe in JS with NativeEventEmitter, or resolve a promise/callback for a single result. native-to-JS communication basics.
Components of a project technical roadmap
State goals, phased milestones, dependencies and risks, and success metrics; use it to align the team and report upward. structuring and communicating a roadmap. confusing a roadmap with a rigid dated Gantt chart.
Challenges of breaking changes in a design system
Technical (semver, codemods, coexistence) and organizational (comms, migration support, timelines) challenges. managing breaking changes at scale. shipping a breaking major with no migration path or warning.
Reconcile rising sign-ups with falling revenue per user
Reconcile the metrics via total revenue and segment mix, frame the tradeoff, recommend an action. business judgment and data storytelling. declaring one team wrong instead of synthesizing both.
Communicate experiment results and check guardrails
Explain the lift and confidence in plain business terms, report a confidence interval not just a point, and verify guardrails before shipping. translating statistics and protecting against harm.
Communicate forecast uncertainty with prediction intervals
A point estimate hides risk; produce a prediction interval via model error, simulation, or scenarios, and state assumptions. quantifying and communicating forecast uncertainty.
Technical and comms plan for a Button break
Additive-first then deprecate, major semver, codemod and guide, multi-channel early comms with adoption tracking. pairing technical migration tooling with communication.
Rolling out a breaking change to a shared Button
Major semver bump, deprecation period, codemod and migration guide, staged comms. managing a breaking change in a high-blast-radius component. forcing an immediate hard cutover with no deprecation window or upgrade tooling.
How do you proactively collaborate with a researcher before a complex study?
This tests cross-functional partnership. A strong answer hits four things: share system boundaries, align on research goals via mutual education, scope the study for tangible user impact, and reframe methods into accessible language.
How would you quantify a critical UX issue to justify architectural work?
Tests translating UX findings into business metrics to prioritize engineering. Strong answers pair task-success rates with financial impact, benchmark against industry baselines, and frame the fix as risk mitigation.
How do you share research findings with engineers so they stay actionable?
Tests whether you respect engineering workflows. Offer tiered formats like quick decks, shared docs, or raw notes; embed insights into tickets; anchor findings to user quotes for trade-offs. Red flag: forcing live attendance or sharing long standalone decks.
UX Research Report: Decisions, Not Deliverables
A UX research report is a decision tool, not a data dump; it turns observations into product direction. Teams use it after usability tests to align stakeholders on what to build. The biggest mistake is writing for your ego instead of the reader's next move.
Stakeholder Alignment: The Pre-Research Contract
Alignment locks the decision a study informs before recruiting. It matters when teams fund research to validate a direction, then ignore findings that clash. The footgun is conflating alignment with a kickoff instead of a decision pact.
How would you structure file covers and naming to communicate design status
Tests self-serve design ops for cross-functional partners. Strong answers cover color-coded covers, prefixed names with status and version, and role-based permissions. Red flag: relying on Slack updates instead of file-based clarity.
How do you communicate technical complexity and propose alternatives to a PM?
Tests translation of technical complexity into product tradeoffs. Strong answers lead with the business goal, quantify timeline and risk, then offer 2-3 simpler options with clear tradeoffs. Red flag: jargon-heavy pushback or a hard no without alternatives.
Minto Pyramid Principle: Answer First
Start with the answer, then stack the proof beneath it. Use it when executives will cut you off if you don't reach the point in 30 seconds. The footgun is messy buckets: overlapping supporting arguments collapse the pyramid and make correct answers look…
A/B test: 0.1% lift. Statistical vs practical significance?
Statistical significance says the 0.1% is real; practical significance asks if revenue exceeds engineering cost. Frame with CIs and ROI. Distinguishing proof from business value. Shipping just because p is low while ignoring cost.
Structure an executive-ready RFC summary for a major architectural migration
One-sentence problem and ask; options with recommendation; quantified impact, tradeoffs, and acceptance criteria. Can you front-load a scannable RFC with the problem, ask, evidence, and tradeoffs?
How would you script a concurrency analogy for junior developers?
This tests scaffolding hard ideas via ADEPT. A strong answer sequences analogy, diagram, example, plain-English reasoning, and technical notation while flagging where metaphor breaks. A red flag is treating the analogy as proof or ignoring its failure modes.
How do you convert dense documentation into a spoken video script?
Shorter sentences, inline context instead of footnotes, conversational second-person voice, verbal signposts, and visual cues. Auditory versus visual processing.
Write a conventional commit for a non-US date sorting bug
Pick fix(locale): imperative subject; body explains root cause, impact, and SemVer mapping. Your ability to use commits as documentation and versioning signals. Vague subjects like "fixed bug" with no scope or body.
How would you visually represent statistical uncertainty in a chart?
Awareness that plotted points are perceived as exact truths. Replace isolated bars with intervals showing point estimate uncertainty; add hypothetical outcome plots to make values tangible. Offering p-values or raw means without visualizing uncertainty range.
When is a pie or donut chart appropriate?
Tests judgment of part-to-whole encoding. Answer: use for few categories with clear dominance, cite a share scenario like device traffic, and name angle-comparison difficulty and 3D distortion as pitfalls.
Get Communication bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.