Earlier quoted context omitted.
As something of a counterpoint, a literal 4-hour assignment isn't that bad--especially as an alternative to a day of interviews. If they give you the assignment and it's immediately obvious that it's actually a 20+ hour assignment, you can always just walk. When I worked for a technology analyst company, we would ask for writing samples--which most potential hires would already have. But, if someone didn't, they'd ha…
No it's not. When i do interviews in-person (even if virtual) , I get the benefit of meeting my future colleagues and learning more about the company. It's much more a two-way benefit, versus an assignment where only one party (the company) gets any information from the other (me). > When I worked for a technology analyst company, we would ask for writing samples--which most potential hires would already have. But, i…
I don't have a very large open source portfolio, but I it's probably bigger than 95% of the people I work with, I don't think my open source work is particularly representative of my abilities.
Companies want to have a somewhat standardized hiring process so that they can evaluate candidates fairly, and most professional developers people don't do much open source work.
Someone having an impressive open source portfolio, might be a good signal that they are a great hire, but I don't think it's a good general strategy for hiring.