Live data from Hacker News

Developer Skills Report

research.hackerrank.com

171–180 of 198 posts

Re: Developer Skills Report

#171

> Irrespective of your job, it will become important for everyone to learn how to code It strikes me that the person who wrote that is used to associating with technical people, and might spend a little more time in the real world. I work in a company of 100 ish people, 15 are delivery drivers. 40 odd are sales assistants that customers value for their detailed product knowledge. 4 are involved in cleaning of differe…

Sales assistant jobs are being automated by AI Cleaning tasks are being replaced by robotics With 40% of jobs soon to be replaced by automation, if your colleagues want to stay ahead, they should learn to code.

Re: Developer Skills Report

#172

Earlier quoted context omitted.

I've had to do one whiteboard coding exercise in my entire career. I knew two other devs that had interview at this company, so I knew what to expect. I accepted the in person interview on a whim. I already had accepted an offer as the dev lead for another company. The whiteboard interview was to write out algorithm for a merge sort. I thought it was the silliest thing in the world. I had already accepted a position…

I think part of the reason for whiteboard style interviews is that programmers don’t have a professional body evaluating their programming skills and knowledge like many other professions do. You can have a CS degree without really being much of a programmer. I’ve seen quite a few Masters graduates that can’t program at fizz buzz level. I agree that something like implementing a merge sort is ridiculous. On the other…

> programmers don’t have a professional body evaluating their programming skills and knowledge like many other professions do

Even if there was, no one would trust it. Case in point: ABET will accredit CS programs like they do other engineering programs; not many schools bother because companies don't give a shit about it.

> You can have a CS degree without really being much of a programmer.

You can get a BSEE without being much of an engineer, too. BSEE new grads definitely get tested by hiring companies to make sure they know their shit, but it is nothing like what this industry does.

Re: Developer Skills Report

#173

> Irrespective of your job, it will become important for everyone to learn how to code It strikes me that the person who wrote that is used to associating with technical people, and might spend a little more time in the real world. I work in a company of 100 ish people, 15 are delivery drivers. 40 odd are sales assistants that customers value for their detailed product knowledge. 4 are involved in cleaning of differe…

Sales assistant jobs are being automated by AI Cleaning tasks are being replaced by robotics With 40% of jobs soon to be replaced by automation, if your colleagues want to stay ahead, they should learn to code.

[citation needed]

Re: Developer Skills Report

#174

Earlier quoted context omitted.

Sales assistant jobs are being automated by AI Cleaning tasks are being replaced by robotics With 40% of jobs soon to be replaced by automation, if your colleagues want to stay ahead, they should learn to code.

[citation needed]

The U.S. will be hit worse by job automation than other major economies A new study from PwC estimates that 38 percent of U.S. jobs could be lost to automation in the next 15 years. https://www.recode.net/2017/3/25/15051308/us-uk-germany-japa...

Re: Developer Skills Report

#175

Earlier quoted context omitted.

This is kind of interesting and brings up a question: would you recommend as a technical lead who has powers to hire, that I go on interviews to other companies myself to see what's great and what sucks in their hiring process? Is it worth while?

I didn't purposefully do that, but I've changed jobs three times since 2012, had 30+ phone screens and 6 in person interviews (I keep a Google Sheet). With no rejections (equally due to going through recruiters as my own skill set). So I've had the chance to see what I like and don't like. In my experience, the best type of coding tests are based on creating a skeleton program with failing unit tests already written…

Agreed on this being the best way. Companies using HackerRank can do this process today in CodePair, where the code can be run to ensure the test cases pass and recorded for replay.

Re: Developer Skills Report

#176

> Irrespective of your job, it will become important for everyone to learn how to code It strikes me that the person who wrote that is used to associating with technical people, and might spend a little more time in the real world. I work in a company of 100 ish people, 15 are delivery drivers. 40 odd are sales assistants that customers value for their detailed product knowledge. 4 are involved in cleaning of differe…

Don't be like these people. Keep an open mind, be ready to adapt, and try to just be kind. Kindness is one thing I can guarantee you'll want to have as a skill, in any future.

https://www.pcworld.com/article/155984/worst_tech_prediction...

Re: Developer Skills Report

#177

Earlier quoted context omitted.

I've had to do one whiteboard coding exercise in my entire career. I knew two other devs that had interview at this company, so I knew what to expect. I accepted the in person interview on a whim. I already had accepted an offer as the dev lead for another company. The whiteboard interview was to write out algorithm for a merge sort. I thought it was the silliest thing in the world. I had already accepted a position…

I think half the reason companies can't find talent is: 1. They wouldn't know it if it hit them in the face. 2. They actively repel talent by their interviewing practices. 3. They refuse to learn form this mistake. Since it couldn't possibly be them (they are infallible of course), it must be the talent.

