3 ms·
Why would you list the .NET version on your CV? Why would anyone hiring care about whether you have experience with .NET 6 vs .NET 3 Do you also list all the l
by ahtihn 4y ago
Why would you list the .NET version on your CV? Why would anyone hiring care about whether you have experience with .NET 6 vs .NET 3
Do you also list all the library versions you've worked with?
This is pretty absurd.
- danparsonson 4y agoThe .NET framework has changed a great deal between versions 1 and 6, so I don't agree that it's sufficient just to say that I am experienced with .NET and leave it at that, nor is it equivalent to listing library versions. Besides I'm a contractor; potential customers are usually looking for someone who can hit the ground running, not spend a month skilling up.
- nightski 4y agoIf a recruiter denies you because you have .NET 6 on your resume instead of .NET 7 then that probably isn't a very lucrative job in the first place. You don't need a month of skill up to go from 6 to 7, maybe like 10 minutes. Personally I'd just say .NET in general and leave the specifics to the interview.
- ewjt 4y agoIt’s a minor signal, but it’s still a signal. If someone only lists “Angular”, it could be Angular 4 from 2016 or something more relevant. Same thing with .NET— the version can imply Windows-related experience (.NET Framework) vs. something more cloud native (.NET 6).
- barking_biscuit 4y agoI guess it's useful to know whether or not a candidate is 15 years out of date. We had a guy come through who knew classic ASP and I'm told it was a painful interview.