A few years back, we had a junior candidate join us right before a major launch. He ended up being fired after a few months because after he spent 3 weeks doing

A few years back, we had a junior candidate join us right before a major launch. He ended up being fired after a few months because after he spent 3 weeks doing nothing, when we tried to ramp him up, he struggled with the tasks he was assigned. I suspect that he struggled to find his next job because he b had worked for us for 3 months and had essentially done nothing in that time. You don't want that. You NEED to get familiar with the codebase. The team after doing the launch, will be busy dealing with post launch issues and will struggle to onboard and train you. Anything you can do to get more familiar with the product and the codebase will help. Some suggestions are to ask for a bug list for the current launch and work on those or volunteer to QA issues for the launch or work on automated tests. Ask the PM what you could do to help.