This is usually a nonsense argument unless you're in a very slow-moving company. Two years is not only enough to see the results of your architectural decisions

This is usually a nonsense argument unless you're in a very slow-moving company. Two years is not only enough to see the results of your architectural decisions, but by that point the architecture would already be due for change. 1-1.5 years in a fast-paced software team is plenty enough to learn 95% of everything you're ever going to learn there and live through one major system lifecycle.