Question: Tell me about a time you did something you were not asked to do? Why did you do it?
Answer: For invoices, we were adding insurance payment. We do it before the payment. Where you were adding this insurance stuff, the code was duplicated between services, and they were doing their own insurance calculation. We went in not knowing the full scope of it. It ended up being a pretty big re-write. I was confident that I would be able to execute on time.
Question: Do you have another example?
Answer: When I got to the company, there were working on an angular app for a year. They lacked coding standards. I suggested and implemented a more modern angular app. You have an HTML template refers to a file, refer to a function. I upgraded to angular 1.5, which gave us access to components that helped us refactor a lot of code. I pushed others to do this as well. People told me there was no good reason to do it. But I had done research about this. I convinced them that the things used were anti-pattern. I also changed a lot of old code, which was commonly used.
Leadership principle asserted: Think Big
The candidate gave two examples to this question. In his first example, he described a case where a much larger scope of work was discovered for a project that was initially thought to be small.
I pushed for an example where he took the initiative to do something bigger than what was required and that needed convincing others.
When the candidate joined his current company, his team was working on an Angular Application for a year. His team wasn’t following the best practices and industry standards for developing Angular application. Candidate upgraded the application to Angular 1.5, which allowed them to use Components from thereon. This allowed his team to refactor a lot of code. At first, when he proposed to use a new version of Angular, he got push back from his team. He was told that there is no real benefit to this upgrade. He did research convinced his team that a lot of their code is using anti-patterns, and using Components would help them fix these.
It’s not because the interviewer asks a second example that all hope is lost. In this example, the interviewer felt confident that he gathered enough datapoints with the two examples combined.