Sorry, my wording left out a bit of detail and was confusing. Our process is:
1) 30 minute intro phone call to see if both parties are pushing in the same direction
2) technical review, which can take one of two forms:
a) 1 hour phone call (no computer needed)
b) take home coding exercise
3) in person phase to meet team, cross functional team members, and ceo
Because of the nature of this comment, I thought it'd be helpful to offer up option 2b directly if someone wants todo it without a phone call blocking things.
We offer the coding exercise as an option for a few reasons, but the most important one is that some great engineers are good on the phone and some aren't. While good communication skills are a must to performing well, doing well on a tech phone call isn't.
1) 30 minute intro phone call to see if both parties are pushing in the same direction
2) technical review, which can take one of two forms:
a) 1 hour phone call (no computer needed)
b) take home coding exercise
3) in person phase to meet team, cross functional team members, and ceo
Because of the nature of this comment, I thought it'd be helpful to offer up option 2b directly if someone wants todo it without a phone call blocking things.
We offer the coding exercise as an option for a few reasons, but the most important one is that some great engineers are good on the phone and some aren't. While good communication skills are a must to performing well, doing well on a tech phone call isn't.