On this page
Questions to practise
Tell me about an outage you handled.
She wants to see how you act under pressure when a real system fails.
Choose one real outage. Say what broke, what you did first, who helped, and how the service came back. End with one thing that changed after. Keep it in order, step by step.
What did you do first when you saw the problem?
She wants your own actions, not only what the team did.
Say "I", not only "we". Name your first step, for example checking alerts, logs or recent changes. Say why you chose that step. Exact details are better than general words.
How did the service come back, and what changed after?
She wants to know if you fix the cause and learn from problems.
Explain the quick fix and the real cause. Then say what you changed: a new alert, a test, a runbook or a review. One honest lesson is enough.
Tell me about something you automated, and why.
Automation is a core part of DevOps work. She wants a real example with a result.
Say what was slow or done by hand. Say what you built and how. Give a clear result, like time saved or fewer mistakes. Numbers help, for example "from one hour to ten minutes".
What did you build yourself?
She asks this when answers sound general or only say "we".
Name your part clearly: the script, the pipeline step, the config you wrote. It is fine to say others helped. Just be clear about your own work.
What did the automation save?
She wants to know if your work made a real difference to the team.
Give one clear result: time each week, fewer failed deploys, faster recovery. If you do not know an exact number, give an honest estimate and say it is an estimate.
How do you work with developers when something breaks?
DevOps needs good teamwork. She wants to know how you communicate during problems.
Give a short real example. Say how you shared updates, who you asked for help, and how you stayed calm. Mention clear messages and respect for other people's time.
Tell me about a new tool you learned.
Tools change fast. She wants to see how quickly and carefully you learn.
Name one tool. Say your steps: reading the docs, building a small test project, asking a colleague. Then say how you used it at real work.
Tell me about a system you looked after. What did you enjoy about it?
She wants to understand your real experience and what motivates you.
Describe the system simply: what it did and your role. Then say one thing you enjoyed, like making it more stable or faster. Keep it short and real.
Is there anything you would do differently now?
She likes honest reflection. It shows you learn and grow.
Choose one small, real point from your outage or automation story. Say what you learned and what you would do now. Stay positive and short.
Let me think of a real outage I worked on.
Clara
AI coach
Leo
AI coach
Lines to try
Let me think of a real outage I worked on.
My first step was to check the logs and the alerts.
I moved traffic to the backup while we looked for the cause.
I wrote a pipeline, and now deploys take about ten minutes.
It saved the team about one hour each week.
I learned it by building a small test project first.
Common questions
What if my outage story is small?
That is fine. A small, real story is better than a big, general one. Make it clear: what broke, what you did first, who helped, how it came back, and what you changed after. Clear steps and your own actions matter most.
Can I say "we" in my answers?
Yes, teamwork is good. But the manager wants to know your part. Use "we" for the team, then say "I" for your own actions. For example: "We had an outage. I checked the alerts and rolled back the change."
What if I don't understand a question?
It is fine to ask. You can say: "Sorry, could you say that again?" or "Do you mean a production outage?" Taking a moment to think is also normal. You can say: "Let me think for a second."