Many companies will try to pull this. It is up to developers to not let them. Ideally we could leave it up to states to do something, like California has done (

Many companies will try to pull this. It is up to developers to not let them. Ideally we could leave it up to states to do something, like California has done (I have read these kinds of IPR agreements are non-enforceable if you work in California). Unfortunately, we have to do it ourselves. If top engineers refuse to enter into these agreements then companies will be forced to not use them in order to remain competitive. Of course, if you use the company's time, software, or hardware to create something then they own it as a work for hire. It's less clear if it's built on your own time with your own resources but using knowledge you learned as part of your job. Generally, from what I've read, you're in the clear so long as the knowledge is not proprietary - but I am not a lawyer. So be devout in separation of your IP and their IP, as church and state. This of course means being willing to walk if they require it as a condition of employment, but good developers have a lot of options in many markets.