Hello, I am interested in pursuing a Masters in Math and was wondering if employers (for those requiring a MSCS) would consider an MS in Math to be equivalent to an MS in CS. Any thoughts? I am currently a Java Developer with about 4 years of experience and also hold a BS in CS. I've thought about going for an MS in CS to make myself more marketable but I am more interested in a MS in Math but was concerned by how it is viewed by employers. Thanks to any of your responses!
A friend of mine works at Lockheed and his programming job is HEAVILY math based. I'm sure other defense jobs like Boeing would have similar job requirements. I think an MS in Math could be quite valuable. However -- I would try to take electives in CS, just to make sure that programming companies still look at you. Look for classes like Algorithms, Computer Algebra, or AI could be quite valuable and would compliment your Math degree too.
master of science in Mathematics can go into field of computational mathematics and maths related stuffs in computer , I know for computer graphics like imaging and 3D stuffs in computer science involves lots hard maths equations and need a good maths background. maybe u do both MSCS and MS maths.
BEA 8.1 Certified Administrator, IBM Certified Solution Developer For XML 1.1 and Related Technologies, SCJP, SCWCD, SCBCD, SCDJWS, SCJD, SCEA,
Oracle Certified Master Java EE 5 Enterprise Architect
You are going to be reasonably well equipped to learn a living whether you have BSCS/MSMath or BSCS/MSCS, or just the BSCS for that matter. My bet is that you'll be happiest long run by following your interests. If you are interested in getting a math degree, there is a good chance you will be happier working for someone who appreciates the math degree than for someone who doesn't. [ April 03, 2004: Message edited by: John Dale ]
I agree with John completely. But I don't see a MS Math to be equivalent to MSCS. If it was, it would be called MSCS. That said, I can point out a dozen or so developers or architects that that have economics, history or other non-related degrees and are damned good. The ability to communicate effectively should not be underestimated. We try to use UML to takes us as far as we can, but at the end of the day, clearly communicating in english is absolutely key. Projects dont continually fail because some team didn't have the requisite knowledge in Java (or whatever technology). Projects nearly always fail due to communication related issues (usually in the form of "I liked you what guys built, but that's not what we wanted or asked for").