3 ms·
I live in a major metropolitan area not on the west coast. When I’m looking for a job, I change my LinkedIn status to “actively looking”, call a list of recruit
by scarface74 7y ago
I live in a major metropolitan area not on the west coast. When I’m looking for a job, I change my LinkedIn status to “actively looking”, call a list of recruiters that I have worked with in the past, and usually have two or three offers in hand within two weeks to a month.
For whatever level I’m at at the time, usually companies pay within a narrow band ($10-$20K). Why should I waste time doing an at home coding test when I can get a job that pays just as much just by answering a few behavioral interview questions and describe my past career history?
I’m no special snowflake. I’m just your average everyday CRUD/SAAS software developer/architect/team lead depending on how the wind is blowing.
- spuz 7y agoWould you work for a company that spent 0 time vetting you? There has to be a "right" amount of time for evaluating candidates and the amount of time the candidate is required to give up when looking for a new job is only one side of the equation. Unless you want to work somewhere that has no hiring standards, you should not dismiss the time taken for take-home tests as wasted without evaluating their effectiveness vs other methods.
- scarface74 7y agoI had two offers before I took my previous job. At Job 1: the interview was a white board interview where he wanted me to write a merge sort. He asked a few questions about my background and had to model a database schema and write a few queries to answer done questions. The 2nd offer was after an interview where I had no language questions, he asked me about how I would design a development process “if I ruled the world”, methodology about dealing with legacy code and integrating it with a mobile app via APIs, my feelings about testing, what trade offs I had to make based on “business realities”, etc. The first offer was full time, a shorter commute and paid more. The second offer was contract to perm, if I translated it to an FTE salary it paid less (I ended up making more since I got paid by the hour), and it was a longer commute. They were both supposedly “senior software engineer” jobs. I took the second offer. I didn’t realize at the time that they were actually looking for a dev lead. When they bought me on perm they matched the offer of the first job. Are you really not able to tell someone’s experience if they have been in the industry for awhile just by talking to them? The truth is that most developers are “dark matter developers” doing yet another software as a service CRUD app or a bespoke internal app that will never see the outside of the company.
- derivagral 7y agoI effectively did this. No whiteboarding, no code stuff, just a phone call and an onsite with coworkers and boss. Small team, range of technical talent, but a much better fit for me compared to the larger (or smaller) standard advertising companies in the area that run 4-6 hour take home tests followed by a day of whiteboarding. You do not need to haze candidates, but you do need to test for basic ability. As for vetting the company from my side: there's a bunch of mentoring and refactors that needed to happen with prior code, sure, but nothing game-breakingly broken. I've viewed this as a great mentorship setup, not as a "time to post another N+1 select to dailywtf".
- subhobroto 7y agoSpot on. I think there's a major disconnect in candidates wanting to be treated respectfully and companies that offer take homes I have a suspicion that companies that offer take homes expect the candidate to cheat in some way or the other and begin with assuming the worst. ... or they are simply going off the data that they have. I think majority of the candidates cheat by simply severely under-reporting the time it took for them to complete the assignment. 99% of the take home offers I receive are "our candidates typically take 2 hours to complete this assignment". These are not tests for basic coding proficiency. These are tests to check if you can build a full stack application - backend AND frontend including a README, tests and majority of candidates are typically taking 2 hours to complete. I can get a GraphQL/Express server up and running from a frequently used template I built, in 90 minutes will full support for Query, Mutation and Subscription. Create new users, tasks, updates, votes? Check Update users, tasks, updates, votes? Check Get realtime notification of changes to users, tasks, updates, votes? Check Apparently there are others who can not only do this but also implement a react frontend that puts the UI support for these as well in just 30 minutes more. Either candidates are reusing templates they have built in previous projects and not reporting the time it took them to build the template when they report the time Or, they are grossly under-reporting the time it took for them to complete the assignment. We are doing this to ourselves. We should not deflect the blame. If we feed garbage data to companies and then companies base their decisions off that, it's absolutely unfair to blame companies for not being realistic