Tell me about something repetitive you automated. How did you decide it was worth it?
What they are really testing: Whether you evaluate automation economically rather than automating for enjoyment. They also want to see you consider whether the task should exist at all.
A real interview question
Tell me about something repetitive you automated. How did you decide it was worth it?
What most people say
drag me
“I automated our release notes because doing them by hand was boring and I like scripting.”
Boring is not a business case, and automating for enjoyment is how teams end up with 15 fragile scripts nobody else can maintain. It also skips the more valuable question of whether the task needed doing at all.
The follow-ups they ask next
When is automating actively the wrong call?
When the task is rare and the automation would rot between uses, when the process is still changing weekly, or when the manual step is a deliberate human checkpoint. Automating an unstable process bakes in a shape you are about to change.
How do you stop your automation becoming the next thing nobody understands?
Keep it in the main repository with tests and documentation, make it boring and readable rather than clever, and have someone else use it unaided before you call it done.
You saved 12 hours a month. Where did that time actually go?
Be honest: it usually spreads rather than converting into a project. The stronger argument is the error reduction and removing the bottleneck, since those are real even when the time saving is diffuse.
What the interviewer is listening for
- Quantifies frequency, duration and error rate
- Deletes unnecessary steps before automating
- Values consistency and shared knowledge over raw time
- Measured the outcome afterwards
What sinks the answer
- Automates because it is fun
- No cost estimate
- Never questions whether the task should exist
- Creates a script only they can run
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“It cost [frequency times duration, plus an error rate that caused untracked debugging later]. First I asked [whether it should exist, and deleted 2 obsolete steps]. Then automating took [3 days], paying back in [under a month] on time alone. The bigger wins were [consistency and removing a single point of knowledge]. Afterwards I [measured rather than assumed].”
Keep going with behavioural
Mid
Tell me about a time you broke production. What happened and what did you do?
Mid
Tell me about a time you disagreed with a developer about how something should be deployed.
Mid
Tell me about a time you were on call and it went badly.
Mid
Tell me about a mistake that cost the company money.
Mid
Walk me through a time you inherited a system nobody understood. Where did you start?
Mid
Tell me about a time you did not know something important and had to act anyway.
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free