Next step is to get recognized for simplification and "streamlining" of the codebase, by subsequent reduction.
Especially if more experienced and knowledgeable engineers can remove the code paths that are "in use" but shouldn't be - premature optimizations that can be simplified, redundancies that can be eliminated, features that aren't bringing in value. It's usually an underappreciated job but can lead to greatly improved velocity and significantly less fragility.