Live data from Hacker News

The latest trend for tech interviews: Days of unpaid homework

work.qz.com

991–1000 of 1001 posts

Re: The latest trend for tech interviews: Days of unpaid homework

#991
post #388

Earlier quoted context omitted.

I used to hate it, but have now performed enough interviews of supposedly senior devs with decades of experience. I've literally seen someone who did firmware for the space shuttle grind for 45 minutes on fizz buzz without making progress. Like, I'd they struggle for ten minutes or so, I take a step back and say "Ok, screw syntax, let's just vaguely talk about what needs to happen and mock up some pseudo code.". Even…

Perhaps it's because you insist on testing their ability to live code on the spot as a performance piece, and misinterpreting that as testing their ability to code. If you're turning down someone who wrote space shuttle firmware, because they "can't do fizzbuzz", then you are administering a terrible test and getting a false negative. I have 20 years of industry experience. Everything on my resume is the truth. I've…

That is why I advocate for a hypothetical "bar exam" for the software programming profession. I also posted a question concerning that: https://news.ycombinator.com/item?id=16702389

Going through a series of technical filters is not a problem in and of itself. The problem is that each company has its own set of filters, many times with skills that don't necessarily transfer to other interviews.

With the "bar exam" approach, you only need to pass 1 exam for N number of companies, leverage that to fast-track through a company interview. With the current approach, you need to take N exams for N companies, and return to square one if you fail. There is no extra layer of validation that lets you keep a "ahead" placement in these interviews. Company specific interviews should focus on basic soft skills, and if they mesh well with the team.

I'm an experienced programmer- not yet considered senior level, but have worked at several companies -and having a hell of a time going through my latest job hunt.

I have been applying for jobs for 3 years straight now, and it's telling that the only offers I've gotten were three short term contract gigs- one from a past employer who's already familiar with my work, and two from small studios with a very informal process where they just looked at my resume and Github projects and with that, they were very convinced that I'm the man for their job. I took these jobs mainly to add more skills and to fill up the gaping time hole in my resume.

