Debugging / Production Interview Questions 2026
Published July 22, 2026 · Updated July 22, 2026
2 Debugging / Production interview questions from Amazon, Uber and more. Real questions from Technical, System Design, and HR rounds.
2 questions
Companies: Amazon, Uber
All Debugging / Production Questions
Your new feature is working in development but failing in production. No exception is thrown. How do you systematically debug it?
Trip fares are occasionally being calculated twice, double-charging riders. The fare calculation service is stateless and horizontally scaled behind a queue. Where would you look first, and what's the likely root cause?
Practice these questions with AI feedback
Get instant grading on your answers, identify your weak areas, and generate a personalised 14-day study plan — all free.
Build my study plan →Same topic at specific companies
Related topics
DSA / Arrays
System Design
DSA / Trees
DSA / Graphs
Behavioral
Testing
Domain
DevOps
API Testing
DSA / Hashmaps
GCP / Real-time Data
Java / Pub-Sub
React / Performance
Node.js / Memory
SQL / Query Optimization
Python / Async
AWS / Lambda
Kafka / Consumer
Microservices / Saga Pattern
TypeScript / Type System
MongoDB / Indexing
Security / SQL Injection
Performance / Latency Tail
Redis / Cache Stampede
Elasticsearch / Cluster Health
GraphQL / Security
Data Engineering / Exactly Once
Snowflake / Architecture
PySpark / Core Concepts
Airflow / Scheduling
Web / WebAssembly
JavaScript / V8 Engine
Frequently asked questions
Your new feature is working in development but failing in production. No exception is thrown. How do you systematically debug it?
Your new feature is working in development but failing in production. No exception is thrown. How do you systematically debug it?
Trip fares are occasionally being calculated twice, double-charging riders. The fare calculation service is stateless and horizontally scaled behind a queue. Where would you look first, and what's the likely root cause?
Trip fares are occasionally being calculated twice, double-charging riders. The fare calculation service is stateless and horizontally scaled behind a queue. Where would you look first, and what's the likely root cause?