3 ms·
I've considered this approach, but I worry that it consumes too much of the candidate's time. That it ends up favoring people who have the time and the financia
by eli 8y ago
I've considered this approach, but I worry that it consumes too much of the candidate's time. That it ends up favoring people who have the time and the financial freedom to do a full day of unpaid work.
- wonderwonder 8y agoThis is a valid criticism; however, they did not specify I had to turn it in the next day, I could have kept it over the weekend and not taken a day off of work. Several people kept it over a weekend with no penalty. I also could have worked on it at night after work. I definitely preferred this option as opposed to having to take a full day off for an in person interview and another for the follow up. I only took an hour off for the first interview as it was at 5 and I just ran home and threw on a suit jacket and a couple hours for the final interview as it was close to the same time. If I had already worked in the js stack they asked me to use the entire project build would have been 5 or 6 hours and that's only because I really wanted to impress, I could have knocked it out once my kids went to sleep. But as in everything it depends on the person and their life circumstances, we all have different things going on.
- camjohnson26 8y agoI have been interviewing recently and started turning down any coding assignment that will take more than a couple of hours. To get a reasonable number of offers to enable you to negotiate requires going through the interview process for several companies since some percentage of them will turn you down. After a phone screen I don’t have enough information about the role to be able to potentially waste 10-20 hours on a toy problem. A few companies gave a simple api project or a timed hacker rank and those feel reasonable. An entire web app with database, rest api, front end and CI pipeline following production code best practices does not.
- dragonwriter 8y ago> To get a reasonable number of offers to enable you to negotiate You only need 1 offer to negotiate.
- the_jeremy 8y agoWhile technically correct, I think most people agree that it is better to field several offers simultaneously so you can choose the best culture fit for yourself as well as being able to provide a concrete example of someone offering you a higher salary to most easily justify your counter-offer.
- wonderwonder 8y agoNegotiating a salary is a situation I have never been in as I have always told them up front before interviewing how much I want to get paid after finding out the salary range. Whenever a recruiter calls, I ask the salary first and tell them where I want to be on that range before even sending a recent resume. Not that negotiating for more if I have several offers would not be great, just not something I have experienced. I interview, they already know my number as I have already asked the hiring salary range and told them what I want. If I pass the interview they offer me my original request and we move forward. I could see how if one was interviewing with multiple companies and had multiple offers how one could seek to play them against one another for a potentially higher amount. Just hasn't happened to me.
- pjc50 8y agoFirst you have to find out the salary range, and a horribly large number of companies are secretive about this.
- scarface74 8y agoThat’s the easy part - don’t apply blindly. I’ve always gone through local recruiters that have relationships with the hiring manager. They know the salary range, the interview process, and where other candidates fail because they get feedback from both the candidate and the hiring manager.
- pmiller2 8y agoHow is that any different from taking a whole day to do a normal onsite interview? Doesn’t that also favor those with the ability to take a day to jump through hoops?
- onion2k 8y agoAt my company we pay the candidate at a typical freelance rate.