This is 100% true. Earlier in my career I might have jumped through these types of hoops because I needed a job. Today, if a potential employer were to tell me I needed to go write X test program for free or do some bullshit test on Hacker Rank I would just say, "No thanks, I've got better things to do." Then I would move on to the next employer.

At this stage in my career when I still get this type of bullshit from someone I just find it ridiculous.

I'm just left thinking, "Did you read my cover letter? Where I told you how I worked on a 3 million CLOC air flight cockpit software that runs in actual planes; so if there are bugs real people would die? How about the part where I discussed being the software lead on financial derivatives trading software; where bugs could lead to millions or even billions of dollars be lost? Did you see that software library I maintain in my free time that has over 1 million installs? And you still aren't sure I'm qualified? Well no sense wasting any more of your time; I'm clearly not qualified then."

Ironically what I would consider the two best interviews of my career went like this respectively.

1) I was called in for a technical interview. The VP of the IT department sat down with me and asked me to tell him about my work experience. I gave him an overview and then he started delving in deeper and deeper on the subjects that I said I had experience in to see what my level of knowledge was. This went on for about 1 1/2 hours at which point he stopped me and said, "Ok, how much money do you need?" I gave him a number to which he replied, "We could do that. Hold on a minute." The VP then went and brought in his top developer (turns out he's also the hiring director) and then we basically repeated the whole thing, but dove into even more technical details. That lasted somewhere between 2 and 3 hours. At the end of it this he says, "I can have an offer letter ready for you tomorrow. When can you start."

2) Preface - I was referred by someone already working with this company.

I get a phone call from the company CEO (small start-up). He asks me a few questions about my background, some soft skill type of questions, nothing real technical. After 20 or 30 minutes of conversation that is basically just a "can we get along with each other" check the CEO says, "Ok, I'll need you to do a technical interview with our team lead." A couple days later I get a call from the team lead.

The conversation goes basically like this.

Him, "Ok, so here's the deal. Steve says your really fucking smart and Steve is really fucking smart so it's probably true. Elijah (CEO) thinks we need to do technical interviews, but really they're all just bullshit anyway. If it turns out you can't do the job we'll fire you in less than three months; if you actually know what you're doing we won't. So do you want the job or not?"

Me, "Yeah"

Re: Developer Skills Report

#178

> The biggest gap in knowledge is with JavaScript frameworks > Most often, employers want developers who know AngularJS, Node.js, and React. Am I overthinking this? When I've been looking for jobs, I've found the emphasis on JavaScript frameworks slightly perplexing and frustrating. I would assume that a competent web developer should be capable of quickly learning a framework. Having to know JavaScript, CSS, etc. to…

> I would assume that a competent web developer should be capable of quickly learning a framework Well, not that I disagree with you that a lot of employers are being awfully ridiculous when it comes to Angular background requirements, but... you're in for a shock if you try to pick up Angular quickly. Angular is more than a framework - or rather, Angular is a framework that depends on a sprawling ecosystem of other…

That's true, especially the testing part (ever seen chain of promises, a deferred object, and completely useless error stack trace?). Debugging? Source maps, transpilers, file watchers - impenetrable pulp. Why the community is so fixated on forcing the framework down the throat of developers? It certainly solves some problems, but these problems could probably be solved in a more comprehensible and simpler way. Angular it not the new cool thing - it's a complex thing with multiple versions, each incompatible with the others.

Re: Developer Skills Report

#179

> Irrespective of your job, it will become important for everyone to learn how to code It strikes me that the person who wrote that is used to associating with technical people, and might spend a little more time in the real world. I work in a company of 100 ish people, 15 are delivery drivers. 40 odd are sales assistants that customers value for their detailed product knowledge. 4 are involved in cleaning of differe…

Completely agree but I would also agree if you would have said:

None of those people will ever learn to code, or need to learn to code, or frankly be capable of learning to code, neither, we devs, are interested in that..

Re: Developer Skills Report

#180
I feel like the wording misrepresents the results in the "In Demand Qualifications" section.

> There's a popular belief that recruiters favor candidates with CS degrees from prestigious universities. But it turns out that they actually care about what you've done — not where you went to school

But over 40% employers say that they care about your educational qualification. It doesn't' make sense to say "they actually care about what you've done - not where you went to school" with this result. If you don't have a college degree in CS, you're going to have a significantly tougher time getting your foot in the door, so therefore, even if it's not the MOST important credential you need to get a job, it's unfortunately still very important as a pre-requisite. We still don't have a good signal for that kind of preparation if the candidate doesn't have a lot of publically viewable work.

Post reply on HN