This is Part 10 of 10, a practice guide with 50 senior project and production interview questions. Use the answer frameworks to prepare truthful stories from your own work; do not present templates as personal experience.
Complete series
This Dev.to series has five core handbook articles plus five focused practice extras. Open the series page to move through the complete reading order:
- Part 1: JavaScript — core handbook, questions 1–120
- Part 2: React — core handbook, questions 121–220
- Part 3: React Native — core handbook, questions 221–420
- Part 4: Performance & Architecture — core handbook, questions 421–560
- Part 5: Senior & System Design — core handbook, questions 561–719
- Part 6: Output-Based JavaScript Practice — bonus practice article
- Part 7: Coding Interview Practice — bonus practice article
- Part 8: Code Output Challenges — bonus practice article
- Part 9: Current React Native Interview Questions — new high-frequency practice article
- Part 10: Project & Production Interviews — senior project ownership and real-production practice
How to answer project questions
Use a concise STAR structure: situation, task, action, and result. Include the technical constraint, evidence used to make decisions, user impact, collaboration, and the durable improvement that followed.
Project architecture and ownership
🔴 Senior
1. How would you explain your last React Native project architecture?
Answer framework
Answer: Use a truthful diagram or narrative: app shell, navigation, feature boundaries, state ownership, API layer, storage, analytics, native integrations, testing, and why those choices fit the constraints.
2. How do you describe a feature you owned end to end?
Answer framework
Answer: Use STAR: user problem, constraints, your technical decisions, delivery coordination, measurable result, and what you would improve.
3. How do you choose feature-based versus layer-based folders?
Answer framework
Answer: Prefer clear product-domain ownership and public interfaces; keep shared platform services and UI primitives separate from feature internals.
4. How do you explain a difficult trade-off in your project?
Answer framework
Answer: State the options, constraints, evidence, reversible decision, user impact, and outcome rather than presenting one option as universally correct.
5. How do you introduce a shared design system?
Answer framework
Answer: Start with high-use primitives and tokens, document contracts, migrate incrementally, enforce accessibility, and measure adoption and regressions.
6. How do you manage technical debt in a fast-moving app?
Answer framework
Answer: Make debt visible, connect it to risk or delivery cost, reserve capacity, and remove it through incremental work rather than vague rewrites.
7. How do you estimate a complex mobile feature?
Answer framework
Answer: Break it into UI, backend contract, native capabilities, analytics, security, testing, rollout, and unknowns; give ranges and assumptions.
8. How do you handle an unclear product requirement?
Answer framework
Answer: Clarify the user outcome, edge cases, success metric, privacy and failure modes, then document a small proposal before building.
9. How do you make a feature configurable?
Answer framework
Answer: Use typed, validated configuration and capability flags with safe defaults instead of scattered runtime conditions.
10. How do you explain your contribution on a team project?
Answer framework
Answer: Be specific about your ownership and collaboration, distinguish your work from team work, and quantify outcomes honestly.
Production incidents and reliability
🔴 Senior
11. How do you answer a production incident question?
Answer framework
Answer: Use a truthful STAR story: detection, user impact, containment, evidence-based root cause, communication, durable prevention, and measured result.
12. What do you do when crash rate rises after release?
Answer framework
Answer: Stop or slow rollout, identify affected release and cohort, inspect symbols and breadcrumbs, mitigate with rollback or flags, then verify recovery.
13. How do you handle a release-only bug?
Answer framework
Answer: Compare release configuration, shrinkers, environment, permissions, symbols, and timing; reproduce on a signed build before changing code.
14. How do you investigate an Android ANR?
Answer framework
Answer: Start with Play Console or captured traces, inspect the blocked main thread and locks, move blocking work off main, and verify in release mode.
15. How do you handle a broken token refresh flow?
Answer framework
Answer: Contain repeated failures, ensure one refresh owner, clear unrecoverable auth safely, preserve a pending destination when appropriate, and add telemetry.
16. How do you respond to a backend outage?
Answer framework
Answer: Show a clear recoverable state, use cached data when safe, bound retries, avoid request storms, communicate status, and measure user impact.
17. How do you debug duplicate payment attempts?
Answer framework
Answer: Treat the backend as source of truth, use idempotency keys, disable duplicate client actions, reconcile unknown states, and audit telemetry safely.
18. How do you manage a failed database migration?
Answer framework
Answer: Preserve recovery paths, stop unsafe progression, capture non-sensitive diagnostics, test upgrade paths, and ship a deterministic repair or rollback.
19. How do you prevent a notification from opening the wrong screen?
Answer framework
Answer: Use a typed navigation intent, validate auth and authorization, wait for navigator readiness, and make duplicate delivery idempotent.
20. What belongs in an incident postmortem?
Answer framework
Answer: Impact, timeline, trigger, systemic contributors, detection gaps, decisions, action owners, and verification of prevention work.
Performance and scale stories
🔴 Senior
21. How do you describe a performance improvement project?
Answer framework
Answer: Name the user-visible symptom, baseline metric and device, evidence, smallest effective change, measured improvement, and regression guard.
22. How do you optimize a slow FlatList in production?
Answer framework
Answer: Profile release-mode JS/UI frames, images, row renders, memory, and data flow; fix the measured bottleneck and compare before/after metrics.
23. How do you reduce app startup time?
Answer framework
Answer: Measure native initialization, bundle evaluation, critical network, image work, and first useful content; defer noncritical work and verify cohorts.
24. How do you investigate rising memory?
Answer framework
Answer: Reproduce a representative lifecycle, capture native and JS evidence, find retained resources, reduce peak allocations, and verify on constrained devices.
25. How do you explain a JS thread freeze?
Answer framework
Answer: Identify synchronous CPU, parsing, render, or event work; reduce input, chunk or defer work, move suitable work native, and measure responsiveness.
26. How do you improve image-heavy feeds?
Answer framework
Answer: Use virtualized rows, correctly sized images, caching, cancellation, pagination, memory measurement, and cautious prefetching.
27. How do you decide whether to add memoization?
Answer framework
Answer: Profile first; fix state ownership and reference churn before using memoization for a measured expensive path.
28. How do you keep offline data responsive?
Answer framework
Answer: Use a local source of truth, transactional writes, incremental queries, durable sync, and visible freshness state.
29. How do you set performance budgets?
Answer framework
Answer: Define user-impact metrics such as startup percentile, frame drops, memory peak, API latency, and crash-free sessions per representative device tier.
30. How do you verify a performance fix remains fixed?
Answer framework
Answer: Add a repeatable benchmark or trace, production monitoring, a release-mode test path, and an alert threshold where appropriate.
Senior delivery and leadership
🔴 Senior
31. How do you lead a React Native migration?
Answer framework
Answer: Inventory dependencies and native boundaries, baseline risk, migrate incrementally, maintain rollback, test both platforms, and stage cohorts.
32. How do you mentor engineers on mobile work?
Answer framework
Answer: Match guidance to risk and experience through pairing, examples, bounded ownership, reasoning-focused reviews, and reusable documentation.
33. How do you handle architecture disagreement?
Answer framework
Answer: Align on constraints, compare trade-offs and reversibility, time-box evidence gathering, record the decision, and support the outcome.
34. What do you look for in senior code review?
Answer framework
Answer: Correctness, cancellation, failure paths, state ownership, security, accessibility, realistic performance, tests, native lifecycle, and observability.
35. How do you communicate a delivery risk?
Answer framework
Answer: Raise it early with impact, evidence, options, trade-offs, recommendation, and a decision deadline; avoid hiding uncertainty.
36. How do you work with Android and iOS engineers?
Answer framework
Answer: Agree on typed contracts, thread and lifecycle ownership, release validation, observability, and clear ownership for platform-specific decisions.
37. How do you plan a safe rollout?
Answer framework
Answer: Use feature flags or cohorts, define success and rollback metrics, monitor user impact, and expand only after stable evidence.
38. How do you prioritize bugs against features?
Answer framework
Answer: Use severity, affected users, trust, revenue, workaround, risk of recurrence, and cost to decide transparently with product partners.
39. How do you handle a missed estimate?
Answer framework
Answer: Communicate early, explain changed assumptions, re-scope or re-sequence work, protect quality and user impact, and improve estimation feedback loops.
40. How do you define senior ownership?
Answer framework
Answer: Take responsibility for outcomes, make trade-offs explicit, improve team systems, prevent repeat failures, and communicate clearly.
Interview storytelling and project questions
🔴 Senior
41. Tell me about your most challenging React Native project.
Answer framework
Answer: Use a truthful story with a clear problem, constraints, technical decisions, collaboration, result, and lesson learned.
42. Tell me about a mistake you made in production.
Answer framework
Answer: Own your role, explain recovery and user impact, then focus on the durable test, process, or design improvement.
43. Tell me about a time you improved code quality.
Answer framework
Answer: Describe the initial pain, the smallest practical change, adoption strategy, measurable result, and how you sustained it.
44. Tell me about a conflict with product requirements.
Answer framework
Answer: Show curiosity about the user goal, explain technical or risk evidence, offer options, align on a decision, and commit to delivery.
45. Tell me about a difficult native integration.
Answer framework
Answer: Explain the capability, platform differences, contract design, error and lifecycle handling, test plan, and production outcome.
46. Tell me about a security decision.
Answer framework
Answer: Describe the threat, data classification, trade-offs, chosen controls, validation, and residual risk without exposing secrets.
47. Tell me about a release you led.
Answer framework
Answer: Cover readiness criteria, CI and signing, rollout cohorts, monitoring, rollback, communication, and final results.
48. Tell me about an offline-first feature.
Answer framework
Answer: Explain local data model, mutation outbox, idempotency, conflict rules, sync status, and user experience during failure.
49. How do you answer a question about a project you did not own fully?
Answer framework
Answer: Be honest about your scope, describe your specific contribution, acknowledge collaborators, and explain what you learned.
50. What questions should you ask the interviewer about their project?
Answer framework
Answer: Ask about users, architecture, release process, native ownership, performance and crash metrics, testing, security, and the team’s current technical risks.
Final preparation checklist
- Prepare three truthful project stories: feature ownership, production incident, and performance or reliability improvement.
- Quantify impact where possible: crash rate, startup time, API failures, conversion, delivery time, or support volume.
- Explain trade-offs and what you would improve with hindsight.
- Never reveal employer secrets, customer data, credentials, or confidential architecture details.
Top comments (0)