Training and experience are different qualifiers. Often times employers want more then you can do "x" in "y" framework. Sure out of some kind of training progra

Training and experience are different qualifiers. Often times employers want more then you can do "x" in "y" framework. Sure out of some kind of training program you can do things quickly, "correctly" if there is such a thing. And most importantly on time. But it often time is more than just the skills to do the job, it's the skills to think, to conduct yourself in a professional manner and also the relevant experience doing many different things. If the company just wants you to lay down lines of code the way you lay down bricks, sure I could see any tech school training as being sufficient. But years of experience are an indicator of a number of different factors: 1. You were competent enough to hold a job(s) doing x for y years 2. You get along with others if you don't how could you possibly accrue 5 years of experience working 3. You've seen different approaches to doing things, which can give you insight into how to do things that make sense for this application 4. You have awareness of performance, maintainability, testing etc... that affect a long-term success of a project. I think it can be helpful, recent grads are just that, recent grads. You have a lot to learn about working for a company, contributing code in a long-running project and other things that your college or tech school training cannot provide. Best case the code you write for this company will be in production and running for many years to come. That's what the company is hoping for. Not just a short-term implementation of some best practices to satisfy short-term goals.