News for hackers. Stuff that matters.
Re:I spent three months working full time to get a job by mr_tristan on Saturday March 04, 2017 @08:36PM (#13794113)
My current company used a "homework assignment" and they bought a lot of my trust with it.

1. The "assignment" took me about 4 hours, which they expected and told me off the bat. 2. It involved mostly relevant code with 1-2 wrinkles that were not odd just not everyday sorts of things.

For the proceeding interview, I was able to sit with 3-4 engineers for 1-2 hours really just diving into details about my experience and their processes, etc.

So if I could offer advice it would be to find a "homework problem" your existing crew could build independently in 4 hours or so. As in you've actually had more than 1 team member attempt the request, and they did it in about 4 hours each.

This was actually an interview process I didn't mind. I have 15-ish years of experience doing development. I can spare half a day for a prospect no problem. It was actually kind of fun.

4 hours seems to be a good "sweet spot". You can ask something sufficiently technical and oriented to the daily work without being a bore. And when the interview comes around, you can make sure it's not some ego-bound contest, more of a conversation.

Re:I spent three months working full time to get a job by lbatx on Saturday March 04, 2017 @09:42PM (#13794296)
At my previous company, I was the hiring manager and gave a homework assignment that was targeted a little shorter than you describe, at right about 2-3 hours. I was clear upfront that it would take about that long, though if you wanted to take longer, you could. Within reason, I didn't hold the time against the person if they took longer.

The crazy thing was that over half of the applicants that passed a resume screen and phone interview could not complete the homework assignment. Over half. Some couldn't get it at all (either gave up or had compile errors), some got it to run but it didn't work, a few got it to mostly work but their programs had serious bugs, and the last few actually got it right.

The assignment was to read a file containing a list of numbers (some formatted incorrectly, so there was some very simple parsing logic involved), call an API using each correctly formatted number as a parameter, and store what the API returned to a file.

I'm still shocked over half of developers couldn't accomplish that task. Makes me wonder what they were accomplishing in their existing roles.

Re:I spent three months working full time to get a job by hinkley on Sunday March 05, 2017 @05:05AM (#13795337)
The last two Homework assignments I got took about 50% longer than the hiring person suggested they would take.

I'm perfectly competent at writing complex code. In fact I'm usually the guy who fixes bugs or perf issues that nobody else believes exist.

A problem you came up with on your own is going to seem simpler to you than to everyone else. Why? Because you thought you picked it at random but your subconscious picked the one it thought was good. In other words, you picked the one you were already primed to answer, and it seemed simple.

So either people are going to work at it longer, the timid will give up (there's nothing wrong with timid coworkers as long as they have someone to listen to them), and the brash will get it done in the time allotment by cutting corners.

Are those the people you were trying to hire? Because that's who you're gonna get.

Re:I spent three months working full time to get a job by chillydawg on Sunday March 05, 2017 @06:23AM (#13795526)
I'm sorry but the problem is a trivial one. Even if you've never read a file, never made a http call in code or written to a file, these are all things a 5 minute stack overflow away.

I absolutely would not hire someone who failed that test. Your defence of it seems bizarre to me.

Re:I spent three months working full time to get a job by kevin_nisbet on Sunday March 05, 2017 @08:59AM (#13796018)
chillydawg, I take hinkley's assertion to be more of a warning to be careful about biases that may have inadvertently been introduced through the testing methodology. I think it's impossible for us to know without seeing the test you use, but it's always possible that the requirements aren't as clear as you think they are, or potentially what you deem as trivial may be biased from recent direct experience on a problem that you've then turned into a test.

I think these tests are a great tool, but like anything we all just need to be aware and careful of the biases introduced. Also, we need to be mindful that really good developers who are employed, have families etc, may not have an over abundance of time to spend on these, so if 10 companies each send a challenge that takes 4 hours, and it's unclear if the assessment will lead to further interviews, some better candidates may give up on the process or be selective about the ones they complete.

I think this creates an additional bias, that the people who complete your assessments may be the ones with the most time to invest in the process (ie the currently unemployed).

Re:I spent three months working full time to get a job by xtracto on Monday March 06, 2017 @06:23PM (#13807026)
At my current job, we have an "onsite" challenge that we used to hire some Cuban devs. We went to Cuba (from Mexico) and gave the candidates a codebase for Tetris in an interpreted language they did not know. They have 2 hours to transform that Tetris into a Nibbles (snake) game.

The catch? There is no internet in Cuba, so they had to do it using a book, and asking questions to a programmer who was helping them there.

Re:I spent three months working full time to get a job by wikwocket on Sunday March 05, 2017 @11:39AM (#13796776)
I think this is a good point. There's a real risk that a homework you think is simple is a little more complicated because you're making assumptions. I think it's good to have a few current team members actually code it up (not just whiteboard it), and also to talk with a few candidates to see how long it took them, to calibrate this.

It's also better to aim small (a la FizzBuzz) and walk up the complexity slowly, as opposed to starting with "Solve this ticket from our prod JIRA queue, with tests please" (which I have actually been given as a test!)

I like to aim for a very simple task, like proposed above, with maybe one non-obvious part or edge case (which the spec mentions, so it's not a trick question). Just enough to demonstrate a) clean coding for the simple parts, and b) ability to solve something without using a completely naive solution.

Re:I spent three months working full time to get a job by _Codemonkeyism on Monday March 06, 2017 @12:24AM (#13800861)
"[...] perf issues that nobody else believes exist."

Uhuh.

Re:I spent three months working full time to get a job by hinkley on Monday March 06, 2017 @01:22PM (#13804752)
You'd be surprised how many people stop looking at the perf numbers once all the tall tent poles are gone. They have no idea or tools for digging beyond that. I've worked on several projects where the customer still wanted the app to be 2-10 times faster (or worse, a competitor was 2-3 times faster) and people look at the charts and announce that they've done everything that can be done. Some hide in plain sight but others are just putting in work. For instance code duplication can hide a tall tent pole because it's chopped into five pieces.

I had a shared library running on a bunch of systems. One was VxWorks. Cross compiled. I knew nothing about VxWorks except that the code needed to run about 8x faster. I got about 2.5x out of my code by improving locality of reference problems that appeared to be intrinsic but just required experience to see. For the rest I filed a bug report to WindRiver and five to the cross compiler writer. At the end of this process I knew more about the VxWorks administration than anybody else in the group.

People give up, even when there's a clear business case for continuing.

Re:I spent three months working full time to get a job by swalsh on Saturday March 04, 2017 @10:42PM (#13794472)
When you first started talking about a "homework assignment" my stomach started turning.

But reading a file, doing some parsing adjustments, and calling an API sounds like a small amount of python code... so I guess not so bad :\

Re:I spent three months working full time to get a job by throw_away_777 on Sunday March 05, 2017 @01:35AM (#13794882)
Often the assignments are more complex than described. I wouldn't be at all surprised if this was the case here. Also 2 hours is actually a really short amount of time, it can take 30 minutes or more just to understand what the person is looking for if the instructions are not clear.
Re:I spent three months working full time to get a job by jasikpark on Saturday March 04, 2017 @11:03PM (#13794531)
I'm just impressed that this is a 2-3 hr task.
Re:I spent three months working full time to get a job by seanp2k2 on Saturday March 04, 2017 @11:51PM (#13794664)
same. Seems like:

  for num in $(egrep --only-matching '^[0-9]+' input-file); do curl -vv -X GET "http://example.com/api/v1/foo?num=${num}" -o "resp-${num}"; done
edit: assuming "parameter" means query param
Re:I spent three months working full time to get a job by elmigranto on Sunday March 05, 2017 @04:18AM (#13795184)
Okay. Now you're sitting with an interviewer to talk about your home asssigment. Turns out there were some changes in a system and you program needs to evolve accordingly: actual format is protobuff struct and API is asynchronous — you send a bunch of tasks, server queues them up and gives you ids, after some time, results are pushed to a client as they come up. You must store data in SQLite and account for HTTP or REST errors (retry logic, etc.).

Your one liner is neat and all, but now you have to do 2-3 hours of initial work + w/ever time it takes for adjustments in 2 hours scheduled for an interview.

You could've thought out this toy architecture up front with initial simple implementations or at least discuss what they expect you to provide, but instead you wrote a shell script for some nefarious reason, even though you saw obvious disconnect between estimated time and time you actually spent.

Re:I spent three months working full time to get a job by swalsh on Sunday March 05, 2017 @07:53AM (#13795791)
Nah, i'd hire the guy with the 1 liner over the guy with the robust architecture any day. A robust architecture is great and all, but I think it should be built after a need for it has been proven.

When I was a junior developer, I was just trying to get code to work. When I learned design patterns, and had some bad experiences, then I started architect "robust" architectures for everything. After perhaps 6 or 7 years of doing this, I started to question my insanity. Sure there were several instances where I was like "Damn, really glad I built it like that" but there were an equal amount where it just ended up turning a simple problem into a complex problem. There's no good excuse for that.

So now, I go high school simple first, and college hard later. If it means I have to do some rework, fine. I'm okay with a little rework, because in the end it aggregates to a simpler platform that took less time to build.

Re:I spent three months working full time to get a job by _mg on Sunday March 05, 2017 @11:18AM (#13796621)
Agreed, the thoughts of an experienced developer. Some related methodologies/acronyms: Lean development, MVP, KISS
Re:I spent three months working full time to get a job by hueving on Sunday March 05, 2017 @08:27AM (#13795905)
This is ridiculous. There are so many changes in requirements there (asynchronous with push results being the biggest), that everyone is going to have to throw away what they wrote an start over.

Anything beyond 10-20 lines for the solution to this problem is pointless levels of abstraction and would be a huge red flag.

Re:I spent three months working full time to get a job by arjie on Sunday March 05, 2017 @05:44AM (#13795423)
I wonder how many responses fail the assignment for making assumptions like this (that 'numbers' means 'integers').

    $ cat file
    1
    1.2
    3
     4.5

    $ egrep --only-matching '^[0-9]+' file
    1
    1
    3
Surely still demonstrates ability, but an automated testing suite is going to throw it out.
Re:I spent three months working full time to get a job by sgustard on Sunday March 05, 2017 @04:45AM (#13795260)
Sure, but imagine all you knew was C++, which is true for many people. Several hundred lines of code right there. I'm a hiring manager, given questions like this and seen that exact result. Remember that many people cannot solve fizzbuzz.
Re:I spent three months working full time to get a job by user5994461 on Sunday March 05, 2017 @10:31AM (#13796336)
You need a library for HTTP calls and that's it. Pick your favorite one and write the code.

Never had a problem with that. It's well known that C++ can't do anything on it's own.

Re:I spent three months working full time to get a job by hyperpape on Sunday March 05, 2017 @09:27AM (#13796090)
Then your choice is whether you want to hire people who only know C++. For some jobs, you don't. But if you do, you need to have multiple tests and choose one based on the candidate's skills.

We have an in office test--the dev sits down at a laptop with internet access, gets clear instructions and scaffolding code. We know that the tasks take n minutes because we see the time that candidates take.

Re:I spent three months working full time to get a job by re-space on Sunday March 05, 2017 @06:37AM (#13795557)
if the numbers are preceded by a space or another symbol your regular expression fails to parse them. You should be more cautious in your assignments.
Re:I spent three months working full time to get a job by tudorconstantin on Sunday March 05, 2017 @12:35AM (#13794745)
Maybe they had to do it in assembly
Re:I spent three months working full time to get a job by vinhboy on Saturday March 04, 2017 @10:27PM (#13794419)
Thanks for sharing. I think this is a good data point to prove that most people will not cheat on their take home.

There is no incentive to cheat. Why would you want a job you are not qualified to do.

From your experience, it sounds like these are good tests, because it's screening for qualified candidates, unlike the phone interview.

Re:I spent three months working full time to get a job by koolba on Saturday March 04, 2017 @10:42PM (#13794470)
Are you kidding me? People will cheat just for fake internet points. With real cash on the line, they'd do just about anything.
Re:I spent three months working full time to get a job by mathgeek on Sunday March 05, 2017 @12:01PM (#13796928)
This. If people didn't lie (or stretch the truth) or cheat, we would only need resumes to know whether someone can do the technical aspects of any job.
Re:I spent three months working full time to get a job by gambogi on Saturday March 04, 2017 @10:32PM (#13794438)
> Why would you want a job you are not qualified to do.

money.

Re:I spent three months working full time to get a job by gaius on Sunday March 05, 2017 @06:12AM (#13795495)
Also, credentialling. Even if you can't do the work and only stay a few months, Google or Goldman or another big name on your CV will still open many doors.
Re:I spent three months working full time to get a job by wolfgke on Sunday March 05, 2017 @07:24AM (#13795697)
In Germany there is a culture of not changing jobs very often (at most every few years, but even this should not happen too often). So if you have a "well-known" name such as Google or Goldman Sachs on your CV, but worked there only for few months, it is a clear sign that you were fired and about every future employer will be very cautious.
Re:I spent three months working full time to get a job by sidlls on Sunday March 05, 2017 @12:15PM (#13797017)
Outside the Valley and startup culture most companies looking for software developers in the US view a tenure of less than two years as being short, and a series of them indicates "job hopping."

I'm not commenting on whether that's a good or bad thing, because good or bad it's simply the way it is.

Re:I spent three months working full time to get a job by user5994461 on Sunday March 05, 2017 @10:33AM (#13796352)
What if you joined Goldman Sacchs and was poached by JP Morgan after 6 months?

What if you joined Google and was poached by Facebook after 1 year?

Re:I spent three months working full time to get a job by wolfgke on Sunday March 05, 2017 @12:41PM (#13797191)
1. What is most important in your CV is the last employer. If it seems that you were fired, this can cause problems with getting a (decent) job afterwards. If you were poached, it is because the other employer wants you badly. So in your example your new "last" employer becomes JP Morgan or Facebook. So this kind of problem does not occur here.

This does not contradict the fact that it still leaves/can leave a bad impression on impression if your were willing to be poached without a very good reason, since can be considered as a strong sign that your are not loyal to your employer and only hunting for money.

2. Poaching is rather uncommon in Germany. As I outlined in 1 being willing to be poached multiple times is a sign that you are not very loyal to your employer. Thus there is a strongly reduced incentive for employees to be poached.

Also for poaching to work, you have to offer lots of money - I'd be really surprised if there are lots of employers that are willing to start such an "arms race with money". Why not simply offer decent money in your regular job advertisements and get good people without any arms race?

Poaching might make sense if there you want to get "rockstars" that are not available on the "free job market", but can only be poached. But I'm also not aware of any industry sector in Germany where there exist employees that are treated as rockstars. :-(

Re:I spent three months working full time to get a job by user5994461 on Sunday March 05, 2017 @03:27PM (#13798380)
Your vision is clearly limited to Germany, where poaching doesn't exist because there is no jobs and no strong companies competing.

Just imagine a random company in a tech hub. They host a meetup once... the days after the meetup, most of their employees have been contacted by recruiters and other companies who attended.

If they want anyone in particular and/or if any employee's salary is not on-par with their value, here they go! :D

Re:I spent three months working full time to get a job by blisterpeanuts on Sunday March 05, 2017 @08:53AM (#13795989)
For medium to large companies, this is true in the U.S. as well. Six months at Facebook, Google, or Bank of America would be a huge red flag.
Re:I spent three months working full time to get a job by gaius on Sunday March 05, 2017 @03:35PM (#13798431)
That person will always be the "Goldman alumni" or the "ex-Googler". Couple that with a semi-prestigious degree and they'll be set.
Re:I spent three months working full time to get a job by matwood on Saturday March 04, 2017 @10:51PM (#13794502)
I don't even care if the person 'cheats' because I'll figure it out when we discuss the solution.
Re:I spent three months working full time to get a job by avn2109 on Saturday March 04, 2017 @11:17PM (#13794573)
This has happened at my company. We give a similarly near-trivial hw problem, and sometimes people come in and literally "cannot remember" any single thing about the assignment, including the names of the columns in the data or the approximate objective of the HW. This is after performing plausibly well on a phone screen etc.
Re:I spent three months working full time to get a job by vinhboy on Saturday March 04, 2017 @11:43PM (#13794641)
Thanks for clarifying this. This is what I meant when I said "Why would you want a job you are not qualified to do."

I am not so good with words sometimes... Haha...

Re:I spent three months working full time to get a job by dottedmag on Sunday March 05, 2017 @02:07AM (#13794942)
From my recruiting experience people cheat even during live-coding interview. I was pretty amused seeng a person whispering to a buddy outside of the video pickup area trying to get _any_ code written.

Why do they do it? I have no idea.

Re:I spent three months working full time to get a job by throwaway_374 on Sunday March 05, 2017 @06:10AM (#13795484)
I'm going to assume "couldn't accomplish the task" means couldn't get it entirely correct. Do you provide a testing baseline that determine the expected behaviour? With TDD being the norm and correct way to test your program behaviour, I'm absolutely not going to go through every edge case with a fine tooth comb to check your "correctly formatted number" calls the API as you expect for a homework assignment. Provide a testing baseline or clearly demarcate the various possible edge cases as would be discussed in real life.
Re:I spent three months working full time to get a job by mdip on Saturday March 04, 2017 @10:32PM (#13794437)
> I'm still shocked over half of developers couldn't accomplish that task. Makes me wonder what they were accomplishing in their existing roles.

I once asked a candidate to write a for loop in C#[0], using my laptop and Visual Studio and watched for a solid 5 minutes while he struggled -- And I don't mean jitters around syntax, I mean, failing to declare a variable properly and while he knew what a for loop was, he had no idea how to write one in C#. His resume touted a series of projects that we estimated put him a little above a Junior developer and the only language he referenced was C#. I don't normally do these kinds of "on the spot tests" because I, personally, hate them, but I was cheering when I read Coding Horror's "Fizz Buzz" article[1] on the subject.

This was the most foul example and my only experience is with developer and ops/security positions, but if you're getting half of developers who are in the same time zone as the title[2], you're doing well. Does this happen in other parts of the business world? Some of the folks we get in would be like a Walmart cashier applying to run a finance department because "they've handled money before". And what if they got the job, do they think they'd come close to being successful? I'm all for the "fake it until you make it" and I'm very willing to overlook weaknesses around experience/education if the candidate is really passionate and I can get enough of a comfort level that they'll be a quick study and love the job, but you have to be realistic about your deficiencies.

A lot of the problem, I've found (being on both sides of this in the past) is with recruiters, as well. They tend to operate on a "throw darts at the wall, blindfolded" approach, with the assumption that if they send out a million candidates for a million jobs without regard for qualifications, that they'll get lucky, one will land somewhere and they'll get a commission from sheer volume on bad odds. This serves nobody well -- it causes companies to put up multi-step gates that involve people who aren't close enough to the field to discern a good candidate from a bad one via resume performing a filter operation that disproportionately disqualifies the really passionate but "not quite a perfect fit on the qualifications side" and it causes job seekers to take a bunch of interviews for positions they won't like/aren't qualified for and won't land -- causing them to have a miserable experience interviewing (and probably resulting in some dropping out of the job market entirely).

[0] The exercise was, specifically, write a for loop with an int value that is incremented by one, adds that int value to another int variable, and multiplies the result against the counter, assigning the value to a third variable. Print the result to the console. This was before "Fizz Buzz" became all the rage, I did my best to give a blindingly simple problem to just validate that the person could do something in the language.

[1] https://blog.codinghorror.com/why-cant-programmers-program/

[2] Never mind the details "Must have 4 years of experience in Angular", nonsense -- a topic for another post, but the way we write job requirements is about stupid. I mean, I've seen experience requirements that exceed the length of time the technology was in existence, and I'd rather see a candidate demonstrate an ability to adapt and learn new things than be overly concerned with whether or not they've used a framework that is really similar to a bunch of other frameworks.

Re:I spent three months working full time to get a job by moron4hire on Saturday March 04, 2017 @11:01PM (#13794527)
Bad jobs are constantly in need of filling: people quit very frequently.

Bad employees are constantly in need of placement: people get fired very frequently.

If you're hearing about a particular job or candidate, the odds are they are bad. Most jobs are filled internally or by referral. IIRC, it's only about 20% of jobs that are filled by recruiters and/or cold job applications.

Re:I spent three months working full time to get a job by gspetr on Sunday March 05, 2017 @08:01PM (#13799974)
Like the sibling commenter I also doubt that people get fired very frequently.

Shady body shops come to mind.

I've witnessed exactly 2 people fired in 7 years.

And anecdotally, the bigger the company the rarer the firings.

Where were you working at that people got fired all the time?

Re:I spent three months working full time to get a job by user5994461 on Sunday March 05, 2017 @10:38AM (#13796379)
> Bad employees are constantly in need of placement: people get fired very frequently.

Not true. Firing is a rare event.

If anything, bad employees will end up in a group that is "relaxed" toward productivity and stays there for a while.

Re:I spent three months working full time to get a job by mdip on Sunday March 05, 2017 @12:03AM (#13794696)
You're right about bad employees, but I've not found it difficult to weed those candidates out. At the same time, I don't fault a candidate for being laid off provided they have a good explanation[0] and/or they're otherwise a good fit.

As for bad jobs, even bad jobs need someone who is functionally capable of doing them. Sure, you have to be vigilant about filling those positions, but it's rare to encounter a "bad job" in this field that would be fine to have a terrible candidate in.

Regarding jobs being from internal candidates: It's interesting, because I hear that statistic rather frequently and often wonder where it originates or whether or not it has the meaning that is often attributed to it. Again, pulling from my anecdotal experience, though my resume was passed in from an internal employee for the two jobs I was most interested in[1], in one case my resume was handed to a sales person who reached out to me with a question about the company I had just been laid off from -- I had never talked to him or met him before and he lived about 100 miles away and in the other case, my sister handed my resume off to a friend of hers who worked there[2]. This friend and I met for the first time on my second day of work there. I don't even know if the guy is a software developer or not -- and that's the crux of the issue. If the recommendation is coming from someone doing the same/similar work on the same/similar team, that candidate is probably a good fit. If it's from someone doing wildly different work or who has no idea what a good candidate would look like, it's not much better than the blind solicitation from a recruiter. This is further complicated by the fact that many/most companies grant a referral bonus, incentivizing staff to solicit and (possibly) lowering the quality of candidates coming through that channel[3]. I'm really curious about others' thoughts on this, particularly those who've hired for their own companies.

The last issue with the 20% rule is that in companies that are dedicated to filling a diversity standard of some kind, it's hard to get there from internal employees unless you already have a very diverse staff. Reality being non-ideal, you tend to hang out with folks who are similar to you[4].

[0] There are plenty of reasons people get laid off/lose a job that have nothing to do with the competency of the employee. Companies go completely out of business, shedding all jobs or merge with companies where the whole department gets eliminated. Less "great" excuses are role elimination, though, this happened directly to me in January but I was offered a position for every job I interviewed for, so given appropriate context it can be fine as well.

[1] I interviewed at four places, all four offered me a position, two of the places were the highest on my list and I took one of my top choices. The two that were high on my list technically had my resume passed in from someone who already worked there.

[2] That it was my sister certainly helped -- she's been the CFO of a very well known global company and is currently the CEO of a mid-sized company -- her recommendation is trustworthy and people who know her know that she wouldn't embellish anything just because of family relation.

[3] I'm on the fence about this, though, personally. On the one hand, I'm less likely to recommend anything but the absolute best candidate for a role at company I work for if there's not a financial incentive -- it's nearly all downside otherwise. If the candidate works out, it's unlikely anyone is going to remember you sent that resume in. If the candidate is a mess, you get a ding on your record for recommending a fool and a subconscious ding to your own reputation that you associate yourself with fools (unfair as that is, I've seen it). If there's a financial incentive, there's always the "well, we paid him to do that; maybe he really needed the money" option which is bad, but not as bad. I got 11 people hired in at CompUSA when I worked there in my teens because they paid a $250 bonus. I had one really bad (as in, he stole things, and damaged things in fits of rage bad) recommendation that surprised my managers and me (he was a close friend and I had no idea he turned in to lunatic once he was being paid to do something).

[4] Though this does apply on racial/gender boundaries, one of the goals of diversity is to also avoid group think. Taking race out of the picture, you favor people who are like/agree with you and if the goal is to seek people who are hard working/passionate but not cut from the same cloth as the rest of the team, an internal recommendation will miss that more than it will hit it.

Re:I spent three months working full time to get a job by ryandrake on Saturday March 04, 2017 @10:46PM (#13794482)
What happened in the phone screen?

If candidates who can't code are actually getting on site, your phone screening is inadequate and vulnerable to "smooth talkers".

Re:I spent three months working full time to get a job by mdip on Saturday March 04, 2017 @11:42PM (#13794636)
You're absolutely right.

Hiring at the company worked like this, provided the resume wasn't passed directly from a member of staff close to that team:

(1) Applicant applied through web/recruiter/e-mail. (2) Resume was reviewed by a generic hiring team who covered every kind of job the company had and none of whom had even the most basic understanding of what a developer's qualifications should be[0]. (3) This same team does a myriad of phone screens to further whittle the pile. (4) Team's manager reviews remainder and often didn't perform a second screen since one was already done[1]. (5) Candidate arrives.

[0] These same people provided many of the "templates" used for the job descriptions, so you can imagine these were similarly bad. This practice resulted in the company, for years, refusing all resumes where the candidate did not complete a 4-year degree program. I pushed for an end to that for dev jobs after two candidates I hired in who had limited/no college experience turned out to be excellent employees.

[1] And in some cases, the manager knew nothing about software development and was put there from some part of the business, so s/he'd be about as effective at a phone screen as the hiring team.

Re:I spent three months working full time to get a job by flukus on Monday March 06, 2017 @02:19AM (#13801193)
Don't assume the person doing the phone screen is the candidate.
Re:I spent three months working full time to get a job by oh_sigh on Sunday March 05, 2017 @12:00AM (#13794688)
Considering how few 'developers' could pass FizzBuzz, it shouldn't surprise you any more.
Re:I spent three months working full time to get a job by pryelluw on Saturday March 04, 2017 @10:18PM (#13794390)
What kind of values did you have to validate from the file? Im tempted to do this myself right now just for the fun of it. Can you provide a sample?
Re:I spent three months working full time to get a job by bbernoulli on Sunday March 05, 2017 @12:29PM (#13797112)
Can you provide anymore details about this? This doesn't seem like it would take 2-3 hours.

I'm going to have to assess come applicants soon and have been trying to come up with something appropriate, which is why I'm interested.

Re:I spent three months working full time to get a job by caseymarquis on Sunday March 05, 2017 @10:13AM (#13796268)
What language was this in, out of curiousity? That timeframe seems very long for the task, but only because I tend to work with languages which have nice standard libraries.
Re:I spent three months working full time to get a job by deepGem on Saturday March 04, 2017 @11:30PM (#13794608)
Just curious, what was the size of your file and did you propose any latency limitations for the API calls ?
Re:I spent three months working full time to get a job by hackinthebochs on Sunday March 05, 2017 @01:03AM (#13794816)
We really need to stop pushing this HW assignment nonsense. It's offloading the cost of hiring on to prospective candidates. The asymmetry of cost makes it plainly exploitative.

So you block off 4-8 hours of your life for this job you're really excited about. What is the employer putting up? Generally nothing. They get a sea of responses and they get to pick a few of the best ones. The 100 responses they got cost these candidates 400+ hours of time for no cost to the employer whatsoever.

Take home assignments are fine, but the employer needs to put up something as well. Either pay for the time I spend on it, or have the assignment late in the interviewing process and have employment contingent on passing some known bar ahead of time. That is, I should be the only one doing the assignment and there should be no wishy-washy rejections.

Re:I spent three months working full time to get a job by throw_away_777 on Sunday March 05, 2017 @01:32AM (#13794876)
To add on to this, a take-home assignment should be more than just another filter. The companies I interviewed for with take-home assignments didn't actually discuss the assignments at all in the in-person interview - I spent the time to prepare for and do the assignment, at least pretend it matters.
Re:I spent three months working full time to get a job by robinson-wall on Sunday March 05, 2017 @06:15AM (#13795504)
That just seems odd. How were they checking that you were the one who completed them?

All of the interview processes I've had recently have checked I did the exercise by either asking me to describe what I built with no aid, asking me to walk through the code with it in front of me, or asking me to conceptually expand on what I built on a whiteboard.

Re:I spent three months working full time to get a job by throw_away_777 on Sunday March 05, 2017 @10:39AM (#13796388)
They gave me the standard whiteboard interviews on-site after that. This was for a data scientist position. I did not get offered the job (but I accepted a good job offer a couple of weeks later, so whatever).
Re:I spent three months working full time to get a job by akulbe on Sunday March 05, 2017 @01:40AM (#13794892)
What if a company offered to pay you a day's wages, or something reasonable still (if it's less than that)?

Whittle down the pool even further and the ones you think look good on paper, and after an interview (or a series of them), have them come in, on a paid basis.

It'd be a sign of good faith that they're both serious about finding a good candidate, and respectful of your time?

I know some companies do paid stuff like that. If only it were more commonplace.

Re:I spent three months working full time to get a job by jventura on Sunday March 05, 2017 @05:07AM (#13795343)
> What if a company offered to pay you a day's wages, or something reasonable still (if it's less than that)?

I did an assignment like that for a company once, I'm still waiting for the money for more than one year...

Re:I spent three months working full time to get a job by hackinthebochs on Sunday March 05, 2017 @02:07AM (#13794941)
That sounds like a fair process. Employers are in a position of power and can easily abuse it. When the employer also invests in me as a candidate it shows they're serious about me and also ethical. Sounds like a win-win.
Re:I spent three months working full time to get a job by dottedmag on Sunday March 05, 2017 @02:05AM (#13794939)
That's the only sensible way to do HW, if it takes more than 5 minutes.

Note that 5-minute-long task is a good pre-filter on its own.

Re:I spent three months working full time to get a job by flukus on Monday March 06, 2017 @02:25AM (#13801212)
I still wouldn't if I currently had a job. By the time I get home my brain is usually pretty fried and that 4 hours probably means giving up a couple of nights.
Re:I spent three months working full time to get a job by mikekchar on Sunday March 05, 2017 @02:56AM (#13795059)
It's a bit frustrating because different people react so strongly in both directions. I don't like live coding, but I'll be ecstatic with a pair programming session -- because I can evaluate them at the same time. Homework, I'm generally OK with, but I honestly hate it when you get a response like "We didn't like your code. Goodbye." On the other hand, I know some people who can't deal with the stress of writing code in an unfamiliar situation.

I wonder if the best thing to do is to simply offer the candidate a choice.

Re:I spent three months working full time to get a job by prefect42 on Sunday March 05, 2017 @09:52AM (#13796165)
> It's offloading the cost of hiring on to prospective candidates.

Why is that a bad thing? The prospective candidates aren't entitled to anything, the burden should be on them to prove they have any capabilities for the job.

> What is the employer putting up? Generally nothing.

Totally incorrect, have you ever had to hire somebody? The initial phone screens alone to weed out the 99% of complete incompetents takes many hours/days. Even getting to the list of phone screens, involves many hours of sifting through resumes, where each resume is cleverly designed to hide the fact that the prospective candidate is incompetent.

Re:I spent three months working full time to get a job by JoeAltmaier on Sunday March 05, 2017 @09:53AM (#13796171)
Its a bad thing, because good employees are hard to find. They'll go elsewhere instead of jumping through your hoops.
Re:I spent three months working full time to get a job by aisofteng on Sunday March 05, 2017 @02:10AM (#13794946)
This reeks of entitlement. If you want the job, you'll find four hours. They don't owe you a job and they don't owe you anything for going through their hiring process that they have designed to find people to pay a salary.

I echo the grandparent's sentiments, myself, from my own personal experience as well.

Re:I spent three months working full time to get a job by hackinthebochs on Sunday March 05, 2017 @02:12AM (#13794949)
So its entitlement to expect an employer to not exploit their position of power? Sure, I'll take that label.

>If you want the job, you'll find four hours.

But what happens when everyone starts having these 4 hour screens? Now its a 40 hour process to apply for 10 jobs in a week (and this is before any commitment on the part of the employer). It's not sustainable or fair. And yet, there's no incentive for employers not to do it. So we as job seekers just need to suck it up and be thankful for the opportunity, right?

Re:I spent three months working full time to get a job by LoSboccacc on Sunday March 05, 2017 @03:42AM (#13795131)
I work at a small company in a remote part of an openly backward state when it comes to startups, and yet got two hundreds applicants to file a javascrip developer position.

After interviewing 10 (say two three hours spent on each between contacting, scheduling up etc) it was clear every unemployed with 'can use word' as skill boosted their resume and applied.

I'm sorry for the real developers looking for a job but a company can't dump 20 days work on chasing and weeding liers.

I'm not a fan of homeworks myself but this is what it has come to.

I'd be payng but that puts the company and the prospect in a very difficult position them towards tax laws and towards their current employer non competes, the company toward again tax laws and then there's the absurd of paying for contract work delivered that's 99% of times not up to spec.

Beside, the unwillingness to compromise smells itself and given the choice I'd never get a potential troublemaker in that only thinks time=money and screw everything else.

That little empathy for both sided of the problems sure is a red flag.

Edit: well unless it's a contracting job then it's fine.

Re:I spent three months working full time to get a job by hackinthebochs on Sunday March 05, 2017 @04:49PM (#13798933)
This seems like something a 5 minute FizzBuzz-esque programming assignment as a pre-filter could easily fix. The goal seems to be a barrier that only serious applicants will even bother to attempt, and that's fair. But when that barrier then becomes a 4+ hour time sink for the serious applicants it becomes a problem. There are plenty of hackerrank style sites where someone can show a bare minimum of competency without costing either side much time.
Re:I spent three months working full time to get a job by LoSboccacc on Monday March 06, 2017 @04:22AM (#13801590)
yeah I think 4 hours is a bit too much, in the end you only need competency as a screening.

we used to give out this http://play.elevatorsaga.com/#challenge=3 and asking for solution to level 3 which can be done in a short time + is the first non trivial challenge.

of course solutions can be find in internet etc, but it's pretty easy to look them up if they smell fishy and it'd all come down crashing at the face-to-face anyway

it's also a very good exercise in real world problem solving and a source of endless technical discussion since there's no single good approach, especially with two elevators to schedule.

Re:I spent three months working full time to get a job by hinkley on Sunday March 05, 2017 @06:04AM (#13795471)
What power do you think they're exploiting?

Most of the places I've been at were desperate for 'good' people and they couldn't seem to find them. It's still a seller's market out there.

Re:I spent three months working full time to get a job by hackinthebochs on Sunday March 05, 2017 @04:55PM (#13798981)
It's the power to get 30+ people to jump through hoops that only one person has a chance at being chosen. Even worse, a good 50-60% of those people have no chance out of the gate, they just don't know it. Encouraging people with little to no shot at the job to do significant work so make your job of filtering them out easier just reeks of exploitation. Come up with a filter that's minimal cost for those applying, fizzbuzz style problems seem suitable.
Re:I spent three months working full time to get a job by gspetr on Sunday March 05, 2017 @08:11PM (#13800008)
In my experience most of the places that tried to pull the "no good people" card were also the places that refused to pay even 20% above the market.

If this were true people would be poached a lot more frequently than what we can observe now.

Re:I spent three months working full time to get a job by aisofteng on Sunday March 05, 2017 @02:43AM (#13795026)
And what's wrong with having a position of power? You say it like it's a dirty phrase.

Can you, personally, pay me a salary? If you can and I want to work with you, I absolutely think it's fair to ask four hours of my own time to demonstrate I'm worth consideration for it. If not, then why does your opinion matter?

Re:I spent three months working full time to get a job by hackinthebochs on Sunday March 05, 2017 @03:03AM (#13795066)
You sound like a Libertarian. I'm assuming all the advances in worker's rights we've had over the last hundred years are also "entitlement"? If not, then I don't see what's different about expecting an employer to not exploit prospective applicants by offloading most of the cost to them.
Re:I spent three months working full time to get a job by PeterisP on Sunday March 05, 2017 @10:24AM (#13796314)
I don't "want the job" per se, I'm interested, which is a bit different and we'll need the interview process to find out if I actually want the job.

Furthermore, I already have a job, just as most reasonable candidates do - so if you want to convince me that I should spend many hours on that, you'd better be sure that your offer has a really attractive first impression and seems likely to be better than the job I currently have, otherwise you'll be self-selecting your candidates only from the (generally less skilled) sub-population of workers for whom "If you want the job, you'll find four hours" is true because they actually are desperate for jobs, unlike most skilled people in tech industry.

Re:I spent three months working full time to get a job by thedufer on Sunday March 05, 2017 @02:31AM (#13794993)
This phrasing may sound like entitlement, but try turning it around. Most of the people who will turn down a homework assignment are the ones who can afford to do so, because they already have a good job or know they can find one. Is that really the first filter you want on your candidate pipeline?

I have never seen a job posting I was sufficiently interested in to put in 4 hours with no investment from the company.

Re:I spent three months working full time to get a job by aisofteng on Sunday March 05, 2017 @02:41AM (#13795018)
I have, and it's how I got the job I have now, which is by far the best job I've had.

Regardless, if you have a good job already, why apply to any position you're not particularly interested in and that you wouldn't spend four hours trying to get?

Re:I spent three months working full time to get a job by dozzie on Sunday March 05, 2017 @04:48AM (#13795274)
Because they contacted me and offered me to participate in the recruitment process, and while I don't look for a job, I'm not against checking where this can take us?
Re:I spent three months working full time to get a job by dkersten on Monday March 06, 2017 @01:34PM (#13804876)
I've never taken a job I've applied to myself. That is, they were the ones who approached me (some more directly than others[1])

Why would I spend any of my already very limited time if they didn't make sure the process is streamlined?

Also, I don't think it's uncommon to like what a company does and being interested without yet knowing if you're interested enough to put the time aside - most company sites and job descriptions are much too generic and vague, so I'd want to talk to some employees first (remember, interviews are two way conversations). So I might not know if I'm interested enough at the time of application, just that I might be.

[1] for my current job, the interview process was essentially them trying to persuade me to join them, and my previous job I was actively looking for a job and someone I know at the company said I should apply. My "application" consisted of telling him "ok set up an interview"

Re:I spent three months working full time to get a job by thedufer on Sunday March 05, 2017 @10:57AM (#13796481)
I think it is worth seeing what's out there even if you're happy. Maybe there's something better!

The standard process where the first two steps are some ordering of a 1-hour interview with someone technical and a chat with a recruiter is perfect for this. With minimal effort (maybe 90 minutes) you find out whether they're interested in you at all, and get to ask both a technical person and a recruiter about the job.

The big time investment typically comes later, and I can easily bail if I decide it isn't going to be a compelling offer. I've done this quite a bit.

I'm glad the homework process worked for you, but my point that it doesn't seem like a good idea for the company stands. If the first thing you do is filter based on how badly applicants need a job, you're losing a significant portion of the best people right off the bat.

Re:I spent three months working full time to get a job by hinkley on Sunday March 05, 2017 @05:48AM (#13795430)
I want this job or three others.

So now I'm doing a day and a half of unpaid work for them, taken out of evenings and time with the family.

Not hypothetical. I just described my last job hunt, 16 months ago.

The place I really wanted to go closed the req on me, and then opened it back up the day after I started at another place. My third choice (stars didn't align on the other 2 interviews, in part because of stuff like this).

Re:I spent three months working full time to get a job by dkersten on Monday March 06, 2017 @01:23PM (#13804759)
And if they want good candidates then they better not treat me like my time is unimportant. I don't owe them my time.

It goes both ways.

Re:I spent three months working full time to get a job by phamilton on Saturday March 04, 2017 @08:48PM (#13794155)
Additionally, most of us are more willing to do interview work in our off time. Taking a vacation day to interview is a direct financial investment. Spending a Saturday doing a 4 hour home work is a sacrifice, but doesn't require taking vacation time. Taking an early afternoon off to go talk with 3-4 engineers for 1-2 hours is something that can much more easily fit into ones schedule.

EDIT: I want to provide an anecdote around this. If your salary is $150k, it may cost you roughly $400 in gross pay to interview somewhere. Sure, you could take paid vacation, but vacation time is paid out in cash when you leave so it still costs you. Companies with unlimited vacation are a different story.

Re:I spent three months working full time to get a job by mdip on Saturday March 04, 2017 @10:07PM (#13794364)
Just wanted to say that I really like the idea of testing the "homework assignment" on your own team to hone it.

I had a similar experience a month ago. It was a similar "4 hour project" but it was open ended with "make it as complicated or as simple as you want". Being a single table backed CRUD app, you could only put in so many capabilities but it got me excited thinking about ways I could surprise the staff. In the end, I made it self-hosted (in a language that self-hosted is less common), included an installer, and made it support multiple connections from different devices with updates that pushed to the connected clients. The project took me about a day and a half (with two of those hours spent yelling at WIX), but the core parts took about two hours. I was genuinely surprised at how much fun I had putting it together. They also asked me to estimate my time spent -- since I had contract work I was doing at the time and couldn't dedicate a long stretch all at once to it -- I broke it down into its individual tasks and documented the whole thing. They had no problem with the fact that I delivered it a week after the interview.

I also second your "I can spare a half a day for a prospect" attitude. There's a flip-side benefit to that, as well. A candidate who feels over burdened with a simple assignment (provided it's tested as you mentioned and truly is simple) is probably not one I'd be interested in hiring, anyway. I'm not saying it's "one size fits all" -- I've had candidates walk in the door that I knew in advance were really good fits who were hired after a 30-minute screen. That, though, is a unicorn sighting.

Re:I spent three months working full time to get a job by hackinthebochs on Sunday March 05, 2017 @01:00AM (#13794806)
What if the HW assignment became the norm. Could you spend half a day, or a whole day to 10 jobs? What if after you spend all that time you still don't get any offers, or even interviews? Job searches are already hard enough (for most people) without these huge time sinks becoming the norm.
Re:I spent three months working full time to get a job by Terr_ on Sunday March 05, 2017 @01:57AM (#13794918)
You're assuming that such assignments would always be given improperly-early in the vetting process.

If 10 good assignments meant at least 3 offers, it'd be a different story, right?

Re:I spent three months working full time to get a job by hackinthebochs on Sunday March 05, 2017 @02:10AM (#13794947)
That would be fair. But having that sort of expected result is impossible for many people. Of course, some people are good enough and sell themselves well enough that they'll never have problems passing such screens and getting offers. But for those that aren't, and worse don't know they aren't, will be able to reach that level of expected return without the process being designed not to exploit those situations.
Re:I spent three months working full time to get a job by wahnfrieden on Saturday March 04, 2017 @11:29PM (#13794604)
Requiring a take-home assignment, not just offering it as an alternative to an in-person interview phase, is a great way to systematically reduce the diversity of your hiring pool. It works well for some, but please don't require it of everyone.
Re:I spent three months working full time to get a job by nialo on Saturday March 04, 2017 @11:37PM (#13794625)
I am confused by this, could you help me to understand why this is so?

In particular, it seems to me that take-home assignments are strictly better for candidate scheduling etc than in-person interviews, if time spent can be held equal. Maybe time spent is just not equal very often?

Re:I spent three months working full time to get a job by stale2002 on Saturday March 04, 2017 @11:43PM (#13794639)
Because if a company is going to make me spend X hours of my time, then I want the company to be spending X hours of THEIR time.
Re:I spent three months working full time to get a job by hackinthebochs on Sunday March 05, 2017 @12:56AM (#13794788)
Yes, absolutely. I say this every time this homework assignment shit pops up. It's offloading the cost of hiring on to prospective candidates. The asymmetry of cost should give everyone pause. It's plainly exploitative.

So you block off 4-8 hours of your life for this job you're really excited about. What is the employer putting up? Generally nothing. They get a sea of responses and they get to pick a few of the best ones. The 100 responses they got cost these candidates 400 hours of time for no cost to the employer whatsoever.

Take home assignments are fine, but the employer needs to put up something as well. Either pay for the time I spend on it, or have the assignment late in the interviewing process and have employment contingent on passing some known bar ahead of time. That is to say, I should be the only one doing the assignment and there should be no wishy-washy rejections.

Re:I spent three months working full time to get a job by rnovak on Sunday March 05, 2017 @01:06AM (#13794823)
> What is the employer putting up? Generally nothing.

Unless you've been in the shoes of a hiring manager, I'm unsure as to where this idea is coming from?

Having been a hiring manager, it is a horrible experience. Unless it's extremely naive, homework sets generally take time to come up with and formalize, and certainly take time to review the results for.

I suppose I can understand conflating the motivations of an interviewer with their employer, but it's not generally true to say that interviewers are just trying to exploit those they interview.

Re:I spent three months working full time to get a job by hackinthebochs on Sunday March 05, 2017 @02:02AM (#13794931)
>homework sets generally take time to come up with and formalize, and certainly take time to review the results for

It's a one-off effort to come up with an assignment. So the cost per application can be extremely low. As far as evaluating them, the bad ones can usually be tossed out in minutes or less. Comparatively, the cost per applicant is basically nothing.

Re:I spent three months working full time to get a job by navalsaini on Sunday March 05, 2017 @01:17AM (#13794843)
How many companies waive the coding requirement or postpone it towards the end, if you already have open sourced a bunch of code. It is also possible that the HR managers are just happy taking a route, where they can offload most work to the other party. The can instead act as better intermediaries, aligning the hiring goals of the company and the experience for the applicant. Whats wrong with asking them to create better value or understand the domain better so as to be able to create better value?
Re:I spent three months working full time to get a job by prodigal_erik on Sunday March 05, 2017 @04:08PM (#13798648)
> if you already have open sourced a bunch of code

How do I know you wrote it and didn't merely paste your name over some project I've never heard of?

Re:I spent three months working full time to get a job by navalsaini on Sunday March 05, 2017 @11:01PM (#13800611)
Thats quite easy.

1) How many forks and stars do you have? 2) How often have you opensourced? 3) Have you blogged about them or created a documentation? 4) Why did they build each of those repos? 5) Commit logs... etc..

Very easy to develop such a framework.

One or two repos can be copied, but there is ample signature on a genuine open source contributors.

Re:I spent three months working full time to get a job by gnaritas on Sunday March 05, 2017 @01:02AM (#13794813)
> It's offloading the cost of hiring on to prospective candidates. The asymmetry of cost should give everyone pause. It's plainly exploitative.

There's nothing wrong with that, it's a competitive market, those who get hired are those willing to compete, not those who complain about unfairness about being asked to demonstrate their skills. Employers spend tons of time filtering candidates, even reviewing the submitted work takes time and effort, saying it's no cost to the employer whatsoever is not only untrue, it's naive.

Re:I spent three months working full time to get a job by mavelikara on Sunday March 05, 2017 @05:12AM (#13795354)
> So you block off 4-8 hours of your life for this job you're really excited about. What is the employer putting up? Generally nothing.

What?! Up until that point, typically, the employer had crafted the job posting, posted in on various channels, reviewed the responses, talked to promising candidates, and then give you the assignment. And a good assignment needs to be carefully crafted, a process that usually takes an order of magnitude time more than what it takes to prepare an answer.

Re:I spent three months working full time to get a job by consz on Sunday March 05, 2017 @07:46AM (#13795753)
An order of magnitude is not much though, that's only ten applicants? Most assignments waste the time of hundreds of applicants, so it sounds like its still a net win for the employer.
Re:I spent three months working full time to get a job by nialo on Sunday March 05, 2017 @09:32AM (#13796111)
It feels to me like the root problem here isn't how many people are doing the homework problem or whatever. It's that this is increasing your time spent as a candidate relative to the in-person interview.

I think your last paragraph is very close, but I think the thing that matters is "no wishy-washy rejections". Not being the only person taking the test or how much time the company spends seem like ways to make that happen to me.

Maybe I'm just completely wrong here, but I think most of the objections to homework type tests are being caused by processes where the homework test was in addition to the in-person whiteboard interview, not instead of it.

How would you feel about a process that was: some preliminary screening -> nominal 4 hour homework thing -> in person meeting to confirm that you're not a complete asshole and negotiate salary?

Re:I spent three months working full time to get a job by cagataygurturk on Sunday March 05, 2017 @01:57PM (#13797766)
Job seeking is a sales activity. You sell your labor on labor market. Every sales activity has a cost. If you do not want to bear this high cost of IT industry, you can work at McDonalds. Probably your sales cost would be much less but your profit also.
Re:I spent three months working full time to get a job by stale2002 on Monday March 06, 2017 @01:58AM (#13801128)
What job market do you live in?

It is a sellers market. I get recruited every single day. Any company that disrespects me and wastes my time isn't going to be very successful at convincing me to work there.

Developers are the ones with the power in this market, and I have no problem throwing this power around.

Re:I spent three months working full time to get a job by cagataygurturk on Monday March 06, 2017 @09:58AM (#13803044)
Then go on with your current arrogance. Hope the market continues like this for you.
Re:I spent three months working full time to get a job by rnovak on Sunday March 05, 2017 @01:00AM (#13794802)
Unless they have a gun to your head, they aren't making you do anything. Applying/Interviewing is your choice.
Re:I spent three months working full time to get a job by navalsaini on Sunday March 05, 2017 @01:12AM (#13794832)
He is saying that the company needs to tell their people to fix the process and do what they are paid for. Not offload it entirely to the applicant.

Maybe just open separate channels for people who have an open source portfolio. I have about 30 repos in my OSS, but still have to take these assignments. Its such an utter waste of my time.

Re:I spent three months working full time to get a job by stale2002 on Sunday March 05, 2017 @01:31PM (#13797559)
Yes.... And I would choose NOT to apply to such a company, because F them.
Re:I spent three months working full time to get a job by jpttsn on Sunday March 05, 2017 @03:07AM (#13795073)
This just seems petty. Do you actually want the job? Or are you just there to spread some kindergarten version of justice?
Re:I spent three months working full time to get a job by stale2002 on Sunday March 05, 2017 @01:33PM (#13797578)
I do not want to work for a company who disrespects me and my time.

That is a huge red flag, and means that they will disrespect me at work as well.

Re:I spent three months working full time to get a job by wool_gather on Sunday March 05, 2017 @11:18AM (#13796622)
It does, if they're actually doing it in a way that's useful to them. At least one, probably two, engineers are going to evaluate what you send in, take notes, and then go over it with you. And they have to do that for every response.

So that's an absolute floor of an engineer-hour per candidate: Anything less than 30 minutes to read through it and take notes is useless, and figure another 30 minutes minimum for a call.

If they're not going over the responses in detail and then talking through them with the candidates, then they're just wasting their own time because they're not actually judging anything.

Re:I spent three months working full time to get a job by gnaritas on Sunday March 05, 2017 @12:59AM (#13794799)
That's a good way to get passed over for good jobs. As a potential candidate, you aren't in a position to making such demands and your unwillingness to demonstrate your skills on a simple assignment just means you won't be considered. Plenty of other fish in the sea who have no problem completing a simple assignment.
Re:I spent three months working full time to get a job by throw_away_777 on Sunday March 05, 2017 @01:42AM (#13794900)
It depends how desperate the candidate is for a job. A coding assignment may have a hidden cost of filtering out many qualified candidates, if qualified candidates don't feel the need to apply to companies with these assignments. Anecdotally, these assignments seem like just another filter companies use, they don't replace any steps in the process, just one more hurdle to pass.
Re:I spent three months working full time to get a job by gnaritas on Sunday March 05, 2017 @11:26AM (#13796687)
If you aren't willing to demonstrate your skills with a little coding assignment, I don't consider you a qualified candidate. I've used a coding test for years, always get exactly the good kind of people I want, it filters out the lazy and the liars, most programming candidates are liars and simply don't have the chops they claim.
Re:I spent three months working full time to get a job by idiot_stick on Sunday March 05, 2017 @09:32AM (#13796110)
>Plenty of other fish in the sea who have no problem completing a simple assignment.

And yet companies have an incredibly hard time hiring talent, even with so many other fish out there. Odd, that.

People need to start understanding their value as an employee. You create more value than you're worth; that's why companies need workers. You don't need to bend over for a potential employer. Plenty of other fish in the sea of employers, too.

Re:I spent three months working full time to get a job by gnaritas on Sunday March 05, 2017 @11:31AM (#13796722)
It's not odd at all, those are old school companies playing by the old rules of looking for candidates locally. And demonstrating your skills isn't bending over, it's showing your value and it's how you get a job. Seriously, this notion that you should be hired for a high paying job without needing to audition for it is just absurd; I wouldn't hire anyone with your attitude.
Re:I spent three months working full time to get a job by stale2002 on Sunday March 05, 2017 @01:36PM (#13797608)
I get recruiting emails literally every day, and people call me on my cell phone, unprompted, once a week. So yes, I absolutely am in such a position to make such demands. If a company doesn't like it, then they can do me a favor by passing me over.

And I am honestly just an average SF engineer.

The current engineering market let's me choose whatever company I want.

So, I am not going to waste my valuable time with companies that disrespect me, when there are a hundred more that I could be talking to instead.

Re:I spent three months working full time to get a job by gnaritas on Sunday March 05, 2017 @07:01PM (#13799696)
Great, but that's an artifact of living in the SF bubble which isn't anything like the rest of the planet. That is not the current engineering market, that's the current SF market. And asking you to demonstrate your skills isn't disrespecting you, you work in an industry that doesn't have a professional certification which means it's loaded with people trying to fake it for the big paycheck; due to that, it's perfectly reasonable for companies to ask for proof of skills. If that makes you feel disrespected, you aren't in touch which what it takes to run a business.
Re:I spent three months working full time to get a job by stale2002 on Monday March 06, 2017 @02:09AM (#13801161)
Don't care. I am the one with the power. And I have no problem using this power to my advantage.

The way that a business relationship works, is that the person with the power gets to make the decisions. And in the market that I am in, that person is me.

And I have no problem demonstrating my skills. I just demand that there is another person from the company, on the other end of the phone line or other end of the table, investing the same amount of time into the relationship as me.

If a company thinks that it is unreasonable for me to demand an equal time investment from them, well sucks to be that company, because as we have already established, they aren't the ones with the power, so their opinion doesn't really matter. They can go find someone else to interview.

Re:I spent three months working full time to get a job by gnaritas on Monday March 06, 2017 @10:02AM (#13803067)
> They can go find someone else to interview.

Oh most happily will, even talking to you is a pain, I wouldn't work with you if you paid me. You're arrogant and entitled, you'd make an awful employee.

Re:I spent three months working full time to get a job by PeterisP on Sunday March 05, 2017 @10:35AM (#13796361)
It may depend on the industry, but in tech generally there's not plenty of other fish in the sea - there's a scarcity of qualified candidates but plenty of other potential employers who desperately want to hire.
Re:I spent three months working full time to get a job by gnaritas on Sunday March 05, 2017 @11:29AM (#13796707)
That's really not true; there's only a scarcity if you insist on locality. There's no shortage of qualified remote workers when you open up your search the whole country or whole world. Employers crying about scarcity are employers who haven't figured out remote working is the future.
Re:I spent three months working full time to get a job by aisofteng on Sunday March 05, 2017 @02:16AM (#13794953)
If you're applying for a job, you're asking for the company to pay you a salary and to believe you can provide labor worth that salary. You can find a few hours.
Re:I spent three months working full time to get a job by shams93 on Saturday March 04, 2017 @11:44PM (#13794643)
I agree its not a process of applying for college, its a job. Testing to see whether somehow is a recent BSCS helps to systemically impose all 3 of the most problematic isms, racism. sexism and ageism. You can get brilliant employees from bootcamps, my current coworker is a truly brilliant bootcamp guy. He's African American and decided to skip student loans and go direct for code bootcamp and for front end he's really good. But if you tested him over recent BSCS type of stuff you would be screening out a brilliant front end developer.
Re:I spent three months working full time to get a job by prodigal_erik on Sunday March 05, 2017 @04:21PM (#13798751)
I wouldn't hire a frontend-only guy instead of a qualified developer, for the same reason I wouldn't hire a guy who can only mount wall outlets instead of a qualified electrician. Everything he didn't care enough to learn is a risk.
Re:I spent three months working full time to get a job by caconym_ on Sunday March 05, 2017 @12:22AM (#13794730)
If the homework assignment is at least somewhat related to the job (not CS esoterica, etc) then I can't really imagine a better way to measure the candidate's relevant programming skill, which is certainly not the only thing you're hiring for (if you're smart) but it's important and I don't really see how it reduces the "diversity" of the hiring pool in any undesirable way. Could you elaborate on your reasoning?
Re:I spent three months working full time to get a job by wahnfrieden on Sunday March 05, 2017 @09:16AM (#13796054)
People have children or other life situations that make it harder and less desirable on average to give up weekends and evenings for a homework assignment. It optimizes for people more willing and able to use their off-hours for work, which is not an even distribution across the population or even necessarily a desirable trait in candidates for that matter.
Re:I spent three months working full time to get a job by caconym_ on Monday March 06, 2017 @03:00AM (#13801347)
Assuming the homework assignment is happening in the hiring phase after the initial screenings, I don't buy this. Getting to that point means it's time to show them why they should hire you, and it's going to take up your time whether you do it in person or "asynchronously". If they give you the opportunity to spend those couple of hours at home rather than at a whiteboard in their office, but you don't care enough to make the time, I don't know why they should care enough to hire you.

If the "homework assignments" are just a scheme to get work done for free, or a competent engineer's time is not set aside to review them, then that's a different story. But as a fair test of programming ability, administered in good faith, I don't see the problem, and such a test is important.

Re:I spent three months working full time to get a job by pmiller2 on Saturday March 04, 2017 @08:50PM (#13794165)
I'd totally go for a 4 hour homework problem, if it got me out of 2-3 hours worth of technical interviews.
Re:I spent three months working full time to get a job by mcbits on Saturday March 04, 2017 @11:55PM (#13794676)
I'd rather do 2-3 hours of technical interviews than 2-3 hours of "revive your most traumatic memory and tell me about it."
Re:I spent three months working full time to get a job by timbowhite on Sunday March 05, 2017 @09:33AM (#13796112)
My advice to job seekers who are asked to complete a "homework assignment" by a potential employer:

Ask to see the company's employment agreements or contracts in writing first.

I was once given a 10 hour assignment, which indeed took that long to complete. Afterwards, the company expressed interest in bringing me on, and sent me a work agreement to sign, which included many unsavory terms such as being paid for completed work 90 days out.

Since their terms were shit, I didn't take the job, and lost 10+ hours of my life.

Re:I spent three months working full time to get a job by golergka on Sunday March 05, 2017 @06:09AM (#13795482)
When I was hiring, I used a homework problem as well - something that we have actually built and released, and I encouraged candidates to look at our implementation (it was a single screen in a very UI-heavy mobile game). We did it in 8 hours, but almost all candidates took more.

Overall level was pretty low that after reviewing about 20 homework assignments, and I had wasted a lot of time on post-mortem interviews where I just had to politely decline with a short code review (after all, they spent all this time, so they deserve something in exchange). After all, I started asking FizzBuzz (yes, not changing the name or anything) on the first phone interview to save time. And yes, turns out, it's not a task that any candidate can do.

So, yes - homework assignments are great, but make sure that a candidate at least knows how to write a simple loop (and yes, I overlook off-by-one errors).

Re:I spent three months working full time to get a job by matwood on Saturday March 04, 2017 @10:43PM (#13794474)
My current company does something similar. I think back when I had to do it, it took 2-3 hours. It's a pretty basic problem using strategies and observers. The next time we're hiring I'll probably update it.

The kicker though, like someone else below mentioned, is that we would receive submissions that didn't even compile.

What I liked about the HW problem is that even something simple gives you and the candidate something to talk about. Why did you do this or that. Tabs or spaces ;) etc...

Re:I spent three months working full time to get a job by Terr_ on Sunday March 05, 2017 @01:25AM (#13794856)
Daydreaming here: If every company's "homework" was representative of what kind of work you'd actually be doing, it'd be valuable enough to do.
Re:I spent three months working full time to get a job by hinkley on Sunday March 05, 2017 @05:57AM (#13795448)
I have not followed up with places because I was worried that the questions were representative.

Remember, the interview goes both ways. You can look dumb for your choice of questions just as much as the interviewee can look dumb for their choice of answers.

Re:I spent three months working full time to get a job by mr_tristan on Sunday March 05, 2017 @04:12PM (#13798679)
I also forgot to mention:

- The homework assignment wasn't open and public: it was an option after doing a brief (30 minute) phone interview.

- The other option was basically coming in for onsite technical interviews.

Re:I spent three months working full time to get a job by maverick_iceman on Sunday March 05, 2017 @07:51PM (#13799941)
Uber?