Should I ask about company policy on side projects while interviewing for full time jobs?
I am currently interviewing for a new full time job (software engineer) and I am wondering what you all think about asking for the companies policy on side projects you wish to monetize.
I currently work at a job that does not mind as long as you aren’t building a competing product. But I’ve Interviewed at other companies that have ranged from absolutely not to it’s fine until you start making money from the project.
A few people have told me I shouldn’t even ask as indie hacking is a hobby to me like woodworking is to others. But I still want to make sure i’m not doing something that might come back to bite me later because of IP contracts engineers sign upon employment.
What do you think? Should I be asking or does it not matter?
I'd always ask. The answer is important to you, and it gives the interviewer or hiring manager a sense of what's important to you. Smaller companies I've worked at or consulted with don't have an official policy, but every one of the larger or enterprise companies I've worked with have a very similar policy: Do it on your own time, with your own hardware and software, and make sure it isn't competitive to our business.
If working on side projects is important to you, definitely ask during the interview process! Policies and written agreements on side projects vary widely, and it's never a good idea to assume your view will match an employer's view on the matter. Nothing worse than finding out when you're signing paperwork on your first day.
It's a bonus if you not only find an employer who allows for side projects, but gets excited when you ask and then talk about what you're working on.
When I've hired people in the past, I disclosed the policy of the company early on. I think that's a rare practice by hiring managers though. I've always had to push for details when I was on the other end of the interview table.
My experience has been the same. Many of the companies I've interviewed at are ok if it's just open source projects but it's different for if it's a side business. Thanks for the advice!
In the past, I disclosed a project because the company required to do so and it came to bite me later during review time as they (a specific manager and his manager) asked me to stop working on it!
At my current job, I disclosed my most important project as well (even though I had stopped working on it). Luckily I decided to continue working on it ten months later. The thing is that it will protect me even after I've left the company because I had disclosed this ahead of time.
On the other hand, I didn't disclose my projects at about ten other companies and everything was fine. But again, I didn't really make money on those either.
I would suggest disclosing your work as a precaution. It will protect you later.
One more thing. When I hire engineers, I expect them to be working on side-projects. Otherwise, they're not a good fit in my org.
I'm not 100% sure but I think I did read somewhere that some companies either don't allow you to work on side projects or some companies have it in the contracts that whatever you work on, even if its during your spare time, the company owns what you do.
I'm not sure if this is completely accurate so maybe someone else can confirm but I believe I read this somewhere, although was a while ago so it may have changed.
But think it is worthwhile checking what the companies policies as it will protect you in the future.
Yeah many tech companies require engineers to sign IP contracts that state that anything you build or create during your employment are owned by the company. From what I understand this is primarily to prevent people from building a competing product while employed. Some companies are more lenient about this than others but still make you sign it just to cover themselves. For example if you work at Apple you must cease development of any personal apps or projects as they deem all industries as part of their business. Contrasted to my current company who only cares if you are building a competing product.