TOPIC
Mobile
These are the same questions found in the library, grouped here by the capability each one mainly examines.
33 questions
A · Professional problem solving and implementation13
- A user backgrounds the app while editing, and the operating system may kill its process. On return, which state should be restored and which should be reloaded, and how would you avoid losing a draft or overwriting newer data?
- A new feature adds startup dependencies and cold start becomes much slower on low-end devices, while high-end metrics remain normal. How would you prioritize optimization?
- A user edits offline and queues several changes. When connectivity returns, the token has expired and some requests may already have reached the server. How would you design reauthentication, idempotency, and conflict handling?
- From a file or the network to picture and sound playing, what stages does a video go through? How do decoding, audio-video sync, stutter, and hardware acceleration each affect the experience?
- How would you design an immersive audio and video feed so that swiping up and down has almost no waiting? How do you balance preloading, player reuse, memory, and data?
- How should the loading and request strategy of streaming media be designed so it starts fast and does not stall? How do you trade off segmenting, adaptive bitrate, preloading, and caching?
- A client must upload a large file, but the operating system may pause or terminate background work at any time. How would you chunk the task, persist progress, and make rescheduling safe?
- A user opens a protected order-detail page from an external link. How would you design route parsing, login return, and authorization so the deep link cannot bypass in-app controls?
- A list screen scrolls poorly even though network metrics are normal and memory is stable. How would you determine whether main-thread computation, layout/drawing, or lock waits are responsible?
- 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?
- 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?
- 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?
No questions in this section match your target. ·
C · Value judgment and direction setting2
- 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?
- 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?
No questions in this section match your target. ·
D · Delivery and ongoing operations3
- A mobile release depends on app-store review with variable duration; backend and web can launch earlier, but a marketing campaign has a fixed date. How would you plan release windows, feature flags, and cross-platform degradation?
- A mobile release goes to 5% of users. The crash rate appears to double, but active devices are few and mostly one older model; a marketing campaign is near. How would you limit harm, gather evidence, and decide whether to continue, pause, or roll back?
- After a mobile release, network failures rise while server metrics remain normal; affected users cluster on older OS versions and weak connections. How would you scope the incident, reduce impact, and decide whether to pause or roll back?
No questions in this section match your target. ·
G · Learning, adaptation, and sustained growth15
- A mobile release crashes on specific devices and you help fix it. How would you transfer the lesson into testing and release practice?
- A new mobile OS changes background-execution limits. You have read the docs but not applied them. How would you verify your understanding?
- You traced battery drain to a background task, and the team wants to apply the lesson elsewhere. How would you extract a reusable method without copying it mechanically?
- You move from one mobile platform to a multiplatform project. Some experience transfers, while some may create false assumptions. How would you learn and validate?
- You learn a new mobile profiler and want to know whether it is faster or more accurate than current methods. How would you validate it?
- The app store rejects a release, and the team says rules were unclear and launch is affected. How would you review preparation, communication, and validation?
- You help build offline caching; success improves, but sync conflicts and support contacts rise. How would you review the approach and decide what next?
- The same backward-compatibility issue happened again. Earlier reviews added tests, but they still missed a real user combination. How would you find out why the corrective actions failed?
- Crashes rise slightly during a limited rollout, but the team expands the audience and later receives widespread complaints. How would you review the decision?
- A mobile platform changes its permission policy, making the invested solution unshippable as planned. How would you recover and re-plan?
- Two consecutive releases are blocked by app-store review, and the team feels effort is unrewarded. How would you recover momentum and find controllable next steps?
- A mobile app has recurring issues on a few devices, and the team relies on overtime testing. How would you restore a sustainable response?
- Legacy OS compatibility has slowed the team several times, but no one owns improvement. How would you decide whether to invest time and drive learning?
- Mobile privacy permissions and review rules keep changing, with no formal training. How would you plan ongoing learning and apply it promptly?
- You are interested in cross-platform frameworks, but the product may not need migration. How would you choose learning investment and decide whether to apply it?
No questions in this section match your target. ·