> Years later, and I've taken a job in software at a large media company. I'll name no names but this company had music brands that were (and are) known globally.
How have you navigated intellectual property to SongBox with your current employer, who it sounds like works in the same industry and who might have claim on some part of what you've created?
If you worked on this while employed without getting a waiver their lawyers might beg to differ in the UK pretty much every contract I’ve seen has “we own all your discoveries unless stated otherwise” clause in it.
I understand what you're saying but it's not a thing in this case. And with my current employer I had my contract amended before I started (as a condition of joining, I recommend everyone does the same). The change implemented allows me to work on anything I want so long as it's not a competing product.
That sort of clause is pretty much universally challenged by anyone with a bit of experience and credibility, too, at least here in the UK. And so it should be. That goes whether we're talking about inventions (which normally means patents) or other intellectual property such as copyright (which appears to be what we're talking about in OP's situation).
"In the course of your employment" or similar words used to be a more reasonable standard that was widely considered fair to both sides for salaried employees. In other words, things you do on company time, using company resources and/or in the company's line of business go to the company, but they have no claim beyond that. I haven't spoken to a lawyer about this recently, so if the issue might affect you, please check whether this is still correct and don't just rely on my comment here.
Maybe what I am asking is ambiguous. However, @dogma said that anything you work on during the time you are employed might be regarded as company IP.
What I am asking is what happens with work/projects/apps that someone has done on the side before joining a company, and especially in the case that this creates a revenue stream.
Oh in that case I'm not sure, but I would always be clear with the employer at the interview stage.
In my current role I mentioned that I work on things on the side and they were like... oh that's not allowed, and I said... oh well I can't work here then.
In my current role I mentioned that I work on things on the side and they were like... oh that's not allowed, and I said... oh well I can't work here then.
Good for you! There seems to be a certain mindset in some company bosses, and it's usually middle management types who have made it to a moderately senior level and never not been "company men" (or women etc. obviously) in my experience. It's like they think becoming an employee at their firm means giving over your life to them, and that by graciously allowing you to work for them they're doing you some big favour that justifies that stance. This is supported by the corporate lawyers routinely trying to insert heavily one-sided terms into employment contracts. But that simply isn't what an employment relationship is, certainly not in the West in 2020, and enough good people saying "no" and being willing to walk away is the only way the "we own you" people will learn.
Most employment contracts have a section where you declare your existing intellectual property. You can also have this amended after you start working there.
From the Why I Built page:
> Years later, and I've taken a job in software at a large media company. I'll name no names but this company had music brands that were (and are) known globally.
How have you navigated intellectual property to SongBox with your current employer, who it sounds like works in the same industry and who might have claim on some part of what you've created?