I learned at a short, obstructed airport, but my towered training was into Baltimore/Washington International, then known as Friendship. We flew in on weekday evenings, and it was busy, but most of the time, we did not need to sidestep for airliners behind us. Later, my Instrument and Commercial check rides were into BWI, and both of them had interruptions. The IR, outside the FAF, "Could you do a very slow 360 to the left to allow a heavy to pass?" Affirmative. Then as I approached the fix the second time, "could you maintain at least 100K to provide proper spacing for the heavy behind you?" Asked the DPE if we were landing, he said no, and I agreed to 100K (the DPE had also said that if I blew it, speed would not be an excuse). Flying in that sort of environment prepares you for the real life of major terminals.
Over the years since, I have landed at ALL the Washington area airports, including Andrews Airbase, plus MIA, STL, RDU, JAX, SAV, CVG, and transited New York City, Logan, Chicago, and Atlanta several times.
That early introduction to the big ones was essential to my comfort in my early long cross country trips, landing at major airports or transiting through their airspace.
The pilot in the video spent too much of his valuable attention to the video, and not nearly enough to his flying. Missing a radio call to your own plane should not happen. I missed one on my IR check ride, but was flying a rental, and forgot which one I was in. The DPE called me on that, and I immediately responded, the only glitch on the ride. The video would have been better if the pilot had a friend doing all the video monitoring, and the left seat had concentrated on accurate flying. I am a believer in the sterile cockpit in the near airport environment.