A "training program" starts with good onboarding. It might even start during the hiring process. A company with 10 devs can be training less experienced folks.
Yes, even the smallest organizations can have a decent onboarding process in terms of making sure new hires understand company policies and have the tools they need to work. But at that scale it's impractical to run a formalized engineering training program with assigned instructors teaching a defined curriculum. Realistically most of the training will have to be 1:1 mentoring delivered as needed by senior engineers. All senior engineers should be expected to participate, but of course that takes time and competent managers will plan for some temporary reduction in team velocity.
This is why pair programming is so popular, but this is presuming that the more senior in that relationship is maybe good at teaching/coaching/mentoring.
A better solution might be have a set person, or even outsource the pair programming with some mentor-in-the-middle who has teaching experience and also can build more user-centered training for that person. Like a vocal coach for music, but for software.
