Companies would do everything the could to get existing employees in the workforce
I'm not disagreeing with you. I would submit that this is already true for other reasons. Speaking specifically of IT or INFOSEC fields, companies currently have extremely high expectations or experience requirements/desires.
This has been a problem for the INFOSEC field where there's a shortage, but companies don't want to hire entry level candidates with little to no experience. They want reasoned, veteran INFOSEC practitioners, which there isn't enough of.
generalized education requirement, above high school, that company should be required to pay off its employees student loans
Much like cell phone carriers locking you into a contract, companies would try to force you to work for them for X number of years because they paid your loans
I like that you both brought this up. There's a real life example of this in the US military. It's a well known benefit/incentive for military service that they would fund your college education if you work for them long enough. You signed your service contract, but if you met that, you got your education for 'free' if you want to call it that. It's a little different in you might be killed in a stupid political war along the way, but it shows that the idea is practical and can work.
I guess if I had the choice of being hired at a really decent company and they would fund some highly sought after training as long as I gave them a reasonable number or years of employment with reasonable compensation, I wouldn't have a problem with it.
On the other had, the SyFi fan that I am, I could see a bit of a dystopian future where you have to belong to companies for a while to start off in life. If you consider that people now start off in massive student loan dept, the dystopian ownership is currently banks while people take up to 20+ years to repay student loans.
@[email protected]
This was a very interesting example. Personally, I don't use any of the higher math that degree programs wanted. For people in the field you're talking about, it would be needed. So in that sense, a dev working for one company would be fine, until they wanted to dev for a company that needs those maths.
I counter my own point though and say that most people who don't use those higher level maths forget it. I am a very good use or lose example.
@cole@[email protected] I agree there can be separation of role types. This is annoyingly inconsistent across industry. Lead/architect/principle/engineer terms get thrown around for all kinds of roles. Sometimes companies just use them as title changes for promotion and talent retention. It would be nice if companies considered adapting a standardize framework for some uniformity. The NICE model comes to mind, but I've had people tell me they think it's too academic and not pragmatic in the real word. I don't think I agree with them.