4 ms·

Dev here. I wish I could find a company that interviewed me like this: - Take home work immediately. Maybe it's just me but I'd rather not get this after the p

Dev here. I wish I could find a company that interviewed me like this: - Take home work immediately. Maybe it's just me but I'd rather not get this after the phone screen and whatever else. Just give me the work and have me submit it with my application or after I apply. - Phone screen. This is important. When I say a phone call, I mean a phone call. I've interviewed with companies that refuse to have a regular phone call and will only do video calls over skype/hangouts/whatever. This is such a Silicon Valley thing. Guess what? Not everyone is in a situation where they can easily setup a video call. I know I'm not. - Technical interview. Honestly the best technical interview I've seen is where the company ask you to get one of your old projects, walk them through how and why you structured the code the way you did, and then pair program with someone on the team and add a feature to the project. If you don't have past projects like that you can pair program on their code base. When it comes to technical interviews and take home work, if you are asking questions that can be googled in 5 seconds then you are just wasting my time.

afarrell 10y ago
My company (GoCardless) does pretty much this except: 1) There is first a very short phone chat with one of our recruiters to see what sort of role within our team you're interested in, let you ask questions, and to make sure you're clear on the scope of the take home challenge. 2) For the first technical interview, we have you talk through your approach to the take home challenge. Not everyone has publicly available code that they can walk through and not everyone's publicly-available projects are good for a discussion with any given one of our engineers. The pair programming interview is also on a challenge that we've standardised and calibrated with the team.

afarrell 10y ago

My company (GoCardless) does pretty much this except: 1) There is first a very short phone chat with one of our recruiters to see what sort of role within our team you're interested in, let you ask questions, and to make sure you're clear on the scope of the take home challenge. 2) For the first technical interview, we have you talk through your approach to the take home challenge. Not everyone has publicly available code that they can walk through and not everyone's publicly-available projects are good for a discussion with any given one of our engineers. The pair programming interview is also on a challenge that we've standardised and calibrated with the team.