4 ms·

I think it's the 6 hour take home coding that's a problem. I would suspect that when hiring writers, they look at a sample of the writer's past work and don't r

by yosito 5y ago

I think it's the 6 hour take home coding that's a problem. I would suspect that when hiring writers, they look at a sample of the writer's past work and don't require the writer to spend 6 hours writing a sample children's book.

raxxorrax 5y ago
Would be nice to have an example. 6h/40h software development doesn't really say much about scope and is highly dependent on your experience with the tools necessary to perform the task.
thinkharderdev 5y ago
The 40h paid project also seems kind of crazy to me. It is nice that is is paid but almost every software engineer I have ever interviewed already had a full-time job and was looking to switch. Where are they supposed to find 40h to work on a side-project even if it is paid? Is the idea that you are supposed to quit your current job first before interviewing?
- aix1 5y ago
  > Where are they supposed to find 40h to work on a side-project even if it is paid? On top of that, taking on paid outside work in the same field could also be contrary to the candidate's contract with their existing employer[*]. [*] This no doubt depends on the employer and the jurisdiction.
  - lifeisstillgood 5y ago
    Of course !
yawaworht1978 5y ago
I had both a full day on site JS programming(css optional) and a 20hr take home reactJS exercise besides all the precious onboarding stuff, pretty crazy effort, for both parties, time is money. For one I had to take a day off, the other i did over a weekend. Another thing I have realized, all the jobs valued php and bit SQL more as basic knowledge for web dev than any nodeJS/MongoDB even if it's just front end, they want some back end understanding. Had some nodeJS things that generated all the front end via express , including chat module and sign up/log in flow, but either it was overlooked or not valued, any 5 minute to do list or crud with anything front end JS seemed more important. I suppose few dare to touch the node ecosystem and nosql databases. And the most recent one asked me if I can do their front end in react(really overkill, no need), told them I'll do it in vanilla JS, but nope, he insisted on react and that was the end of the story. Was for a MVP and would be the sole dev for a while. I have found in general that speaking to hr is not useful, if you get past that and a senior dev (not a manager or product owner) interviews me, it would be a good experience.

by yosito 5y ago

raxxorrax 5y ago

Would be nice to have an example. 6h/40h software development doesn't really say much about scope and is highly dependent on your experience with the tools necessary to perform the task.

thinkharderdev 5y ago

The 40h paid project also seems kind of crazy to me. It is nice that is is paid but almost every software engineer I have ever interviewed already had a full-time job and was looking to switch. Where are they supposed to find 40h to work on a side-project even if it is paid? Is the idea that you are supposed to quit your current job first before interviewing?

aix1 5y ago
> Where are they supposed to find 40h to work on a side-project even if it is paid? On top of that, taking on paid outside work in the same field could also be contrary to the candidate's contract with their existing employer[*]. [*] This no doubt depends on the employer and the jurisdiction.
- lifeisstillgood 5y ago
  Of course !

yawaworht1978 5y ago

I had both a full day on site JS programming(css optional) and a 20hr take home reactJS exercise besides all the precious onboarding stuff, pretty crazy effort, for both parties, time is money. For one I had to take a day off, the other i did over a weekend. Another thing I have realized, all the jobs valued php and bit SQL more as basic knowledge for web dev than any nodeJS/MongoDB even if it's just front end, they want some back end understanding. Had some nodeJS things that generated all the front end via express , including chat module and sign up/log in flow, but either it was overlooked or not valued, any 5 minute to do list or crud with anything front end JS seemed more important. I suppose few dare to touch the node ecosystem and nosql databases. And the most recent one asked me if I can do their front end in react(really overkill, no need), told them I'll do it in vanilla JS, but nope, he insisted on react and that was the end of the story. Was for a MVP and would be the sole dev for a while. I have found in general that speaking to hr is not useful, if you get past that and a senior dev (not a manager or product owner) interviews me, it would be a good experience.