| > How much faith do you really have in these questions? It depends entirely on how you direct the converstation. > After reverse engineering the launch protocol, we discovered that we could increase speeds by 5x simply by limiting the fuel cell usage Tell me HOW you reverse engineered it. What tools did you use. What source did it wind up as. What problems did you encounter? >Oh tell me about your rocket fuel cell usage (Don't ask that question because you don't care about rocket fuel cell usage, you care about if this person is a good coder. Ask them questions about code and their person software process!) >What did they do for testing: We used Jest. Was it automated: Yes. Obviously it's on you to tease out more than one word answers. If you want to have a conversation with somebody and learn if they're capable of something, the onus is on you to direct the conversation and get what you need. If you're willing to accept one word answers, then I'm thinking this "informal chat over a few hours" approach is not for you. |
And that, by switching to the "Hello, nice to meet you, okay let's open up Coderpad and solve this problem", as "inhumane" as it sounds, and I KNOW we will continue to see these forum threads for years to come, it actually WORKED to find some seriously amazing candidates who could actually showcase their skills LIVE.
It's like, there's knowing your implementation details, and there's actually implementing something.
Honestly, as a candidate, I prefer the technical challenge now. Partly because my brain isn't equipped to even remember deep implementation details of specific projects. Think about it, how much can you really remember from the last project you worked on? Is that result going to give you more concrete details than actual code on a small problem? I think companies will continue to use Coderpad because it just gets to a clear result faster.