So when I first started the documentation was really bad, new services where created out of nowhere and nothing was documented. Why we did things and what not. So the first thing I did was creating/participating in technical design documents, or product decision docs, to actually validate data. If you contribute there, your team will recognize you more and more. Its kind of "passive" marketing within the team with few touchpoints to other teams when integrating APIs. Other engineers will see you on the docs and discussion which will make them remember you.
In most big corporations, promotion processes or people who drive the company will be in other teams. The managers and or tech leads of the whole domain or subgroup. To impress them you have to build and achieve things they will recognize. For me, in Klarna, the platform to do this was a monorepo where improvements had to be made to developer experience, build systems and so on. Most bigger corps have separate teams dedicated to that but improving documentation here and there always helps already.
I also got into blogging and driving open source at the company. Organized a hackathon and did many other mundane admin stuff, but coolest thing was that i got into an all hands regarding the hackathon, so actually everyone was seeing me. Reach out for these opportunities because i am sure your company will have these as well and the people are happy to get a helping hand, for sure.
Otherwise as other people mentioned I also kept a brag document, that helped me to collect all achievements and present them to my manager in case of questions about work progress or promotions: https://getworkrecognized.com/blog/junior-to-senior-software...
But overall lesson: Share your achievements like in newsletters of the team/blogs/hackathons/all-hands/group meetings/office hours and be involved in many groups so you can network and get to know people.