The short answer
Be honest about this: repetition is often where reliability lives, and where automation starts.
Healthy approach
- 1Do the task correctly first
- 2Notice patterns
- 3Automate / templatize when ROI is clear
- 4Keep a checklist so quality doesn't drift
- 5Rotate learning goals alongside ops work
Example outline
> Weekly CSV onboarding was repetitive. I documented the steps, then wrote a small parameterized script and a checklist for schema validation. Same work, less error, more time for modeling improvements.
Fresher tip
Manual data cleaning in a project → then a reusable cleaning function.
Interview tip: Don't sound bored by maintenance. Reliability is the job.