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 601–650 of 1313 on this page.
B · Business understanding and domain modeling50
- A user upgrades mid-cycle and later requests a refund. The contract requires a calculation based on remaining service time, while promotional discounts and taxes also affect settlement. How would you decompose the rules and make the amount calculation traceable?
- A campaign allows each user to claim a discount once, but under high concurrency a user submits from multiple devices and receives several entitlements. How would you map the eligibility rule to atomic reservation, issuance records, and failure compensation?
- A user clicks a campaign link on Monday and purchases on Tuesday, but the purchase event uploads on Friday because the client was offline. How would you define event time, arrival time, attribution windows, and backfill rules so results remain explainable?
- A database field has been replaced, but reports, exports, and external integrations still read it; deleting it directly could cause silent errors. How would you plan compatibility migration, consumer confirmation, and final removal?
- Marketplace order value is rising, but merchants receive lower settlement amounts; the gap may involve discount sponsors, refunds, platform fees, and settlement timing. How would you explain participant value, money flows, and operating constraints along the transaction chain?
- Sales reports growth by signed contract value, Finance tracks recognized revenue, and Operations schedules work by fulfilled orders; all three call their number “business scale.” How would you map the process and definitions so teams can make one decision together?
- Enterprise customers expect a weekday response, while individual users expect self-service at any time; the team plans to standardize one support workflow. How would you analyze customer needs, issue urgency, service commitments, and delivery costs?
- An enterprise customer uses one contract for several departments; employees may work across departments, and administrators may operate on behalf of multiple accounts. How would you distinguish organizations, contract accounts, individual identities, memberships, and authorization scope?
- A cross-team project launches on schedule, but user feedback, operating costs, and data corrections remain; the project team is about to disband. How would you model product, platform, operations, and project responsibilities after delivery?
- A product feature is configured by customer contract, adjusted by experiment group, and constrained by regional rules; analysts need to explain which combination shaped a user's experience. How would you model configuration sources, scope, effective time, and decision provenance?
- Customers pay by API usage, but usage events may be duplicated, arrive late, or be replayed at month-end; sent invoices can lead to disputes. How would you define billable units, deduplication keys, close windows, and corrections?
- A dashboard's total conversion rate cannot explain which customer segment or process step caused a change; teams want to drill down by channel, plan, and region, but dimensions have different grains. How would you define fact grain and valid aggregation rules?
- A promotion increases subscriptions, but many subscribers renew at a lower price and full-price renewal has not yet reached its observation window. How would you decompose acquisition, renewal, discount, and churn to judge long-term value?
- A user reports that a service was not fulfilled as promised. Logs show the product flow triggered, the supplier did not confirm, and Operations says the contract is unclear. How would you map the service commitment, ownership boundaries, and remediation path?
- The company shifts from acquiring new customers to increasing value from existing customers, but sales incentives, product roadmaps, and service capacity still reflect acquisition goals. How would you map the value chain and incentives to find misalignment?
- A plan includes entitlements, users can purchase add-on capacity or receive temporary campaign credits, and contract changes may require manual compensation. How would you distinguish entitlement definitions, granted balances, sources, expiry, and consumption records?
- A cross-team objective spans several projects, each with routine tasks, risks, and incidents; retrospectives struggle to trace which decisions and work drove an outcome. How would you model relationships among objectives, projects, work items, events, and evidence?
- Business users can edit rules ahead of time, schedule them after approval, and still have older versions referenced by some users and asynchronous jobs. How would you model draft, review, publication, effective time, and rollback?
- Order revenue is shared by a platform, provider, and channel partner. Weeks later, part of the order is refunded; one party has already settled and lacks sufficient balance. How would you express allocation rules, refund responsibility, recovery, and reconciliation state?
- A product offers one free trial, but users may register with another email, share a device with family, or qualify through a partner channel. How would you define the eligible party, exception sources, abuse boundaries, and appeals?
- Business reporting needs the duration of every state transition, while an operations page needs only the object's current state; a wide table overwrote history during updates. How would you separate event facts, snapshots, and current-state models?
- CRM, billing, and product logs use customer IDs, contract IDs, and anonymous device identifiers; analysts need one customer's lifecycle. How would you model identity mappings, confidence, temporal validity, and correction?
- Several teams maintain customer profiles. When data is wrong, no one knows which system is authoritative, and systems also write values back to one another. How would you define field ownership, source of truth, synchronization direction, and dispute handling?
- A device reports a cumulative counter, but the counter resets after device replacement or data correction; the data platform may also backfill historical events. How would you define deltas, reset markers, negative differences, and recomputation boundaries?
- A numeric feature value of zero may mean the user had no activity, missing may mean the device did not report, and unknown may mean computation is unfinished; the pipeline currently fills all three with zero. How would you define the semantics and downstream handling?
- A global product counts daily activity by calendar day, but product analytics, the warehouse, and model serving use user time, UTC, and server time respectively; results often differ near month-end. How would you define boundaries and versioned semantics?
- Billing changes from calendar-month pricing to service-day pricing, with the new rule applying only to new contracts; old contracts cross the release date, and support still needs to explain past invoices. How would you version rules, contract applicability, and invoice snapshots?
- Business categories may be added, merged, or renamed. Reports must reproduce the definition used at the time and compare results under the current definition. How would you preserve source categories, mapping versions, and report definitions?
- An event producer wants to change a field from a string to a structured object, but some consumers deploy slowly and others drop unknown fields when writing records back. How would you stage dual writes, version negotiation, migration, and retirement of the old format?
- A customer-ownership field in historical events is wrong and must be corrected in bulk to recompute downstream metrics; the same events may also trigger notifications and partner callbacks. How would you separate data recomputation from side-effect replay?
- Active users and revenue are growing, but human support hours, refunds, and infrastructure costs per user are rising faster. How would you use user segments, tasks, and service flows to assess the economic quality of growth?
- A service requires a user, platform, and partner to act in sequence. Each party measures its own SLA, yet users still wait repeatedly and resubmit information. How would you model the end-to-end journey, waiting ownership, and handoff costs?
- An accountant uses one identity to manage several legal entities, each with separate contracts, invoices, and approvers; some group reports allow cross-entity summaries. How would you model identity, membership, resource ownership, and cross-entity access?
- Several users file cases about one incident. Some can share a resolution, but each has different contract deadlines, communications, and compensation eligibility. How would you model the parent issue, linked cases, individual commitments, and closure criteria?
- Plans sold through different channels share a display name but have different features, quotas, and renewal terms; users may switch channels during an upgrade. How would you distinguish the catalog display, sellable offer, contract version, and effective entitlements?
- Customers can apply points to part of an amount and then use a cash coupon; points may be funded by the platform or a partner and some may need restoration after cancellation. How would you separate payment, discount, point liability, and refund rules?
- After a merchant updates a price, an item already in a cart may still show the old amount; a submitted but unpaid order may carry a different commitment. How would you define price locking, effective time, and user notice?
- An enterprise pays per active seat, but some employees share accounts across shifts while others have accounts they never use; the contract does not define “active.” How would you determine the billable entity, activity definition, and dispute evidence?
- Orders contain nested line items, shipping, and tax, while refunds may apply to only some items; joining order headers directly to lines doubles totals in existing reports. How would you model grain and aggregation semantics?
- Sales performance rolls up through a regional hierarchy. Midyear, a region is split; historical reports must remain unchanged, while future reports use the new hierarchy. How would you represent organization versions, effective time, and attribution?
- Some transaction details must be retained for years under policy, while product analytics wants to use them for user segmentation and experiments. How would you model purpose authorization, retention, and access views?
- A user's transaction enters a behavioral feature window, then is reversed days later due to refund or fraud review; downstream models and reports have already consumed the feature. How would you model reversal, window recomputation, and impact propagation?
- A team wants a ratio feature of completions divided by applications, but applications can be withdrawn, duplicated, or later invalidated beyond the observation window. How would you define numerator, denominator, maturity window, and recomputation semantics?
- New users have little behavioral history, and the feature pipeline fills missing values with a global average, making “not observed” indistinguishable from “average behavior.” How would you represent cold-start status and evidence boundaries?
- An online feature service can return its last computed value after a cache expires, but some predictions need the freshest feature while others tolerate brief staleness. How would you define freshness metadata, task constraints, and unavailable-value fallback?
- A new workflow requires every record to have an ownership field, but historical data lacks it and older clients still write records. How would you design backfill provenance, dual-read/write migration, validation gates, and retirement of old clients?
- The same service faces different supply capacity, tax rules, and fulfillment times across regions, but the sales page uses one promise; some orders require manual rescheduling. How would you describe the relationship among regional constraints, service capability, and customer expectations?
- The company invested in a shared release platform, but most teams still use custom scripts. The platform team believes its features are sufficient, while product teams worry about migration risk and schedule conflicts. How would you analyze platform value, adoption cost, and incentives?
- An employee creates a project space and later hands it to another owner; the department manager still approves its budget, while audit requires the original creator to remain visible. How would you separate resource ownership, operational responsibility, authorization, and historical attribution?
- An enterprise contract promises response and recovery times and grants service credits when breached; one incident affects several features and crosses a billing period. How would you define timing, impact scope, credit caps, and appeal evidence?
No questions in this section match your target. ·