Investigate
Incident Desk
Production problems. System failures. You open the channels.
A browser incident desk: logs, metrics, traces, database, cache, API, deploys, and changes. Name the root cause. Then read the postmortem.
Enter →Vol. 01 / Manila
Al Beltran
Engineering Lab
Production problems. System failures. Architectural trade-offs. You investigate.
Interactive desks for incidents, design, SQL, and interviews. Everything runs in the browser. Progress stays on this device. Nothing here is live production telemetry.
Al Beltran Engineering Lab
Today's engineering challenge
Checkout latency +382%. Pool at 98%. What do you open first?
Open today's lab →Engineer profile
- Completed
- 0
- Best
- 0
- Streak
- 0
- Incident Desk0
- How I'd Build This0
- Debug This0
- System Design Simulator0
- Code Battle0
- SQL Arena0
- Production Is On Fire0
- Cloud Cost Challenge0
- Engineering Interview0
Achievements
First Fix
Completed your first Engineering Lab challenge.
Bug Hunter
Solved 10 debugging challenges.
Production Hero
Resolved 5 production incidents.
Architect
Completed 10 system design challenges.
Speed Demon
Finished a timed challenge under the target time.
SQL Wizard
Completed 10 SQL Arena challenges.
Senior Mindset
Scored 90% or higher on a senior or staff interview.
Cost Cutter
Beat a Cloud Cost challenge under budget.
Experiences
Trade-offs
How I'd Build This
Pick a store, a cache, and a bus. See what you just committed to.
Architecture prompts with no single right stack. Each choice has strengths, weaknesses, and operational cost.
Enter →Incidents
Debug This
Production is broken. Find the root cause.
Inspect simulated logs, errors, metrics, and symptoms, then name what actually failed.
Enter →Architecture
System Design Simulator
Design a system that survives millions of users.
Pick components and architecture decisions, then score scalability, reliability, performance, cost, and complexity.
Enter →Timed
Code Battle
Solve engineering problems before time runs out.
Timed questions across JavaScript, TypeScript, React, Node.js, Java, Spring Boot, PHP, Laravel, and SQL.
Enter →Data
SQL Arena
Write the query. Beat the challenge.
Query a small in-browser dataset. No server and no real database — just SQL-style thinking.
Enter →Response
Production Is On Fire
Your production system is failing. You have limited time.
Choose incident actions and watch downtime, latency, cost, and users affected change.
Enter →Estimates
Cloud Cost Challenge
Build the architecture without burning money.
Tune compute, database, storage, CDN, and cache using static estimate pricing — not live cloud APIs.
Enter →Thinking
Engineering Interview
Think like a senior engineer.
Junior through Staff quizzes on JavaScript, React, backend, system design, databases, DevOps, and leadership.
Enter →How the challenge works
- Pick an experience. Every challenge runs in the browser against static data.
- Your scores, streak, and achievements stay in localStorage on this device only.
- Share a result as text or a link. Nothing is uploaded and there are no accounts.
Key concepts
Practice over pages
Each tool is a small engineering experiment: debug, design, query, respond, estimate, and explain.
Local progress
Completions and high scores never leave the browser. Clear site data and the profile resets.
Common mistakes
- Treating a high score as proof you would ship that design in production.
- Skipping the debrief. The explanation is the useful part.
Interview tips
- Say the tradeoff out loud before you pick a component or a root cause.
- Time-box. Interviewers care about how you prioritize under pressure.