Slashdot Mirror


Ask Slashdot: Handling Patented IP In a Job Interview?

ZahrGnosis writes I'm in the midst of a rather lengthy job interview; something I haven't done for some time as I've worked as a contract employee with a much lower barrier to entry for years. Recently, I've started patenting some inventions that are applicable to my industry. One hope is that the patents look good to the prospective employer on a resume, but I don't want them to take the existing IP for granted as part of the deal. I'm worried I have the wrong attitude, however. My question is, how should I treat licensing of the patent as a topic with respect to the topic of my employment? Should I build the use of my patented ideas into my salary? Should I explicitly refuse to implement my patented IP for the company without a separate licensing fee? If I emphasize the patent during the interviews without the intent to give them the IP for free, is that an ethical lapse — a personal false advertising? At the same time, when I work for a company I feel they should get the benefit of my full expertise... am I holding back something I shouldn't by not granting a de-facto license while I work for them? I perceive a fine balance between being confrontational and helpful, while not wanting to jeopardize the job prospect nor restrict my ability to capitalize on my invention. Thoughts?

3 of 224 comments (clear)

  1. Patent attorney chiming in by reebmmm · · Score: 5, Informative

    The real question is: are you applying for a job or are you trying to license your technology? In all likelihood, a blended negotiation is probably not going to happen unless: 1. you're looking for work in academics/advanced research or 2. you're a pre-eminent engineer/scientist being hired for your contributions in your inventive space.

    If you're applying for a job, then the recruiter probably doesn't want to hear your invention pitch. The recruiter probably doesn't care about your patented stuff other than perhaps an aggregate count: e.g., I'm a named inventor on 3 million patent applications. You should be focused on what your qualifications for a job are.

    If you're afraid that once you get the job that you're going to be deprived of a subsequent royalty stream, you should review your employment contract and should just flag that as a concern of yours. I suspect you're unlikely to get much value for your IPs from your employer, but at least the paperwork will be clear as to rights to use, the existence of the inventions prior to employment, etc.

    If you're talking about trying to license your technology, then you need to talk to the right people. Probably their patent attorney or the person in charge of in-licensing technology. This is usually a protracted negotiation.

    Last point, on your moral quandary: your patent probably doesn't stop you from deploying your full efforts at a job. It might stop you from implementing your own patented invention. But, on that point, you're the gatekeeper of your own invention. If you elect to deploy your patented invention as part of your regular work, you shouldn't expect compensation for it unless your employer asks you to.

  2. Re:Are you patenting software? by ZahrGnosis · · Score: 5, Informative

    I almost put a note in the original question about that, but I decided not to, in an effort to keep the talk on topic. So let me point out my stance. First, I'm against software patents and frankly I think the whole patent situation needs reform far beyond software patents. At the same time, if something is patentable, I'm not sure anyone should avoid patenting the idea simply because you disagree with the system. I'd rather patent them and donate the patents to the EFF and GPL an implementation. On the other hand, I want to avoid a situation where for-profit companies co-opt the idea and charge people for it. Maybe I'm not altruistic enough; I'm conflicted on it, honestly. I haven't quite gotten there yet, though, so in order to not turn this into a flame war I skipped the topic. Anyway, here we are, and I'm trying to respond thoughtfully rather than just, as you say, fuck off.

    To answer you point, though, some of my ideas are similar to these patents... decide for yourself if these are deeply "software patents": https://www.google.com/patents/US6263334, https://www.google.com/patents/US20030187867, and https://www.google.com/patents/US7185023, and I'd love to get feedback on how to deal with that aspect of the issue.

  3. Re:You guessed it: It depends by Jane+Q.+Public · · Score: 5, Insightful

    For each job it will be different.

    No, and no.

    Patented IP belongs to the patent holder. Employment is a different issue altogether. Under normal circumstances, they are legally completely separate issues... so why would you want to mess that up?

    If you want employment, make an employment agreement. If you want to sell, lease, rent, or royalty-license your patents, then do that.

    Why would you want to confuse these things and mix them up?