TOPIC
Communication
These are the same questions found in the library, grouped here by the capability each one mainly examines.
204 questions
Questions 1–50 of 204 on this page.
A · Professional problem solving and implementation1
No questions in this section match your target. ·
B · Business understanding and domain modeling3
- When you explain a business, how do you first lay out the whole and then the position and value of the part you own within it? How does someone without a whole-picture view tell it, and what is the difference?
- A producer plans to rename a field and change an enum’s meaning, while a dozen teams depend on the current schema. How would you manage the change?
- Write a one-page product overview for someone who just joined. How would you mark which statements are fact, which are inference, and which are simply unanswered questions?
No questions in this section match your target. ·
C · Value judgment and direction setting5
- In the past year, how much team capacity did you secure to address technical debt (accumulated maintenance and rework) or improve engineering infrastructure such as builds and releases? When these problems slow product work, how do you explain their impact and risk to business leaders and secure time to refactor?
- The boss or the business side squeezes the schedule and says "ship first, messy code is fine". As the owner, how do you respond? Which quality can give way and which cannot, and how do you make the concession open and time-limited rather than quietly becoming permanent debt?
- An improvement you made has no reliable numbers. What other evidence would you offer that it really improved something?
- Your quarterly plan leaves out several important items. How do you record them so that when someone wants to revisit one later, the discussion rests on the judgment rather than re-arguing how important it is?
- How do you confirm that your team's goals are consistent with the company's strategic goals? When they are not, do you adjust the team's goals or try to influence the goals above?
No questions in this section match your target. ·
D · Delivery and ongoing operations11
- The organization requires every project to use the same weekly reports, reviews, and approval gates; a small exploratory effort now spends more time reporting than executing. How would you design tiered governance without missing high-risk work?
- A new service launches on schedule, but the project team is moving to other goals; on-call ownership, documentation, cost monitoring, and follow-up improvements have no clear owners. How would you determine whether the project is ready to hand off?
- A release project has capacity, vendor-delivery, and data-quality risks, each below its individual escalation threshold, but all may converge in the same week. How would you assess the combined risk and decide what action to take?
- A business partner brings you a problem that is not clearly defined. What sources would you check, whom would you consult, and how would you separate confirmed facts from assumptions? How would you turn the findings into an actionable plan?
- Different teams provide conflicting data and explanations for the same business problem, while the project is already planned for this quarter. How would you decide what to investigate first and what to defer?
- A customer asks for “a real-time dashboard,” but their examples suggest they only discover inventory errors later in the day. How would you guide the discussion?
- A campaign goes live overnight, but heavy traffic stalls the system. Users cannot claim coupons and start complaining. As an engineer involved in the campaign, how would you coordinate with operations and support on temporary business measures while restoring the system?
- A production service suddenly fails widely. In what order do you act during the first hour?
- Sales, support, and engineering can all label customer issues top priority, so the queue cannot distinguish business outages from general dissatisfaction. How would you design severity and escalation?
- During an outage, engineering wants to disable a feature, business wants to keep accepting orders, and support has promised a recovery time. Responders receive conflicting directions. How would you organize the response?
- A strategic change requires you to shut down at once a business that brings many users but has lost money for years. How do you, in the shortest time, reassure thousands of affected partners, complete the wind-down compliantly and smoothly, and prevent a group public-relations crisis?
No questions in this section match your target. ·
E · Collaboration, communication, and influence13
- After you escalated a delivery risk, a colleague felt bypassed and stopped sharing information promptly. How would you repair the relationship while preserving necessary risk transparency?
- Two leads disagree on building platform capability first versus delivering a customer feature first. Meetings repeat the same arguments without new evidence. How would you establish a decision process and a deadline?
- In a cross-functional review, you notice the lead’s proposal omits a migration step that would change metric definitions. The meeting is ending and an external partner is present. How would you intervene and follow up?
- A colleague says you often overturn a plan late in discussion. You believe those instances followed newly discovered risks. How would you understand the feedback and decide whether to change your behavior?
- Several teams agree in a review to improve data quality, but two weeks later no one has taken the implementation work; each lead believes agreement itself completed the collaboration. How would you turn consensus into ownership and checkpoints?
- A project has borrowed an analyst from another team for two months, but the assignment has no clear end condition and the original team’s ongoing work is backing up. How would you negotiate scope, review timing, and return conditions?
- Teams across three time zones rely on asynchronous reviews, but critical feedback often arrives after implementation is complete. How would you locate where the delay occurs and adjust information and decision cadence?
- A project sponsor changes success from launch, to adoption, to cost reduction, affecting different teams each time. How would you make changes explicit and protect teams from repeated rework?
- A cross-time-zone team relies on chat history for handoffs, and recipients repeatedly misunderstand status and open decisions. How would you shape handoff information and verify understanding?
- Product considers the risk acceptable, while security wants a delay; each cites different impact scenarios. How would you clarify facts, decision rights, and executable options?
- The upstream team wants rapid API changes while downstream teams need long compatibility and have no spare capacity. How would you negotiate versions, ownership, and cost?
- Several teams use a metric with the same name to make opposing decisions, but you cannot mandate a definition. How would you build an influence path?
- The vendor contract promises average availability, while the business cares about data recovery and incident notification. How would you align internal stakeholders to drive change?
No questions in this section match your target. ·
F · People and organization building4
- The team must fill an on-call lead role within a month. A candidate is technically strong but has no incident-command experience. How would you decide which capabilities can be developed on the job and which evidence is essential before appointment?
- Two frontline managers delivered planned results. One reports a stable team; another says key contributors have worked repeated overtime and may leave. How would you verify and help them address it rather than simply choose whom to believe?
- A key contributor says they will leave unless they receive a large raise this quarter, but compensation cycles and budget are already fixed. How would you understand their main concern, explain constraints, and discuss realistic paths?
- A team shifts from serving one product to supporting six business teams. Technical work has not grown much, but requests, priority conflicts, and feedback channels have multiplied. How would you decide whether to change the organization or first change the operating model?
No questions in this section match your target. ·
G · Learning, adaptation, and sustained growth1
H · Professional responsibility and work style12
- You are writing the summary of a high-impact project, but its result came from several teams and a key decision was not yours. How would you represent your contribution, others’ contributions, and the responsibility you carried?
- You discover that last week’s configuration change made part of a report inaccurate. Worried about appearing unreliable, you tried to correct it alone first; the impact is still unknown. What would you do now?
- You deliver an interface on schedule, but the downstream team has not integrated it and the business workflow still cannot be used. Your contractual task boundary is complete. How would you decide what responsibility to take next and communicate it?
- Your quarterly outcome has not definitively failed, but new validation has sharply reduced the chance of meeting it on time. You worry early reporting will look like weak execution. How would you communicate and organize next steps?
- A critical data migration has no owner, and each team says it is outside its scope. How would you make sure the migration is completed safely while naming the final owner and ongoing responsibilities?
- A project falls short of its commitment, partly because of external dependencies and untested assumptions. How would you distinguish your responsibility, external factors, and corrective actions? If a dependency team refuses to address a gap, how would you assign ownership and escalate?
- You realize your status report omitted a risk that could change the decision, and executives have already relied on it. How would you correct it?
- A leader asks you to show only favorable segments and describe an insignificant result as a trend. How would you respond and preserve factual accuracy?
- You notice another team’s operation may expose user data; they have not invited you, and release is imminent. How would you decide whether and how to intervene?
- The technical decision authority and growth scope discussed during hiring differ substantially from the actual role. How would you establish facts, negotiate, and decide whether to stay?
- The team routinely relies on night-time responses for long-running emergencies, conflicting with your sustainability boundary. How would you raise the issue and seek a workable arrangement?
- You are asked to commit to a delivery date before dependencies and risks are confirmed, with unclear authority. How would you communicate without making a false commitment?
No questions in this section match your target. ·