zlacker

[parent] [thread] 6 comments
1. yalok+(OP)[view] [source] 2025-12-04 00:31:55
moonlighting is permitted by law in California (companies legally can't prevent you from doing it, iiuc), as long as there's no conflict of interest with your main job...
replies(2): >>fragme+32 >>jarjou+sd
2. fragme+32[view] [source] 2025-12-04 00:46:20
>>yalok+(OP)
As long as you don't use their hardware to do it.
replies(1): >>jarjou+Hd
3. jarjou+sd[view] [source] 2025-12-04 02:30:14
>>yalok+(OP)
"no conflict of interest" is basically meaningless if your day job is writing software. These clauses you sign are quite broad in what that scope of conflict could be.

Every company I've worked for has had very explicit rules that say, you must get written permission from someone at some director or VP level sign off on your "side project," open source or not.

You might want to check your company guidelines around this just to make sure you're safe.

replies(1): >>kyrra+Qm
◧◩
4. jarjou+Hd[view] [source] [discussion] 2025-12-04 02:31:35
>>fragme+32
that goes without saying, but it's still not free permission when you use your own stuff.
◧◩
5. kyrra+Qm[view] [source] [discussion] 2025-12-04 04:02:43
>>jarjou+sd
Side projects that aren't a conflict of interest when working at Google is rather limiting. Likely less so for small companies.
replies(1): >>yalok+0y
◧◩◪
6. yalok+0y[view] [source] [discussion] 2025-12-04 06:21:50
>>kyrra+Qm
Not really, in my personal experience and per my friends, most of big companies are pretty lenient about it, except for Apple.
replies(1): >>saagar+wE1
◧◩◪◨
7. saagar+wE1[view] [source] [discussion] 2025-12-04 15:21:40
>>yalok+0y
No, they're pretty strict. It just changes what you are allowed to do, with Apple being very restrictive in not letting you do it at all.
[go to top]