'I have been hunted down by HR reps, lawyers, and comms people:' Developers discuss the pain and prevalence of side work clauses

Side-work clauses are becoming a real friction point for Game Developers, especially for people who build games, art, tools, or content on the side to sharpen their craft or earn extra income. Developers are describing a pattern where outside projects can trigger scrutiny from HR, lawyers, and communications teams, even when the work is clearly separate from their employer’s products.

The core problem is that these clauses are often broad enough to cover almost any creative output, which makes it hard to know where the line is between a harmless hobby and a policy violation. For experienced devs, that uncertainty matters: it can affect whether you can prototype a game at night, take freelance illustration work, contribute to open source tools, or even maintain a public portfolio without asking for permission first.

The broader concern is cultural as much as contractual. Game development already relies on personal experimentation, and side projects are often where new mechanics, pipelines, and visual styles are born. When companies treat outside creativity as a liability, they risk discouraging the very kind of initiative that helps developers grow and, in some cases, helps studios recruit better talent.

For teams and managers, the practical takeaway is that these policies need clearer definitions, narrower scope, and better communication. Developers want to know what counts as competing work, what must be disclosed, and whether non-commercial hobby projects are protected. Without that clarity, side-work clauses can become a blunt instrument that creates distrust instead...