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 451–500 of 1143 on this page.
A · Professional problem solving and implementation35
- Given a set of records that may exceed memory capacity, process them in batches while allowing the caller to cancel. Describe or implement an interface that bounds memory, locates errors, and starts no new batch after cancellation.
- Several callers read a configuration file whose fields keep growing; older fields may be absent, and new versions must allow unknown extension fields. How would you design a parsing interface so callers can understand defaults, validation errors, and backward-compatibility behavior?
- Latency is normal after a release, but p99 rises gradually after several hours and temporarily recovers after a restart. CPU is steady while connection counts and heap memory slowly grow. How would you break down hypotheses and design low-risk tests?
- A feature works on the corporate network and most home networks, but requests often time out on a particular carrier or under poor connectivity; server error rates do not rise at the same time. How would you isolate causes across client, network path, protocol, and retry behavior?
- Users can edit a profile on a phone while offline and may also edit it on the web. The device must sync when connectivity returns without silently overwriting valuable changes. How would you design versioning, conflict detection, merging, and user confirmation?
- An entry service calls several downstream systems. One noncritical dependency occasionally slows down, exhausting request threads and affecting unrelated features. How would you design timeouts, concurrency isolation, degradation, and recovery?
- A shared library releases a backward-compatible version, but application repositories cannot upgrade promptly because of pinned dependencies, generated code, or different release windows; a security fix remains blocked. How would you design compatibility policy and the dependency-upgrade process?
- An AI assistant repeatedly calls search, databases, and external APIs for a small share of requests, making latency and cost far higher than average. How would you design per-task budgets, stop conditions, idempotency, and auditable execution records?
- During user interviews, people repeatedly suggest buttons, filters, and reminders but rarely describe their goals or blocked situations. How would you adjust question order and wording to distinguish real experiences, stated preferences, and proposed solutions?
- A core service remains within its monthly SLO, but its error budget is being consumed much faster and errors cluster around a recent feature release. How would you decide whether to pause rollout or roll back?
- A new model scores much better on an offline test set, but a small production rollout shows lower task completion for one user group and more complaints. How would you determine where the evaluation set, metrics, or release decision failed?
- An AI assistant retrieves documents from several business systems, where users have different permissions in each. How would you ensure retrieval, caching, summaries, and citations follow source permissions, including after access is revoked?
- A model service used by an AI feature has highly variable latency, causing user requests to exceed the end-to-end deadline. How would you allocate budgets across retrieval, model calls, and post-processing, and design fallbacks after a timeout?
- The same commit passes reliably on a developer's machine but occasionally fails in CI because of time zones, random ordering, shared caches, or parallel races. How would you classify, reproduce, and reduce this nondeterminism?
- A function appears read-only under multithreading, but a formatter it calls uses a shared internal buffer and occasionally mixes results. How would you distinguish thread safety, reentrancy, and statelessness, and decide where to fix the issue?
- The input contains time intervals that may overlap or touch, and callers need to find records covering a given instant. Describe or implement a merge and query strategy, including whether endpoints are inclusive.
- An API adds a new state, but older clients may not recognize it; some must still display the record, while critical operations must reject unknown states. How would you design parsing and defaults so an unknown value is not mistaken for a valid state?
- The client sees one submission, but the server occasionally creates two identical records. It usually happens after a timeout and retry, with no obvious log error. How would you reconstruct the request timeline and verify where duplication occurs?
- The default locale renders correctly, but a few buttons overflow and tables shift after switching languages; failures occur only on narrow screens with enlarged system text. How would you narrow the cause and build regression coverage?
- Fresh installations work, but users who upgraded across several versions report missing local drafts. The issue is hard to reproduce, and the server has no corresponding deletion record. How would you preserve evidence and investigate migrations, cache cleanup, and lifecycle callbacks?
- A mobile upload of a large file may be interrupted, and users may retry by tapping again; the system also bills successful processing. How would you design chunks, validation, resumable state, finalization, and the billing point?
- After a dependency slows down, several callers increase retries at the same time; traffic doubles and the outage spreads. How would you design retry budgets, backoff, jitter, and cross-service coordination?
- A feature is fully launched, but switches created years ago still control several code paths; the team does not know which flags can be removed and relies on memory during rollback. How would you establish flag lifecycles and cleanup ownership?
- A backend API generates TypeScript, Java, and Swift SDKs, but nullable types, enums, and error models are drifting across languages. How would you design the contract source, generation process, and cross-language compatibility tests?
- A production dependency has a different artifact hash from the build associated with its repository tag, and the team cannot confirm it passed the expected CI. How would you establish build traceability, artifact verification, and release authorization?
- New clients use a replacement API, but users upgrade slowly and older versions still account for meaningful traffic; continued support also constrains server evolution. How would you set a support window, capability detection, migration notices, and retirement criteria?
- A user submits a long AI analysis, closes the page, and later checks from another device; the task may call several tools and produce partial results. How would you design task state, cancellation, retry, and result visibility?
- A model begins returning structured JSON, while mobile, server, and analytics consumers upgrade at different rates; new fields may be absent or enum values may change. How would you define the output contract, handle validation failures, and preserve compatibility?
- An AI assistant reads user-uploaded documents that may tell it to ignore existing rules and call external tools. How would you distinguish data from instructions, constrain tool permissions, and verify the safeguards?
- A model has streamed partial output to a user when the connection drops or a safety check fails; the client may make the answer look complete. How would you design completion markers, withdrawal or explanatory notices, and retry behavior?
- Overall task success is unchanged after a model update, but outcomes diverge more across users by language, device, and experience. How would you define evaluation segments, manage small-sample risk, and decide whether to continue rollout?
- The team believes a new flow is simpler, but usability tests show only familiar users succeed; newcomers get stuck on permission explanations and next steps. How would you recruit, design tasks, and define observations to judge whether it is actually usable?
- Researchers can recruit only active users but need to understand why occasional or churned users leave. How would you identify sample bias, adjust recruitment, and limit the reach of conclusions?
- Users can upload archives for processing, and a past incident showed that malicious files could exhaust resources or access paths without authorization. How would you design isolation, extraction limits, content checks, and safe failure behavior?
- The team needs real user conversations to reproduce model failures, but logs contain personal and sensitive business content. How would you minimize collection, redact data, authorize access, and set retention while preserving debugging value?
No questions in this section match your target. ·
B · Business understanding and domain modeling12
- Marketplace transactions keep growing, but buyers wait longer, sellers cancel more often, and subsidy spending rises. How would you describe the exchange of value and constraints across participants, then decide whether growth reflects better matching or one-sided subsidy?
- An order moves through created, awaiting confirmation, processing, partially fulfilled, canceled, and refunded states; different pages and services interpret “complete” differently. How would you model state, events, and valid transitions so each client does not invent its own meaning?
- 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?
- 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?
- 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?
No questions in this section match your target. ·
E · Collaboration, communication, and influence3
- Sales promised several customers faster response times, but operations capacity has not increased. How would you renegotiate service levels and eligibility with sales, product, and service teams?
- A cross-department meeting records a decision, but an affected team says it cannot deliver on time. How would you confirm who accepted the decision, which objections remain, and who owns the next step?
- The release owner decides to ship on schedule. The security team says residual risk exceeds its acceptance range, but leadership chooses to continue. How would you record dissent, responsibility, and review conditions and clarify executable scope and escalation boundaries?
No questions in this section match your target. ·