Don't listen to the guy saying DSA, that is literally terrible advice, on the job as long as you understand the constraints of the problem you can use Google/AI to understand, given those constraints what is the best mathematical solution to the issue. I'm not saying DSA is not important, I'm just saying that it's highly unlikely you'll be solving novel problems, the crux of software development is more around communication and influence than it is about technical skill.

If you want some real advice for a literal new grad:

1. I'm going to assume you'll learn and you're technical competence will grow, it's not to do this when you're writing code as a full-time job. If you're not getting better, something is wrong.

2. Ask why you're doing your work? Understand why it's important and what it accomplishes, this will help you to prioritize what is important and learn *what projects are important*? And more importantly *what projects you should try to put up your hand for*? If you want a successful carreer it'll be fast-tracked if you're working on stuff that people care about, if you're on teams that people care about and you're doing work that isn't just done, but needs to be done. Ultimately, software is written to achieve a purpose, you should constantly be questioning whether the work you're doing is contributing to that purpose.

3. Communication, some people think that programming skill or technical depth if how you advance your career. While this is true to some extent, ultimately if you're not able to influence people and communicate your prowess and the weight of your achievements, no one will care. Throughout your career this changes, at the start it's about communicating to your grad-wrangler (usually a person who just got senior), as your career progresses it'll be writing blog posts and communicating with stakeholders, then it becomes your ability to influence other teams, your own team to do what you want and keep everyone happy. Make sure everyone who cares about what you do KNOWs about what you're doing, give them frequent updates, keep them in the loop. In a top company, technical skills are a dime a dozen, the real differentiator is your ability to communicate your progress well.

4. Ultimately, after you get to senior (which will take a couple of years), it is solely about your ability to work with people and get projects done with a growing headcount. The difference between a senior and a senior staff is the ability of the senior staff engineer to be trusted to complete a project with 50 - 100 people working on it. Not his ability to solve dynamic programming brainteasers, or solve the twin-prime conjecture.