I did something like this back when I worked at a fast-growing startup that was eventually acquired. I built shiny new features, sure, but I also reviewed every

I did something like this back when I worked at a fast-growing startup that was eventually acquired. I built shiny new features, sure, but I also reviewed every line of code from before I joined, found major problems, refactored them and documented best practices so they could be avoided in the future, and made sure that the founder/CEO was aware of my work every step of the way. I was promoted to lead the team a few months later. To be honest, I found refactoring and cleaning up tech debt to be just as fun, if not moreso, than building new features. And the user-facing results spoke for themselves: Less bugs and faster response times. Everybody wins.