ROLE
Mobile
Compare expectations across career stages →
These are the same questions found in the library, grouped here by the capability each one mainly examines.
1143 questions
Extended questions 501–550 of 1143 on this page.
B · Business understanding and domain modeling28
- 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?
- 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?
- 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?
- 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 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?
- 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?
- 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?
- 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?
- 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 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?
- A user requests personal-data deletion, but the system uses append-only events, search indexes, and offline analytics copies; some events must remain for business audit. How would you distinguish deletable fields, identity mappings, cryptographic erasure, and retention exceptions?
- A click-through feature suggests low interest in an item, but it appeared briefly at the bottom of a page; the team still trains a recommender on clicks. How would you model exposure opportunity, position, visibility duration, and user action separately?
- The system changes its user key from email to an immutable ID, but mobile caches, partner callbacks, and historical exports still reference email. How would you design mappings, a dual-read period, privacy cleanup, and retirement of old references?
- A customer entity must be split into two real customers after an erroneous merge, while old orders, permissions, and metrics reference the original ID. How would you model the split, historical attribution, current-reference migration, and indeterminate records?
- Several teams define user-status events differently, and the platform plans to unify them; some consumers rely on special meanings in old fields and cannot migrate at once. How would you build compatibility adapters, parallel validation, and deprecation governance?
- A product changes permanently valid credits to monthly refreshes, but some older contracts promise permanent balances and users have accumulated unused credits. How would you version rules, balance lots, contract cutovers, and user explanations?
No questions in this section match your target. ·
C · Value judgment and direction setting22
- A mobile onboarding redesign helps more users complete setup on day one, but active retention drops two weeks later; the flow also requests more permissions. How would you judge whether short-term conversion masks lower long-term value or loss of trust?
- An AI assistant increases apparent task-completion rates, but users recheck every result and some errors cause downstream rework. How would you judge whether automation actually lowers total task cost?
- A new checkout flow omits a fee explanation and increases payment conversion, but refund questions and cancellations also rise. How would you decide whether short-term conversion is worth it and identify evidence that the design created an expectation gap?
- Analytics show target users skipping the product's main flow and using exports, spreadsheets, or manual coordination instead; the team believes this is a user-habit problem. How would you decide whether the product conflicts with real work practices?
- A new operations dashboard is visited often, but interviews show most people only take screenshots before reviews and do not adjust resources or actions. How would you decide whether it creates decision value or only serves a display need?
- A keyboard-navigation defect affects few users but prevents them from completing a critical task; a feature expected to add revenue is also waiting. How would you compare user harm, obligations, opportunity cost, and repair scope?
- A premium feature available only on mobile has few users, but they renew and show strong willingness to pay; continued support increases cross-platform differences and testing cost. How would you decide whether to expand, retain it as a premium capability, or stop investing?
- Two projects are both committed for this quarter and depend on the only expert familiar with a legacy system; splitting that person's time would slow both. How would you compare delay cost, alternatives, and investment in shared capability?
- The team can launch a limited but imperfect experiment this week, or wait three months for broader research before a large commitment; the latter may miss a key market window. How would you compare learning value, delay cost, and decision risk?
- A failure affects few requests but can cause unrecoverable data loss; a new feature is expected to add revenue but would delay reliability work. How would you compare probability, severity, detectability, and opportunity cost?
- Growth, Support, and Product each want a new home-page entry; each change helps one group but could make the core task harder for first-time users to find. How would you choose the entry priority and experiment sequence?
- A new market opportunity emerges mid-quarter and leadership wants an immediate pivot; customer promises, team goals, and partner schedules have already been published. How would you compare the opportunity window with the cost of breaking commitments and decide what to keep, reduce, or renegotiate?
- Several teams spend hours each month resolving deployment configuration problems; a platform change could remove repeated work but adds no immediate revenue, while product features have explicit revenue targets. How would you estimate attributable platform value and investment limits?
- A redesign improves average conversion but increases task failure for a constrained user group; expanding the sample requires more research time. How would you prioritize the risk and decide whether to pause rollout?
- Policy and procurement cycles in a new market are unclear, yet the company must set annual goals and budgets. How would you translate long-term direction into quarterly hypotheses, validation milestones, and triggers for adjusting the plan?
- The team plans to pilot a service in three cities, but supply quality, repeat use, and unit economics are unproven; sales materials already show a firm expansion timeline. How would you rewrite stage goals and external commitments?
- The same product has different technical debt, release cadence, and user behavior on iOS, Android, and web; the roadmap still schedules uniform feature milestones, leaving one platform early and another far behind. How would you plan across platforms and define consistency boundaries?
- The company sets an annual revenue target, while teams control only parts of product features, channels, or service capacity; quarter-end reviews often dispute attribution. How would you build a goal tree, dependencies, and team-controllable outcome measures?
- The roadmap lists many goals but no explicit exits; each new request is added on top, and commitments keep changing. How would you include stopped, deferred, and declined work in planning governance?
- The team releases monthly, and the business wants weekly releases, but automated testing, rollback, and monitoring are immature. How would you plan release capability without using deployment frequency as the only success measure?
- The team defines conversion as purchasers divided by visitors. After a redesign, visits fall while purchaser count stays roughly flat, so the rate rises. How would you decide whether the redesign improved the target user's purchase experience?
- Checkout, recommendations, and promotion teams run experiments at the same time and share traffic and revenue measures; results conflict and each team claims success. How would you identify interactions, interference, and resource conflicts?
No questions in this section match your target. ·