On this page
Questions to practise
Tell me about a network problem you solved. What happened?
They want to see how you work through a real problem, step by step, in your own words.
Use three parts: what broke, how you found the cause, and how you fixed it. Say “I”, not only “we”. Example: “Our office lost internet. I checked the logs and found a bad switch port.”
What did you check first?
They want to know if you start in a logical way, not by guessing.
Name your first step clearly, like checking alerts, logs or the physical connection. Then say why you started there. Example: “First I checked the logs, because they show recent errors.”
How did you find the cause?
They want an engineer who tests ideas and finds the real cause, not just the symptom.
Explain how you narrowed it down. Say what you tested and what you ruled out. Example: “I tested the cable, then the port. The port was the problem.”
How did you know it was fixed?
They want to see that you check your work and confirm the problem is really gone.
Say how you tested after the fix. Mention monitoring, a ping test, or users confirming the service works. Example: “I pinged the server and watched the alerts for an hour. Users said it worked.”
How do you plan a change on a live network?
Changes can cause outages. They want someone careful who plans before acting.
Give clear steps: test first, book a change window, tell the people affected, and write a rollback plan. Example: “I test it first, book a change window, and write a rollback plan.”
What do you do if a change fails?
They want to know you have a safe way back and stay calm.
Talk about your rollback plan. Say you follow the steps to undo the change, check the network works again, and tell the team. Then explain you look for the reason before trying again.
Who do you tell before you make a change?
Good communication stops surprises for users and other teams.
Name the groups you inform, such as your manager, other teams, or users who may notice. Say when you tell them and how, for example by email or a change ticket.
Do you keep notes or documentation? How?
Clear notes help the team fix problems faster and understand past changes.
Say what you write down and where. Example: “I always write down what I changed and why.” Mention diagrams, tickets or a shared document if you use them.
How do you handle on-call work?
They want someone who stays steady and organised when something breaks at night.
Describe your steps: check alerts first, write down each step, and ask for help when needed. Example: “When I get a call at night, I check the alerts first and note each step.”
When do you ask for help during an incident?
They want someone who knows their limits and does not wait too long.
Say it is normal to ask for help. Give a clear point, like when the problem affects many users or you are stuck after some time. Explain who you contact.
Let me think of a good example.
Clara
AI coach
Leo
AI coach
Lines to try
Let me think of a good example.
First I checked the logs, then I tested my idea.
I always write down what I changed and why.
Before any change, I test it and write a rollback plan.
When I get an alert, I check what it says first.
If I am stuck, I ask a teammate for help early.
Common questions
What if I make mistakes in English?
That is okay. Use short, clear sentences. The interviewer wants clear steps and real examples. If you need time, say “Let me think of a good example.” If you do not understand a question, ask politely: “Could you say that again, please?”
Should I say “I” or “we” in my answers?
Use “I” for the things you did yourself. It is fine to mention the team, but the interviewer wants to know your own steps. If you only say “we”, they may ask, “What did you do yourself?”
How long should my answers be?
Short answers are fine. Aim for a few clear sentences. For a problem story, cover what broke, the cause, and your fix. If the interviewer wants more detail, they will ask a follow-up question.