Hacker News new | ask | show | jobs
by notTyler 2592 days ago
I am not a Senior. Not junior, not senior. I have been interviewing lately after my company staffed me as the only remote member of a team based in Argentina. (Live in the midwest USA, don't speak a lick of spanish).

I typically won't do programming challenges. I don't believe it's fair for the applicant, because if it becomes the industry norm then applying for 10 jobs means 10 separate programming challenges just for the opportunity to get an onsite. But, recently, during a phone interview with a shipping logistics company with a common first name in their name, I vibed with the lead I spoke to and decided I would give their hackerrank a go.

There was an interpolate json feed into an object question. There was a semi-complex array sorting / manipulation question. There was a javascript quirks question. There was a sql question that I probably would have solved using both code and sql rather than just sql. The solution I came up with was using a temp table, that hackerrank permissions did not allow. The array question, my (working) solution timed out because one of the tests used an array with several million units in it. There was no indication of a certain time this should run under. It took about five minutes after submitting to realize a way that probably wouldn't have timed out, but at the time I was happy with my solution given the whole test was timed and I had written six lines of code to solve this problem.

The final question of the test, after all of these and a few I won't go into, was to write an html form field that updated a list via javascript and had alternating CSS colors. I was so frustrated that they would throw in something so very menial and time consuming after the rest of the (timed!) test that I didn't even attempt it. (to be clear, basic javascript knowledge had already been demonstrated on the prior fizzbuzz).

I had really thought my answers would grant me an onsite, but it didn't. So yeah, back to not doing stupid timed tests.

This was a month ago. The position is still open and I expect it to be for the near future.

If anyone read this far, I have given some thought about my various interviews after some interesting ones recently (another recent time at a .net shop I was asked to demonstrate sorting a list so i did a toarray() then sort and they were like no, do it manually).

I'm probably going to put together a blog about my interviews over the years since I've had all sorts. I feel like as deep as retrospective as I can remember over my decade of interviewing might give me some insight as how I should be better.