ROLE
General software engineering
Compare expectations across career stages →
These are the same questions found in the library, grouped here by the capability each one mainly examines.
1313 questions
Extended questions 1051–1100 of 1313 on this page.
A · Professional problem solving and implementation19
- Two currently valid policies in the knowledge base conflict, with similar retrieval scores. The assistant must not choose whichever is more convenient. What response and escalation path would you design?
- A new assistant improves satisfaction ratings, but task completion and repeat-contact rates remain unchanged. How would you determine whether this is a real improvement?
- Model responses may echo customer identifiers, while production debugging relies on request and response logs. How would you design collection, redaction, access, and retention?
- Users see response times double, but model inference time has barely changed. How would you break down the request-processing stages, locate the bottleneck, and limit impact?
- The team tunes prompts and model settings against the same fixed evaluation set every week. Scores rise, but new-user feedback does not improve. How would you restore evaluation trustworthiness?
- A model passes evaluations in a major market but behaves inconsistently in a new region because language, terminology, and service rules differ. How would you set rollout scope and follow-up gates?
- To reduce inference cost, the team caches answers by prompt text. User permissions, knowledge versions, and regional rules may differ. How would you define cache keys and invalidation?
- The evaluation set has grown, but many items are slight rewrites of one template, making model scores look stable. How would you audit sample quality?
- A natural-language request omits an amount limit and target account, while the agent can invoke a side-effecting tool. How would you decide whether to clarify, advise only, or require confirmation?
- A shared cache is read-heavy and the team plans to replace a mutex with a reader-writer lock. What evidence would you gather, and how would you judge whether the added complexity is worthwhile?
- A migration across millions of records cannot fit in one transaction. The business cannot expose a partially completed state. How would you design batched writes, visibility, and recovery?
- A service accumulates monetary values with floating-point numbers, and reconciliation drift grows over time. How would you identify the source and redesign calculations while migrating historical data?
- An operations table uses red, yellow, and green for risk. Some users cannot distinguish the colors, and screen readers announce only values. How would you redesign the information?
- A feature targets people who have never used the product, but all usability participants are core users. Which design decisions can the current evidence support?
- After submitting a form, users see “validation failed,” with no field identified and no entered data preserved. How would you redesign the error and recovery path?
- A desktop admin table has 14 columns, while mobile users need to handle exceptions in the field. How would you decide what to retain, hide, or move to details?
- A dashboard flags anomalies but shows no magnitude, baseline, or related events. Users export data to interpret it themselves. How would you improve diagnosis?
- Review feedback centers on “not premium enough” or “I dislike this color,” but the team has no shared user goal. How would you run the next review?
- Several product teams override shared component styles with CSS, causing frequent regressions after upgrades. How would you choose between adding configuration, splitting the component, or keeping exceptions?
No questions in this section match your target. ·
B · Business understanding and domain modeling4
- Revenue was recognized for an order last month, and a partial refund occurs this month. Finance and growth disagree on order count, net revenue, and refund-month treatment. How would you establish consistent data semantics?
- A service rebuilds state from an event log, but the live snapshot differs and responders cannot tell which to repair. How would you define authority and the repair process?
- A promotion starts at local midnight, services run in UTC, and customers may move regions. How would you represent effective time and handle boundary invoices?
- After a feature definition is fixed, the modeling team wants a historical backfill. Training reproducibility requires the original version, while business reports want corrected values. How would you design both views?
No questions in this section match your target. ·
C · Value judgment and direction setting1
No questions in this section match your target. ·
D · Delivery and ongoing operations13
- A project is nearly complete, but the business sponsor has left and the receiving team has no clear owner. How would you handle acceptance, handoff, and unresolved risk?
- The team has been interrupted by unplanned support work for three quarters and commitment completion has fallen. Leadership wants everyone fully booked to raise utilization. How would you propose a more reliable plan?
- An outage did not meet the threshold for a major customer incident, but affected a small group and exposed process gaps. How would you decide whether and how much to publish?
- Three projects need an integration environment that cannot be shared concurrently. Release dates are close and they depend on the same test team. How would you set scheduling rules and contingencies?
- The team believes rework is excessive, but some count bug fixes, others requirement changes, and others code rewrites. How would you define the problem and set an improvement target?
- The same remediation command has different effects in two regions, but the runbook describes only the default topology. Responders may use it in the wrong environment. How would you revise and prevent recurrence?
- Upstream events are delayed by hours, while downstream reports still show success and customers make incorrect decisions. How would you design freshness states and notifications?
- A vendor’s committed throughput is below peak-season forecast, and migration to an alternative takes two months. How would you plan capacity and business constraints?
- Disaster-recovery drills notify every team a week in advance, and special scripts make the exercise succeed while real recovery still fails. How would you redesign the drill?
- Scope is frozen and acceptance is underway when compliance identifies a new mandatory requirement. Releasing as planned creates audit risk. How would you respond?
- The monthly cloud bill is under budget, but cost per transaction keeps rising; temporarily lower volume hides efficiency regression. How would you govern cost?
- The business depends on a third-party API with no formal SLA and inconsistent support. How would you set internal continuity goals and fallback options?
- Leadership asks for higher engineering productivity next quarter without defining it. Some propose increasing commits; others want fewer meetings. How would you establish an improvement direction?
No questions in this section match your target. ·
E · Collaboration, communication, and influence2
- Project documents are fully accessible, but meetings repeatedly revisit decided options and newcomers do not know what can be reopened. How would you improve decision records?
- A dependency team verbally promises a quarterly interface but will not assign an owner, capacity, or milestones. Your project has already committed externally. How would you renegotiate?
No questions in this section match your target. ·
H · Professional responsibility and work style11
- You find a colleague omitted one class of refunds from business results already sent to leadership. They suggest quietly replacing the file. How would you ensure the conclusion and decision record are corrected?
- An access setting may have exposed some customers’ data to others, but scope is unconfirmed. Your manager worries early notice will cause alarm. How would you handle escalation and customer communication?
- You find a delay risk in a project you own, and your manager has been pleased with progress so far. When and how would you raise it?
- Your history includes a gap, a layoff, or a part that does not look good. How do you explain it truthfully, without avoiding it and without over-explaining?
- Your quarterly report says a target was met. You later discover that the data pipeline changed the definition of “active customer” midway through the period; recalculating with the old definition puts the result below target. How would you correct the report, inform decision-makers, and repair the process?
- Tell me about the piece of work you are proudest of. Why is it the best, what yardstick do you measure it by, and which parts were your own contribution?
- While reviewing a partner document, you find exposed customer credentials. This is outside your team’s remit, the owner is away, and the material may be public. How would you contain and hand off the risk?
- A critical delivery is falling behind on work owned by another team, so you step in and prevent a delay. This has happened three times, and people now assume you will handle it. How would you protect the current result while clarifying future owners and ways of working?
- Describe a project or module you owned that fell short of its commitment. How did dependencies and unvalidated assumptions affect the result, what was your responsibility, and how did you recover and improve your validation for next time?
- Tell me about a time you took on a challenge beyond your role. Why did you do it, how did you balance your regular work, and what were the result and the cost?
- Tell me about a time you noticed something that nobody owned but that affected the outcome. What did you do, and how did you define your own responsibility in it?
No questions in this section match your target. ·