[prof_hobart]

> if my new employer hires me for the same role and I am asked to do the same thing again(and I'll mention this work on my resume and interview), I'll do it. Otherwise, what am I gonna do? Make railway engines for them or rockets or weave yards of fabric?

There's a big difference between your old company and your new company both asking you to implement (for example) a unified search box, and your new company asking you if you can think of any clever new features they should implement and you suggesting the unified search box that you've been asked to build at your old company but which is not yet public information. The former is likely to be fine. The latter is fairly likely to be breaching your previous contract of employment.

I've no idea which end of the spectrum this particular case is closer to, which is why it's not a good idea to jump to conclusions before the details are out.

[fakeer]

I doubt the latter case is not a breach of contract IMHO. The thing is, my job is not to implement a search box when I'm told to, but my job is also to tell my employer that a search box is needed when asked about s possible new feature - AAMOF I think the latter is more important part of my job.

An IP or a potential IP(applied or under process for application) is an entirely different thing. This specifically binds you legally not to discuss openly.

And I think even the idea of suggesting a "search box" can be a legal matter iff you had signed a specific contact/nda for that. Otherwise it's well within your general knowledge of your field of expertise for which you were hired in the first place. Ofcourse no one can stop legal trolling.

Jumping to conclusions is a byproduct of discussion. Nothing bad I see in them. As an intelligent species we often conclude based on known facts and (un)intelligent and educated guesses, and often are proved right and wrong. Some ending up in each side.