3 ms·

Not GP, but I would say that lack of attention to detail is a negative mark. Depending on GP's industry or team, that could be a dealbreaker. If you can't conn

Not GP, but I would say that lack of attention to detail is a negative mark. Depending on GP's industry or team, that could be a dealbreaker. If you can't connect to the server, or it returns a fatal HTTP error, a reasonable candidate would reach out via other means (assuming they aren't deliberately hidden or unavailable).

EnderMB 8y ago
We had covered all of these eventualities. We had an uptime badge on the repo to say whether it worked or not, and we encouraged developers to tag us on a GitHub issue or email us directly if something seemed wrong. We were also keen to stress that this should take far less than an hour of their time. We didn't want to see dependency injection, metaprogramming, or anything overboard that showcased a developers knowledge - this is purely just to see if they can deliver code that matches a requirement in the time provided. In the case where we had downtime (once in 18 months), I just forwarded their email to HR and we spent some extra time going over code in the sit-down interview.
ManlyBread 8y ago
If I would see that the server is unreachable I wouldn't contact anyone, I would interpret that as a red flag. The company would have no problem with deeming me unfit to work for them if I fail to complete the task - why should I consider working for that company when it's their fault that I'm unable to complete the task? What if this situation illustrates how the company works on the inside (no one takes care of the environments, things are constantly broken)? Is it worth it to find out?
- Maert 8y ago
  That's a lot of jumping to conclusions. A simple "Hey guys, the server seems to be down, not sure if you're aware. Can you let me know when it's back up so I can submit my request, as intended?" Shows understanding, shows willingness to reach out and solve problems, shows ability to delegate responsibility.
  - ManlyBread 8y ago
    My approach is merely a reverse take on "it is better to pass up a good candidate than to hire a bad one" that most companies seem to utilize. I'd rather refrain from continuing the interview (even if the company wouldn't end up being that bad) than wasting several months in a bad place.

EnderMB 8y ago

We had covered all of these eventualities. We had an uptime badge on the repo to say whether it worked or not, and we encouraged developers to tag us on a GitHub issue or email us directly if something seemed wrong. We were also keen to stress that this should take far less than an hour of their time. We didn't want to see dependency injection, metaprogramming, or anything overboard that showcased a developers knowledge - this is purely just to see if they can deliver code that matches a requirement in the time provided. In the case where we had downtime (once in 18 months), I just forwarded their email to HR and we spent some extra time going over code in the sit-down interview.

ManlyBread 8y ago

If I would see that the server is unreachable I wouldn't contact anyone, I would interpret that as a red flag. The company would have no problem with deeming me unfit to work for them if I fail to complete the task - why should I consider working for that company when it's their fault that I'm unable to complete the task? What if this situation illustrates how the company works on the inside (no one takes care of the environments, things are constantly broken)? Is it worth it to find out?

Maert 8y ago
That's a lot of jumping to conclusions. A simple "Hey guys, the server seems to be down, not sure if you're aware. Can you let me know when it's back up so I can submit my request, as intended?" Shows understanding, shows willingness to reach out and solve problems, shows ability to delegate responsibility.
- ManlyBread 8y ago
  My approach is merely a reverse take on "it is better to pass up a good candidate than to hire a bad one" that most companies seem to utilize. I'd rather refrain from continuing the interview (even if the company wouldn't end up being that bad) than wasting several months in a bad place.