But for the "regular" full-time jobs at businesses, big or small, local or on the west coast (I'm a midwesterner), I have not gotten an offer. I've been through many tests and live coding going through a lot of things. Triplebyte expects you to be a speed demon, but at least they give detailed feedback on what you did wrong.

So what is with the saturation of applicants and tendency to make the hiring process slower and slower? That's what these coding tests and interviews do, they make the process slower.

It's not 2009 anymore- unemployment is reasonably low, so this current phenomena of rigorous testing shouldn't happen. More programmers need to discover and embrace the power of collective bargaining.

Re: The latest trend for tech interviews: Days of unpaid homework

#992
post #991
post #388

Earlier quoted context omitted.

Perhaps it's because you insist on testing their ability to live code on the spot as a performance piece, and misinterpreting that as testing their ability to code. If you're turning down someone who wrote space shuttle firmware, because they "can't do fizzbuzz", then you are administering a terrible test and getting a false negative. I have 20 years of industry experience. Everything on my resume is the truth. I've…

That is why I advocate for a hypothetical "bar exam" for the software programming profession. I also posted a question concerning that: https://news.ycombinator.com/item?id=16702389 Going through a series of technical filters is not a problem in and of itself. The problem is that each company has its own set of filters, many times with skills that don't necessarily transfer to other interviews. With the "bar exam" ap…

I've been advocating for the same thing except I call it a "Software Engineering License".

Re: The latest trend for tech interviews: Days of unpaid homework

#993
The whiteboard interview is coding's version of being asked to do a freestyle rap. It's largely orthogonal to creating good code, but it's also a trainable skill that arguably does show something, even if that something is just a willingness to play the game. Whether it's worth seriously training for is another matter.

Cue the music (sung to the tune of Eminem's 8 Mile Road, see https://bit.ly/2iI8tG2) and the scene of a nerd sweating in front of the whiteboard as the interviewers nod their heads to the beat:

Sometimes I just feel like, quittin', I still might Why do I put up this fight, why do I still write (code)?

Sometimes I just hate life, something ain't right Hit the brake lights, case of the stage fright Drawing a blank like

It ain't my fault, great big eyeballs My insides crawl, FizzBuzz I scrawl And I clam up, I just slam shut

Gonna travel this road Gonna show 'em my code My Big-O is so dope the universe will implode (as our hero proudly writes = O(1/n^2) on the board)

etc. Someone can make a viral video; I'm too busy practicing code problems.

Re: The latest trend for tech interviews: Days of unpaid homework

#994

Earlier quoted context omitted.

The problem is that a lying liar will also have a resumé like yours. How can I — who have never met you, and have no-one I trust recommending you to me — differentiate between gaius the awesome developer and gaius-prime the lying liar? I've got to administer some sort of test to distinguish the two, and the likeliest sort seems to me to be one which attempts to discern whether one knows the sort of stuff gaius would…

Which makes asking for a resume, rather pointless. There would likely be a lot more acceptance of fizzbuzz take home tests and so on; if that was instead of writing up resumes (replace one time suck with another instead of adding a second one in). However that makes it hard to justify paying recruiters. Given how Da Vinchi had a resume its amazing we still use them. (His was better thoigh, it had his name and address…

>Which makes asking for a resume, rather pointless.

I wouldn't go that far. It still weeds out the honest-but-unqualified with minimal effort - it's basically a good early filter. This actually works for the candidate too - how much would it suck to 6 hours of interviews and then get told you don't have the right degree or some such?

Re: The latest trend for tech interviews: Days of unpaid homework

#995
post #861

Earlier quoted context omitted.

If it's anything like white boarding, then they would bring in a game of operation and have the surgeons pull out all the pieces. If the buzzer goes off, well they just aren't good surgeons.

Very apt. But I'd really like to know why a medical degree means "can perform real medical work" while we're OK with a CS degree meaning "well, she has successfully completed the degree requirements, but hey, actual software development is not part of it".

Surgeons do different things.

However, CS is close to something else: Economics. People spend 4+ years learning about economics, but don't know shit about how it really works. They found a solution for that: business schools.

CS at a University versus CS at a technical college.

Re: The latest trend for tech interviews: Days of unpaid homework

#996
post #691
post #675

Earlier quoted context omitted.

Yep, that’s what I needed to hear. I’m really glad I retracted my resume. Even though I’m nowhere OP’s level, it felt a bit degrading.

If you're capable of developing software, being offered $15/hr /even without any interview at all/ is just broken. This is not about the interview process, that's just an old fashioned screwjob. I'm really confused by your situation. What are your qualifications and seriously what kind of compensation are you receiving right now if you are employed? If you want to talk, email me at my username at gmail. To put things…

Just so we’re clear, I did email YOU, right? I don’t mind if you don’t answer but I’m wondering if you got it at all.

Re: The latest trend for tech interviews: Days of unpaid homework

#997

Earlier quoted context omitted.

I attended catholic high school in nyc from 1965 to 69 and we wore a sport coat and tie with dress slacks. Hair length inspections were conducted. It didn't kill anyone as far as I know.

The way I've always seen it, if you insist on being able to dress the way you want as a means of self-expression, then you really don't have anything worth expressing. Dressing for comfort, or to suit the physical demands of your job are valid motivations. I wore a shirt and tie at my first job (back in 1987), but within a few years, I didn't bother any more because no one else did. Nowadays, "business casual" is fin…

"If you insist on being able to dress the way you want as a means of self expression then you really dont have anything worth expressing."

My initial reaction was to guffaw at the ridiculousness of such a statement. Expression through fashion and attire is pretty much the entire reason we dont all wear the same thing as each other every day. I feel the exact opposite as you: people who dont dress with the awareness that their appearance is a statement to the world they walk into are missing a massive opportunity to affect their day. How people treat you. How people respond to you. Etc.

But since I'm growing less cynical in my old age, I would care to learn more about your perspective if you care to share.

Re: The latest trend for tech interviews: Days of unpaid homework

#998
How many of these homework assignments become actual code that companies use? If you ran a business and your programmers were all busy but you wanted some new widget, what is preventing you from posting a job and tricking 100+ programmers into bootstrap your project for free?

A friend recently spent a week building a chat server with a very specific telnet/ssh interface as a "code test" for a video game company. I helped him test it and it was really solid. He walked the interviewer through the setup and how everything worked and then never heard back from them. I suspect that they simply used his code in their next project. What's stopping them from handing over his code to the next round of applicants with the assignment of adding all the features they need? They could post a high salary and offer great benefits, but never actually hire anyone.

We, as developers, simply can't be giving away free work. We're all aware of how opportunistic business folks can be. I refuse to do "homework assignments" (unpaid work) and so should you.

Re: The latest trend for tech interviews: Days of unpaid homework

#999
post #301

It's unreal that will people will bitch and moan about having to invest a couple days, maybe even a whole week in cramming/prepping/interviewing, to perform on-demand, one time, for a job that realistically will earn them $100k, $200k, $300k, $400k+ a year. Meanwhile people that work harder than us 5 days a week for the entire duration of their career will make 1/2, 1/4, 1/6th, or less of income, with none of the per…

There ought to be a formally-named logical fallacy for the "we shouldn't attempt to fix this problem, because someone somewhere else has it worse than we do" attitude.

Re: The latest trend for tech interviews: Days of unpaid homework

#1000

Earlier quoted context omitted.

Haha, I'd love to see it if that's true. I love cool approaches to computation. FWIW as long as you can back it up with knowledge of what the relevant tradeoffs are (and don't scoff at a more KISS attitude for doing actual work), you're pretty much guaranteed to get a thumbs up from me if you give an answer off the beaten path.

I dislike traditional phone screens enough that I hone unusual solutions for them. And when they get evil enough, I put them in a public repository. Here's my FizzBuzz: https://github.com/ubernostrum/interviewer-hell/blob/master/...

How is that not iterating (admittedly within the stdlib methods)? They are not literally for loops, but the same concept of iteration.
Post reply on HN