5 ms·
Some reasons against a 1 week working interview: * It can take up to a week just to get someone ramped up with access to things in many environments (setting u
by amorphid 10y ago
Some reasons against a 1 week working interview:
* It can take up to a week just to get someone ramped up with access to things in many environments (setting up accounts, configuring dev environment, etc.) It's not free to create and disable a dev's access.
* Most places I've seen aren't set up to ramp someone up in a week. I think Pivotal Labs gives people a try for 3 week contracts, and they have a culture of ramping up new hires via pair programming in XP environment.
* You'd only be productive in an environment where you are already familiar with the tools they are using. If they're using Erlang, and you're coming from Java, you simply couldn't do much with Erlang in a week.
* Many places can't/won't put you to work without you passing a background check.
* Candidates who already have a job aren't likely to be in a position to take a week off to work for someone else.
- dimino 10y agoYou make a good point, but if I'm getting to pick my ideal work environment though, it's one where I can get ramped up and contributing meaningfully in a week.
- jacalata 10y agoPivotal Labs definitely doesn't require a 3 week contract before hiring, and it never even came up as a theoretical option when I interviewed with them and got an offer last year.
- amorphid 10y agoGotcha. Maybe the one example I am remembering is a special case, or that person simply didn't work out after three weeks.