Here is a simplified English version. It uses shorter sentences and easier words while keeping the important technical ideas, making it much easier to memorize and speak naturally during the interview.
Topic: Solving a System Breakdown on Student Registration Day
1. Situation
- “In my previous job, I managed the Student Registration System.”
- “On the first day of registration, thousands of students logged in at the same time. The system became very slow, and students could not register.”
- “Both teams started arguing. The Developer Team said their code was perfect and blamed the hardware. My team thought the code was bad. Everyone was pointing fingers while the system was still down.”
2. Task
- “My main goal was to stop the argument and get everyone to focus on one thing: fixing the system for the students as fast as possible.”
- “After that, I needed to find the real problem using clear data, so it would not happen again.”
3. Action
- Stopped the Blame Game: “I called an urgent meeting and told everyone, ‘The students cannot register right now. Let’s focus on fixing the system first. We can find out who is wrong after the system is back online.’“
- Looked at the Facts: “I shared my screen and showed our Monitoring Dashboard. The data showed that our servers and network were fine, but the Database Server CPU was at 100% because there were too many connections.”
- Fixed it Together: “I asked my team to increase the database size (Scale Up) immediately. At the same time, I asked the Dev team to change the ‘Save’ button code so students couldn’t click it too many times. In 30 minutes, the system was working again.”
- Held a Good Meeting: “The next day, I set up a Blameless Post-Mortem meeting. I told everyone we were there to fix the system process, not to punish any person.”
4. Result
- “The system worked well for the rest of the day, and the teams stopped arguing.”
- “We found out that a heavy database query was causing the bottleneck when traffic was high.”
- “To prevent this, we agreed to do Load Testing together before every registration day. We also added a Redis cache to make the database work less. This event changed our culture to be more data-driven and supportive.”