You crushed the job search, the interview gauntlet, and the salary negotiation, and you have accepted a promising offer… that came with an email attachment. You’re now staring at it—a wall of text also known as the employment agreement. This agreement is a legally binding contract that lays out basic rules, responsibilities, and rights of the employer and new employee—that is, you.
In addition to a start date, a standard employment agreement typically includes various clauses:
Both you and the employer sign the employment agreement at the start of onboarding. Before you sign it, read the agreement thoroughly; if your eyes start glazing over, be sure to at least clear them enough to answer the following key questions:
In some cases, these issues have a logic that might not be clear at first glance. In the IP case, for example, the organization might simply be protecting itself from an employee using work done for the company to field a competing or adjacent application.
Say, for example, your day job is to develop computer-aided design (CAD) systems for architects. Then, in your free time, you create and market a CAD system for fashion designers that has similar functionality. This is probably not going to go over well at the day job. But, if you create a voice-recognition system for your niece’s nightlight? Not likely to be a problem.
Either way, if the IP or noncompete clauses seem overly restrictive, check for what’s reasonable with state or national organizations (such as the U.S. National Employment Law Project). Once you understand the basic limits, you’ll know if they’re outside them and can ask your prospective employer to clarify–and if necessary, to modify the terms.
After all, with these and other clauses, deviations from what you expect could just be a wording or a communication issue. Or: such deviations might flag a problem that you don’t want to face downstream. If you see a problem with your employment agreement, write it out clearly, in an email, and get it resolved before you sign.
Disclaimer: The author is completely responsible for the content of this article. The opinions expressed are their own and do not represent IEEE’s position nor that of the Computer Society nor its Leadership.