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?

22 of 224 comments (clear)

  1. Are you patenting software? by Anonymous Coward · · Score: 4, Insightful

    If so then fuck off.

    1. 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.

    2. Re:Are you patenting software? by NetCow · · Score: 4, Insightful

      Those patents disclose algorithms. Basically, applied math. Which should have never, ever been allowed as claims in a patent since they are antithetical to the compromise between the inventor's and society's benefit the patent system was designed to facilitate. So, yes, they are pretty much what one would call "software patents".

      Whether or not they describe revolutionary ideas, and whether or not they required creative thought to invent is completely beside the point. Patenting algorithms runs against the very worldview that built the research scaffolding which allowed you to come up with these ideas (the old adage about standing on the shoulders of giants--and now imagine a world where those shoulders could only be visited if you paid the piper.) Math isn't invented, it's discovered.

      That being said, under no circumstances would I recommend a client to hire you if I caught wind that you owned patents applicable to the field in which you would be working. That simply screams "conflict of interest", "subsequent lawsuit", and "humongous liability."

    3. Re:Are you patenting software? by ZahrGnosis · · Score: 4, Informative

      No, I didn't patent those ideas, the links were examples; but I completely agree that the patent system is failing, and I pointed that out. The question is how to deal with it. I think it's a valid approach to continue to patent ideas until the issue is fixed because the mixed-bag approach is very difficult.

      The EFF agrees at least that the situation is not black and white... from their site: "While [abandoning patents is] compelling, there are risks to this strong approach. Every piece of software released to the world without legal protections may leave open a door for someone else to attempt to patent the same technology (and may leave its creators more open to legal threats without a patent to wield defensively)." (https://www.eff.org/patent).

      I am genuinely not trying to get rich (well, not through patent evil or trolling), or to be exploitative, and while I don't want to contribute to the problem, I don't want to be a victim of it. Anyway, I appreciate the comments, but again I was trying to shy the focus away from software patents... much ink has already been spilled on that topic. Assuming the patents were one that met your complete approval, would you feel differently?

    4. Re:Are you patenting software? by linuxrocks123 · · Score: 4, Informative

      I'm not sure how one might think patents on methods of optimizing database queries would not qualify as software patents. As someone else said below, it's applied mathematics. Heck, the "relational" part of "relational database" comes from the theory of set relations. And if databases are your field, you know that. And if you'd donated the patents to the EFF, then you wouldn't be asking this question.

      Trying to play devil's advocate the only counterargument I can come up with is, "the optimizations are useful because of the way this particular computer is architected." But that's silly; much of number theory is useful and studied because it's applicable to cryptography. Being useful in an engineering situation doesn't turn mathematics into engineering.

      I don't believe in telling people to fuck off for asking an honest question. At the same time, I'm not personally inclined to help you with your problem, because you're asking with help engaging in an antisocial activity. The weird thing is, from your comment, it seems we're in agreement on that, but you don't see that what you're doing is what we both believe is wrong. Dude, those kinds of patents are the types of things most software developers talk about when they mean software patents. Amazon one-click and Microsoft's FAT patent are just talked about more because *EVERYONE* runs into those, whereas only compiler developers run into the asinine register allocation patents, and only database developers run into yours. But they're still bad, just bad in a narrower field. Look up the history of register allocation in GCC and LLVM if you want to see what patents can do to OSS. LLVM uses linear scan register allocation, which is faster than the standard graph coloring algorithm, but worse-performing. Guess which consideration is most important in 2014 when you can compile on 16 CPUs at once? GCC, as usual, does something totally fucked up because it's been around so long accumulating cruft, but its algorithm was originally designed around exactly the same patents LLVM had to design around.

      Again: software patents have crippled open source compilers' register allocation algorithms from the dawn of GCC to the rise of LLVM. How disgusting is that? And the register allocation patents are what happens when we're aware of the patents and they're held by an OSS-friendly company (IBM).

      If you're not going to stop patenting software, but you care about the ethical implications of your work, my minimal request to you would be to donate the patents somewhere like the EFF or FSF in your will. If you don't, your heirs might decide to sell your work to SCOracle and you'll fuck up every OSS database for a LONG. TIME. I'm sure you don't want that to be your legacy.

      And btw, if you haven't, you should have your estate planning done anyway. Everyone with even a small amount of assets should. Shit happens, it's not as expensive as you might think, and a competent attorney will also prepare "collaterals" where you say, among other things, what you want to happen if you end up like Terri Schiavo. And if you're not aware of why you really need to make that absolutely clear in a totally legally binding way ... just look at the Wikipedia article for "Terri Schiavo".

      --
      vi ~/.emacs # I'm probably going to Hell for this.
    5. Re:Are you patenting software? by smaddox · · Score: 3, Insightful

      Or you could publish the method/algorithm in a journal. Nothing already published qualifies for a patent. Having your name on (high quality) journal articles also can't hurt your job prospects.

    6. Re: Are you patenting software? by TheP4st · · Score: 3, Funny

      And also the abuses of software patents cause economic harm that FAR outweighs the benefits.

      Indeed, just look at all the productivity that goes to waste whenever /. posts an article containing the word patent. In a nanosecond hordes of well paid tech professionals stop coding, innovating and creating just to read through all 389 posts and post a couple of their own. By the time they are done posting others have posted too, generating a whole bunch of new posts that have to be read and replied to, severely delaying the calculation of the Ultimate question

      --
      "I have downloaded hundreds and hundreds of records, why would I care if somebody downloads ours?" Robin Pecknold
  2. IP is licensed separately. by Animats · · Score: 4, Informative

    Yes, you should explicitly refuse to implement your patented IP for the company without a separate licensing fee. This is completely separate from employment.

    In particular, you don't want to use your IP in their product without a licensing deal in place. That creates a conflict of interest situation, one likely to result in litigation later. What if, later, you sold your patent rights to another party and they sued your employer? Your employer could then sue you for putting them in that situation.

    Bring in a lawyer. Welcome to the big time.

    1. Re:IP is licensed separately. by shrikel · · Score: 4, Interesting

      probably best not to mention any patents you are holding

      Mod parent: -1 (Bad advice)

      Frank, honest communication is one of the pillars of a lasting business relationship. Hiding things from your employer is only likely to cause more problems later when it comes out, with potential consequences ranging from a soured relationship with your boss all the way up to an expensive, bitter lawsuit. (Not to say you'd lose the suit, but I can certainly see it happening, and it's something you don't want to be involved in.)

      Definitely bring it up, and definitely make separate arrangements for use of the IP. I would have that complement your salary rather than being a part of it. Not only is there the chance you might sell the IP elsewhere, but what happens when you leave? On either good terms or bad? As an employer, if I hire you, it's because I think you (and your knowledge / capabilities / skills) will be an asset to the company. I would not put myself in the position of bringing you on, becoming dependent (to any degree) on your IP, and then having you rip that out of my company when you leave.

      Granted, on some level we employers EXPECT to become dependent on some level on our new hires' skills and abilities. But that particular person we hire does not have a monopoly on skill or ability, so if they get hit by a truck / leave / whatever, they can be replaced, though perhaps not easily.

      With patents, you DO have a guaranteed monopoly on that particular benefit you can bring to the company. If you were applying to work for me, I would want to arrange -- perhaps parallel to your salary -- a separate licensing agreement for the IP. At the very least, I would require a perpetual (or at least renewable-at-my-option-under-original-terms), non-exclusive license to any IP that make their way into the business's core operations. I'm not saying I'd require that for free, but without the guarantee that bringing you on wasn't going to cripple me in the future, I would definitely not hire you at any price.

      The simple fact that you were capable of developing the patented methods that I find important adds to your value as an employee, and therefore to the salary I'd be willing to pay.

      Disclaimer: I consider myself a high-integrity businessperson, so I could be overlooking some way that a scoundrel would try to take advantage of you. Get a lawyer's advice on the contract. And don't apply to work for any scoundrels anyway, because that's just asking for trouble. ;)

      --
      Any sufficiently simple magic can be passed off as mere advanced technology.
  3. Leave them off your resume. by khasim · · Score: 3, Insightful

    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.

    If it is not part of the deal then leave it off your resume.

    My question is, how should I treat licensing of the patent as a topic with respect to the topic of my employment?

    I think you are confusing two different situations in an interview situation.

    1. You working for a company.

    2. A company licensing your patents.

    Leave the patents out of the process at this point.

  4. 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.

  5. Separate by Moof123 · · Score: 3, Insightful

    If you want to money for use of your patents, go sell patent licenses. If you want a job, be clear that you are there to work and your patented work is off limits (I am assuming you personally hold the patents). When we interview patent holders I grill them on the patent since it is clear piece of representative work I have access to, but I have never considered that their patents come along for the ride (usually they are owned by some other company).

    When it comes to proprietary IP that is not patented, I steer a wide berth to avoid any chance of making it look like they need to share their protected knowledge to pass the interview. If it is on their resume I generally ask for enough description to understand the gyst of what they are working on and will ask industry standard design questions, but I do my best to stay far away from anything that makes them squirm.

  6. Talk to a lawyer by Vladus2000 · · Score: 3, Insightful

    Seriously, talk to a lawyer. I am not at all versed in various IP /employment laws and I assume you are not either. I have no idea what can go wrong, but you need to know these things. Have that lawyer read anything you are going to sign. You do not want to sign away your rights accidentally. Once you know the finer details of the relevant case law, you can decide how you want to approach it. If you are an employee and you do not want to share your patents and your employer uses them anyway, what happens then? Are you going to sue your employer? Corporations are soulless entities that will suck whatever life/power out of you that you let them. Work on the assumption they are out to screw you and prepare appropriately.

  7. Create a LTD company by Anonymous Coward · · Score: 4, Interesting

    Hi
    Why don't you create a limited company, then you sell your patents to [your|the] company for an undisclosed sum and then pretend you had success in patenting and selling your patents.
    You achieved two goals: You can put your legitimate patents in your CV and the patents are not part of the deal because they are now in the hands of a legal third party.
    Cheers
    Nicola

  8. Consult a lawyer by angel'o'sphere · · Score: 3, Interesting

    Obviously employment and patent licenses are two completely different things.

    Bottom line you basically could lead your new employer into a situation where 'he' is infringing 'your' patent.

    Obviously it could be opposite around.

    I would not trust any /. advice, except: consult a competent IP/patent lawyer.

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  9. Duh! by Greyfox · · Score: 4, Funny

    You should implement your patented IP and then when you leave you should sue them for patent infringement!

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

    1. Re:Duh! by Greyfox · · Score: 3, Funny

      Yeah! I mean think about it! If you're a patent troll, are you going to get more business by sitting back and hoping someone invents the thing you patented, or are you going to get more business by sending out an army of coders to make SURE something you've patented gets invented? Ah it's such a brilliant idea I should go get a business process patent for it!

      --

      I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  10. License them and they are a plus by Anonymous Coward · · Score: 4, Insightful

    The idiots that tell you that they would never hire anyone who has a patent are just that, idiots.

    I own a successful company with nearly 100 employees. The fact that you have patents shows that you're not just a run-of-the-mill employee like these wannabes who are decrying the fact that you have a patent. Of course if you come to work for me, you will sign an agreement signing anything you invent while you work for me to my company. That is part and parcel of the deal these days. I would not consider you to be a problem employee I would hope and expect that while you work for me he would generate patents for me. If the idea of generating patents for me and not getting any other benefit out of it chafes at you, then you should not be out searching for a job. You should instead find a way to monetize and licensure patents so that you can work as an individual inventor and secure more patents for yourself.

    If your patents were somehow relevant to my business, then we would potentially have a separate discussion about licensing. If you got the patent and you own the patent then any financial value to it is yours not mine. I think it is wrong of me is employer to expect you to just give me the use of your patent. If you feel like it, then go ahead. Especially as some have mentioned if it's a dream job and the commercial value of your patent is not much.

    If your patent was somehow a fundamental advantage to my business, I would want to license it from you and keep it out of the hands of my competitors. Or at the very least negotiate most favorable terms from you.

    So no, I see no situation where you owning a patent would be a disadvantage. Unless, of course, you're trying to get a job with some Slashdot pinhead.

  11. 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?

  12. Re:You guessed it: It depends by arth1 · · Score: 3, Insightful

    It's worse than that. If the company you apply for a job at has any interest in the patents, chances are that they will not offer you a job.
    The problem is that you selling/licensing patents to them while an employee will easily be seen as a conflict of interest.

    If they want you and the patents, I believe they may require you to sign over any and all IP to them as terms of employment, compensated by a signing bonus.

  13. Patents, employment, and invention by Immerman · · Score: 4, Insightful

    I think that would depend on whether you were producing new inventions while in their employ, or simply licensing preexisting patents to them. I don't see any conflict of interest in the latter.

    In fact that brings up another important, and related, issue - look at that employment contract *carefully*, it's quite common for an employer to claim ownership of all "IP" you produce while you are in their employ, including stuff created completely on your own time. The rationale being that you were probably at least thinking about it on their time. Supposedly most employers are quite negotiable on that bit beforehand, they may even have alternate contracts at the ready, but if you don't catch it when you sign your contract then they've got you by the short hairs.

    --
    --- Most topics have many sides worth arguing, allow me to take one opposite you.
  14. Re:"headofficed" - LOL by BVis · · Score: 3, Informative

    Verbing wierds language.

    --
    Never underestimate the power of stupid people in large groups.