Everyone I've talked to in the industry views people with a Masters much less favorably than people with a Bachelors or PhD.
And from experience I can say there is a shockingly high number of people with Masters in Comp Sci churning through the hiring pool who can't write a single line of code or even valid HTML.
I don't know why this is, but I think a Masters is getting a negative reputation to the point that you might consider not listing it on your resume at all in certain cases.
Getting an MS is a sign that the candidate wasn't particularly good before getting one, because of the various reasons people get an MS. And it's not like they became a better developer as a result of getting one.
The way to determine this is by measuring actual performance.
With more information, like why or how they got an MS, the probability distribution changes. My impression is, there's a set of dimwits from a dimwit part of the industry that decide they should get a Master's in order to better their career. As opposed to, say, getting one right after school because you didn't want to enter the real world, or because a 5-year MS seemed like a good idea, or being brainwashed in general about the value of formal schooling.
And from experience I can say there is a shockingly high number of people with Masters in Comp Sci churning through the hiring pool who can't write a single line of code or even valid HTML.
I don't know why this is, but I think a Masters is getting a negative reputation to the point that you might consider not listing it on your resume at all in certain cases.