This is ideally how QA should be run at most organizations. Help familiarize juniors with tooling like git, the command line, deploying things, writing tickets, communicating with the team-- have them see different parts of the engineering organization and then let them choose where they think they have the most interest.
I know because I've done this with wild success and everywhere that doesn't do this has had by comparison awful QA.
I know because I've done this with wild success and everywhere that doesn't do this has had by comparison awful QA.