Slashdot Mirror
Ask Slashdot: Finding a Job After Completing Computer Science Ph.D?
An anonymous reader writes I recently completed my PhD in computer science and hit the job market. I did not think I would have difficulty finding a job esp. with a PhD in computer science but I have had no luck so far in the four months I have been looking. Online resume submittals get no response and there is no way to contact anybody. When I do manage to get a technical interview, it is either 'not a good match' after I do the interviews or get rejected after an overly technical question like listing all the container classes in STL from the top of my head. I had worked as a C++ software developer before my PhD but in the past 6 years, software development landscape has changed quite a bit. What am I doing wrong? Has software development changed so much in the last 6 years I was in school or is my job hunting strategy completely wrong? (The PhD was on a very technical topic that has very little practical application and so working on it does not seem to count as experience.)
>technical question like listing all the container classes in STL from the top of my head
Do experienced devs even know this? I've programmed in several languages and I could never give a list of functions on demand. That's what reference material is for.
You honestly dodged a bullet with that one; any company that asks for such a thing has a damaged tech culture.
I know it's sad, but hide your PhD. Most employers are scared of PhD's for multiple reasons: (1) they don't want to pay them what their credentials demand , (2) many hiring bosses are intimidated or feel threatened to have an underling with more education than they do, and (3) they are probably hesitant to invest in someone who is so highly credentialed for fear of losing them when a sweet offer comes around. Sad, I know. But I'd go ahead and hide the PhD. (Disclaimer: I'm working on mine now)
Surely your advisor has links to industry? Where does the funding come from? Industrial consortia? Federal sources (NSF / DOE / etc). Can you look at doing a postdoc at a National Lab so you can make some contacts? If you don't, ask your advisor for help. It is the least he or she can do for you.
I don't think resume sites are good places for a newly minted PhD to look for work. You surely did some networking while you were a student. Did you present your research at some conferences? Those are the people you should be talking to about work, not filling out on-line applications. At the PhD level you find work based on a personal network, not web-based applications (although you will need to fill those out for compliance).
It's not fair, but it's probably better to just list your master's for now.
Right now they figure you won't be happy with a junior position, but you don't have the experience from them to trust you with something more senior. Once you've got a bit of experience put the PhD back on. It will help you land more senior jobs later.
It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow
Or more pertinent to a PhD in particular is: what was your focus? A PhD isn't like a BS or even MS, it almost always reflects a near unique level of understanding something. What was it? What was your thesis? Why are you not working on that, in particular?
There's the solution: Pose as a $1500/mo. Indian PhD. Practice the accent.
Table-ized A.I.
I've conducted a lot of interviews (in an academic setting in the humanities), and I can say that it's risky guessing what exactly the interviewer is trying to accomplish with a question. Sometimes a question is asked neither to see if someone knows the answer to the question nor to see the content of the interviewee's answer, but to see how the person handles being asked such a question. I could see someone deliberately asking a question that he know the candidate not to know the answer to just for such a purpose, though personally I would avoid doing it as it's neither nice nor useful to stress out the interviewee even more (but I might do it in a mock interview preparing someone for a real interview).
So the interviewer might be interested to see if the interviewee honestly, humbly and politely says: "Would you like me to tell you the container classes I use the most? The others I have to look up when I need them", or if the person pretends to know the answer, or rudely bristles, or tries to weasel out of the question by changing the topic (of course it might be a bonus if the interviewee actually has a great memory and knows all the container classes; but then another question might need to be asked to gauge character).
How do you then explain the 6 year gap in your resume?
You could say that for the last six years you were a volunteer jihadi for ISIS. That would be bad, but it would cover the gap, and would not be as bad as admitting that you have a PhD.
Any place that shuns someone with a masters degree is pretty sucky, I feel sorry for you. There are many companies that value people with education. Do you really think at the CTO and architect level that they prefer BA to BS, and BS to MS, and MS to PhD? Granted, fresh graduates don't get those jobs but people do work up to them. Not everyone is in the trenches forever doing coding that other people tell them to do, eventually there's someone in the company that has to actually know something, if the company is worth anything.