It's often called an "Intellectual Property Assignment" agreement, and they are usually way more restrictive than a simple non-compete, although you need to rea

It's often called an "Intellectual Property Assignment" agreement, and they are usually way more restrictive than a simple non-compete, although you need to read either very carefully. I found out the hard way about IP assignments after I accepted a software engineer position in my earlier days, around ~2005. The centimeter-thick document arrived by certified mail. I was raging mad, called the HR director that hired me and asked why this was not mentioned earlier. She said "everybody signs them" and "it's fine". To me, this was Not...Fine. They knew full well during my interview that I had side projects, including real software sales, real customers, and an LLC. I immediately consulted a lawyer, who gave me multiple options/ideas other than just signing the document outright. The HR Director, my future supervisor, and the Division Vice President I was to work under all met (this was a $700 million USD revenue per year company at the time, with 1400 employees, so not exactly small). The VP was visibly irritated and said things like "why do you even want to work for us anyway?". Things became heated quickly, and I remember inhaling one last time, grasping my chair with both hands in preparation to get up and walk...but the HR director intervened. We solved the problem by adding an addendum to the original IP agreement doc, listing all my side projects. I felt pretty weird on my first day on the job. :D Side Story: A few weeks on the job, I needed a special software utility to help do my work. That same VP (who is now the CEO) made me explain to him, one-on-one and for nearly an hour, on why I needed that software. That utility cost $45 USD. Pretty sure he didn't like me.