I would say, from my experience (3 years in enterprise software dev) if you don't understand LINQ, you shouldn't put C# down.

C++/Java/C# are not that different at the language level(although, I would say that C# is the most friendly of the bunch), but the standard libraries make all the difference.

Right, right now I don't even list it. I was just wondering as I learn it, and being that I already knew how to code, when I would be good at it. I wasn't sure how much was out there to know.

In all likelihood if you are good at C++, you would be good with C# - 90% of the code you write will be similar and you can look up what the C# equivalent of std::vector is, etc.

But, employers know good programmers can transfer to new languages (good employers anyway) so on your CV it's more to show how much experience you have, rather than how good you are.

Adding that you're interested in and self-training in C# might look good, somewhere in your CV or covering letter, as it shows a real interest.

In all likelihood if you are good at C++, you would be good with C# - 90% of the code you write will be similar and you can look up what the C# equivalent of std::vector is, etc.

Yes. If you've got a good team and a good mentor you'll pickup what they are doing in the first month without too much trouble. But that's not a guarantee.

I could ask you some interview questions about Java that your C++ skills will not help with, so just be honest. I learned on C++, and I though Java was a slow, silly language. But within a few months I grew to love it, and have been using it for a long time.

I will also point out that unless you've been doing correct OO programming with C++, the transition will not be without some trouble. C++ lets you break all kinds of rules: global variables, friend functions, unions, pointer arithmetic, function pointers, casting void* arrays, and all kinds of other things with constructors, destructors, lack of garbage collection, no integrated threading or synchronization library, and a different compile/link/deployment paradigm.