Detailed explanation
This question tests whether you notice useful opportunities and take ownership beyond your assigned responsibilities. Interviewers are not simply looking for someone who works longer hours or accepts every extra task. They want evidence that you understood a real need, chose a sensible improvement, and delivered value without neglecting your original work. For a fresher or junior developer, the example can come from an internship, college project, volunteering activity, or student club; it does not need to involve a major business decision.
Build your answer around the difference between what was expected and what you voluntarily added. Briefly describe your assigned task and establish that it was completed or remained on track. Then explain the problem you noticed, why it mattered, and the action you took. If the improvement affected shared systems, data, or another person's workflow, mention how you checked with the relevant person before proceeding. This demonstrates initiative with judgement rather than acting outside your authority. Spend most of the answer on your specific contribution, not background information.
For example, if it reflects your actual experience, you could say: “During my internship, I was assigned to build a dashboard and completed it on schedule. I noticed that a teammate manually prepared the same report every Friday. After checking that automation would be useful, I wrote a script, compared its output with the existing report, and documented how to run it. Based on the teammate's usual preparation time, it saved about two hours each week. The team continued using it after my internship.” The validation, handover, and continued use make the contribution more convincing than simply saying you wrote extra code.
End with the benefit and, if useful, one sentence about what you learned. Quantify results only when you can explain the basis: a timed task, fewer manual steps, or feedback from the people using your work. If you lack a reliable number, describe an observable outcome honestly. Interviewers may probe whether the extra work was genuinely voluntary, whether others helped, and whether it created maintenance costs. A strong answer shows useful initiative, appropriate collaboration, and a sustainable result—not an attempt to appear indispensable.
Key points to remember
- Choose a genuine example with a clear benefit to someone else.
- Separate your assigned responsibility from your voluntary contribution.
- Show that your core work stayed on track and relevant permissions were respected.
- Explain your own actions, including validation and handover where relevant.
- Support the result with a defensible measurement or observable outcome.
Common mistakes candidates make
- Describing extra hours or extra features without explaining why they were useful.
- Claiming precise savings without evidence or presenting team achievements as individual work.
- Making unauthorised changes or neglecting assigned tasks and calling it initiative.
Likely follow-up questions
How did you know the additional work was worth doing?
Explain how you confirmed the need with the person affected and compared the likely benefit with the effort involved. Mention any small trial or quick check that helped you avoid building an unnecessary solution.
How did you measure the impact?
State the source of your measurement, such as timing the old and new processes or getting confirmation from the regular user. If the result was an estimate, label it clearly and explain its basis.
How did you balance this with your assigned responsibilities?
Describe how you completed the main deliverable first or agreed on priorities with your supervisor. Explain how you limited the extra work's scope so it did not put the original deadline at risk.
Interview tip: Deliver a 60–90-second story that clearly distinguishes what was asked, what you added, and who benefited.