The latest trend for tech interviews: Days of unpaid homework
81–90 of 1001 posts
Re: The latest trend for tech interviews: Days of unpaid homework
#82Maybe paying people for the time if you end up saying "no" is a nice compromise?
If you are potentially serious about hiring the candidate and they are serious about potentially working for you, doing some "homework" does not seem like a major amount of effort in the grand scheme of things to me.
Re: The latest trend for tech interviews: Days of unpaid homework
#83I'd much rather do a timed coding test for 30 to 60 minutes and be done with it.
Re: The latest trend for tech interviews: Days of unpaid homework
#84I don't want to name names but one YC company I interviewed at left me with the distinct impression that they talked a big game, just to get me to work on one of their (apparently) "strictly-hiring-related toy projects" as homework. Homework, "sure", except it: 1) integrated with a real system, 2) mirrored something they actually did, and 3) they would only agree to proceed if I signed an IP/work contract and accepte…
I have noticed a trend of not naming companies here. Is it against the rules? I fell that we should name and shame companies that are disrespectful of peoples time.
Re: The latest trend for tech interviews: Days of unpaid homework
#85I'm a general contractor (Unicorn Homes Inc.) and I'm currently building a number of spec homes. We're going to need electrical work done in all the homes and I'm in the process of sub-contracting out that work. What I need from you, Joe Electrician, is for you to go wire the kitchen of one of these homes. Once you're done I will inspect your work and let you know if I'm interested in hiring you for more work.
Re: The latest trend for tech interviews: Days of unpaid homework
#86I worked for a company that did a 3-day, challenging take-home problem. It was a big ask, but it was amazing for getting a sense of people's problem solving and coding abilities. (The final result would only be 1000 lines of code or so, but 3 days provided time to think and experiment with different approaches.) Maybe paying people for the time if you end up saying "no" is a nice compromise? If you are potentially se…
Re: The latest trend for tech interviews: Days of unpaid homework
#87I worked for a company that did a 3-day, challenging take-home problem. It was a big ask, but it was amazing for getting a sense of people's problem solving and coding abilities. (The final result would only be 1000 lines of code or so, but 3 days provided time to think and experiment with different approaches.) Maybe paying people for the time if you end up saying "no" is a nice compromise? If you are potentially se…
They make it a point of ego / pride that they have such a long, arduous process. They've even mentioned the occasional candidate who asks about billable hours for an 8+ hour code problem, saying "Who the hell does that guy think he is?" Of course, they were shocked and appalled when I asked who they thought they were to ask someone to spend 8+ hours of their time on an code test before even having so much as a phone screen to determine compatibility.
As it were, this was a company in the contracting space so I assume this is an intentional filter to weed out all but the most compliant individuals. If you're not willing to bend over backwards, they're not interested.
Re: The latest trend for tech interviews: Days of unpaid homework
#88Earlier quoted context omitted.
are you willing to pay for it? Would you pay the candidate a reasonable sum This would be additional income complicating tax, and many companies restrict employees from taking on outside paid work without approval. No matter how you slice it, these multi-hour homeworks are a stupid idea. And the real reason for them is to discourage candidates to justify getting indentured labour instead. Or to discriminate against o…
This would be additional income complicating tax, and many companies restrict employees from taking on outside paid work without approval. It seems wrong to reject a good idea because other bad idea will interfere with it. Maybe I'm fortunate; I take extra irregular work in the sum of about 30 days a year, and at the end of the year HMRC and I settle up very simply and easily. I couldn't imagine taking a contract tha…
It’s usually about avoiding conflicts of interest - you can generally get the box ticked easily enough to do something unrelated to your job with them. But “doing an audition at a competitor” is unlikely to be signed off!
But even so - these homework assignments are stupid, and discriminatory on factors unrelated to job performance, and no other industry does it. In fact they yield worse candidates because quality candidates don’t tolerate this kind of nonsense.
And how would this work - you take vacation to do your trial period? You quit to do a trial period knowing it’s still an interview not even an offer?
Re: The latest trend for tech interviews: Days of unpaid homework
#89When i interviewed for a backend development position, the task was to set up flask with two routes, connect to a dB and retrieve a couple of rows when user visited the routes.
It was not hard even though I never worked with flask before, and it wasn't supposed to be hard either. It was a test if I had basic programming skills and that was it.
Re: The latest trend for tech interviews: Days of unpaid homework
#90Then give up to 3 months of mentorship. If the person doesn’t look like they meet expectations, then fire her quickly. Give them the remaining time up to 3 months as severance.
This is the best way to do it because you're not subjecting people to bad interviews, and you're giving them up to 3 months severance if it doesn't work out.