7 ms·
Here's a list of reasons I've heard for having my resume screened out: * Didn't study CS. * Didn't go to "brand name" school. * One of my job titles (which c
by pmiller2 11y ago
Here's a list of reasons I've heard for having my resume screened out:
* Didn't study CS.
* Didn't go to "brand name" school.
* One of my job titles (which currently comprises half my software experience) doesn't say "software engineer" or similar on it.
* You know Python; we use Ruby (or similar)
It gets demoralizing after a while, That's the main reason Patrick is right about bypassing the resume black hole. It just doesn't work. I seriously wonder about the number of interviews I would have gotten had I crossed out the school I went to and written "Stanford" or "Berkeley EECS."
I've got 3 years writing Python software, so it should start getting a little easier (and it has -- very little).
PS I'm looking, and my email is in my profile if anyone wants to chat a bit. :)
- jszymborski 11y agoIt's too bad to hear that, and a surprise to me... always thinking that it was an applicants market. Also, python didn't strike me as a hard-to-sell language.
- potatolicious 11y agoIt's absolutely an applicant's market... if your profile fits within an extremely narrow window of what companies are interested in. The tech industry is largely a group of companies competing to outbid each other to hire a small pool of "credentialed elite" developers for lots of money, and everyone else.
- vinceguidry 11y agoPython's weird in the ecosystem of languages. It's way more of a hobbyist language than it lets on. Since, as Patrick writes, most dev jobs are for line-of-business apps, and Python occupies a very very small niche in that world, very few devs can specialize in Python and hope to easily find a job if they present themselves as a Python specialist. Data science might change things, but it's still a very new field. If you're looking for a dev job, you should learn Ruby unless you have an irrational disdain for it. It's close enough to Python to be a fairly easy switch, but it will raise your position considerably in the job market. But really, you should take Patrick's advice and not present yourself as an X developer. I do because I want to work primarily with Ruby and Rails, but when I was starting out, I presented myself as a competent engineer that could get up to speed effectively with any framework. I got a .NET job that way, having no former experience in the stack. Got fired in three weeks, but I still got paid. Now I do Ruby exclusively, and have no trouble finding opps.
- switch007 11y agoI'm not sure about the UK. Python, according to these job-regex-match statistics, seems more in demand: itjobswatch.co.uk: number of jobs in the past 3 months citing ruby: 2,766, python: 6,013. Rank table: http://www.itjobswatch.co.uk/IT-Job-Market/UK/Programming-Languages http://www.itjobswatch.co.uk/IT-Job-Market/UK/Programming-La... GB section on this page put Ruby mentions at 3% and Python 6% https://gooroo.io/GoorooTHINK/Article/16300/Programming-languages--salaries-and-demand-May-2015/18672 https://gooroo.io/GoorooTHINK/Article/16300/Programming-lang... EDIT: indeed.com, ruby vs python: http://www.indeed.com/jobtrends/ruby%2C+python.html http://www.indeed.com/jobtrends/ruby%2C+python.html Does anyone know where else to get data (not anecdotes)?
- tetraodonpuffer 11y agowhat does "citing" here mean? in my experience if a job has, say, ruby, odds are it's a ruby job, if it has python often it's a job on something completely different where at the bottom they put "familiarity with scripting (python, perl) is an asset"
- morgante 11y agoIf you're actually working as a developer, you really shouldn't be a "specialist" in any language. That's like a carpenter who can only work with one kind of drill.
- vinceguidry 11y agoDepends on what kind of career you want and what you're hoping to get out of it. For me, a career is a tool I use to enable my life. Regularizing it as much as possible is worth it for me. Languages don't just disappear. People still make fine livings programming Fortran. If I'm going to keep programming for 20+ years, I'd be happy to be one of those guys. I'd rather move into business, but if for some reason that never happens, being a specialist in a deep niche holds a deep appeal for me.
- pmiller2 11y agoI've applied cold for jobs where every one of the requirements matched a point on my resume and didn't get so much as an acknowledgement.
- anexprogrammer 11y agoHere's a few I've had * Needed 5 years experience of 4 year old framework, you only have 3.5 * Didn't mention vi. I was convinced this was excuse, phone call to recruiter seemed to indicate dense recruiter and he thought it as important as mentioning C++ or Java. Why it mattered was another thing. * You don't mention specific flavour and minor release of OS. * You don't mention degree. I'm past 40, why does this still matter? In fact you're the first to ask in 15 years... Not to mention all the false positives from interfacing with some other language or app. Memorable interview - Recruiter had completely falsified my CV and given me a ton of experience I simply didn't have along with taking away a good chunk I did have. 5 mins in and it was an obvious farce and I handed interviewer an accurate CV. We had a bit of a chat and agreed it wasn't something I'd want or they'd offer.
- duderific 11y agoOn the degree thing... I recently got pretty deep into the interview process at Google. I got through the interviews and did well enough to be recommended to some departments. The Payments team was interested in me based on my interview results. Then, my information (resume and interview results) gets handed to the "hiring committee". They needed some more information: specifically, what my years of undergrad were (although that was already on my resume) and what my freaking GPA was (that wasn't). Suffice to say that although I went to Berkeley, my undergrad degree was not CS, and I guess my GPA wasn't high enough because I didn't get an offer.
- mywittyname 11y agoPerhaps companies are really telling you that they have so many more obviously qualified applicants that you probably won't beat out the other candidates, even if you are perfectly qualified for the position. It's like being picked for a basketball team. You might be able to nail three-pointers all day long, but if you're only 5'8, be prepared to be picked last. It's even worse with recruiters, because sending a bad candidate has the potential to lose them out on a lot of future business. So they have a huge incentive to play it safe.
- napoleond 11y agoEmail incoming :)
- rahimnathwani 11y agoYour profile doesn't mention where you are based, or the range of locations in which you would be willing to be based.
- olavgg 11y agoTwo years ago I applied for a a month contract as a JavaScript developer for a Microsoft .NET shop. At that time I had 7 years and several big and small projects with JavaScript experience, and a few .NET projects. They were not interested because I had a lot more experience with Java and Linux than with Windows and .NET. Lesson learned, now I hide less relevant experience and highlight the more relevant experience. The "holes" is my resume can always be explained later.