A practice prompt we wrote. No company or candidate report names it, so it carries no company tag.
How to answer
This question tests timing as much as scripting. Automate on the first run and you encode a process you don’t understand yet; wait too long and the customer pays for your hands for months. Your story should show why the moment you picked was the right one.
- The manual work, concretely. What you did, for whom, how often and how long it took. “Every Monday I reconciled their shipment export against the carrier invoices by hand.”
- Why by hand first. What the manual runs taught you: the edge cases, the fields that lied, the steps that needed a person.
- The trigger. What tipped it: the hours, an error that reached the customer, a second customer with the same need. Say what you knew by then that you did not know on the first run.
- The safety checks. How you proved the automation matched you: a parallel run against your manual output, and the difference it caught. Then what guards it now: totals that must reconcile, an alert when they don’t, and cases it hands to a person instead of guessing.
- What it saved, measured, and where it lives. Hours per week and error rate, before and after. Then who owns it: a job their team runs, one you support, or a request to product because the next customer needs it too.
Say out loud what you left manual and why. An automation that knows its limits is the sign of judgment the interviewer is listening for.
The traps: a script that ran silently wrong for weeks, a tool only you can run, and a saving you estimate but never measured.
Follow-ups
What the interviewer may ask next, once your first answer is on the table.
- How many times did you do it by hand before you automated it, and what did the hand runs teach you?
- Why was an engineer doing this by hand in the first place? Should it have been a product feature?
- Who runs it now, and what happens when it fails while you are away?
Where answers go wrong
- Says “I wrote a script and it saved a lot of time” with no before-and-after measure and no check that the automated output matched the manual one.
- Automates something done once or twice, so the story is about building a tool, not about knowing when the work had become repeatable.
Answer this in two minutes
Write the answer you would say out loud. The clock starts with your first word.
Illustrative answer about a fictional project
I was a solutions engineer at a company that runs online ordering for restaurant chains. One customer, a fast-casual chain, opened a new location every few weeks, and each one had to be set up in our platform before launch: menu, prices, modifiers, tax rate, opening hours and delivery zone.