Live data from Hacker News

Unfortunately, we'll reject most software developer job applications.

supercoders.com.au

1–10 of 45 posts

Re: Unfortunately, we'll reject most software developer job applications.

#3
post #2

So according to this post, companies are only going to hire the top 0.5% of programmers to their entry-level positions. Something is seriously wrong with this employment model if 99.5% of the labour pool can expect to never find work.

I don't know about all companies, but most of the companies we work with require strong knowledge of OO. There's probably lots of employers who don't really care much about OO. So I think the 99.5% of people will get jobs at places that are looking for different things to what we look for.

Re: Unfortunately, we'll reject most software developer job applications.

#4
post #2

So according to this post, companies are only going to hire the top 0.5% of programmers to their entry-level positions. Something is seriously wrong with this employment model if 99.5% of the labour pool can expect to never find work.

Hyperbole aside, I think what they're saying is that the vast majority of people who apply are, in fact, not actually software developers.

Perhaps they are looking for some kind of job, and because they know how to type, that must mean they can code. Since coding is just typing, right? (how many of us had bosses at one time that thought this!)

If you can't answer those 5 questions, then I would wager you've never actually written an OO program, you've never attended a single undergrad COSI course, or you don't speak English.

Re: Unfortunately, we'll reject most software developer job applications.

#6
I think it's hard to give answers that are both accurate and concise to some of these questions, without appending "in language ______" to them. In some languages, access control is a compiler feature and is actually strictly enforced. Objective-C has access control for instance variables, but not for messages, and the ivar access control can be circumvented via the runtime (to say nothing of -valueForKey:). "Private" messages are typically declared in the implementation file or a second header. Python sort of has private methods through name mangling, but they aren't really private, since we're all adults. In Ruby, those words mean something fairly different.

Re: Unfortunately, we'll reject most software developer job applications.

#8
It's worth noting that answers, particularly if you expect accurate ones, would be different depending on the language being considered. For example, private in Ruby is similar to protected in Java. But pedantry aside, those are fair questions for programmers.

Re: Unfortunately, we'll reject most software developer job applications.

#10
It's just a publicity stunt. Some of their questions do not have answers that are both clear and concise because the language specifications themselves are not both clear and concise (in some cases they're neither). It's a classic example of people trying to make themselves look/feel smart by demanding that others' off-the-cuff answers meet a higher standard that their own researched-at-leisure questions. The proof lies in the fact that the answers are language-specific but "SuperCoders" apparently can't meet their own "accurate, clear and concise" standard in identifying that context.
Post reply on HN