Be honest about this: repetition is often where reliability lives, and where automation starts.
Healthy approach
1. Do the task correctly first 2. Notice patterns 3. Automate / templatize when ROI is clear 4. Keep a checklist so quality doesn't drift 5. Rotate 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.