News for hackers. Stuff that matters.
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 ?