Re:We compiled a library of realistic engineering take-home ...
by alexyang21 on Thursday August 25, 2022 @06:38PM
(#32600863)
Yes! I spoke to Andy (the author of the article you linked) when he posted this. I'm a big fan of this approach. And the software we're building is quite similar to the interview-bot one that GitHub uses internally. Why shouldn't every eng team be able to benefit from tools like theirs?
I'd love to add GitHub's take-home to the library, but I feel the article describes the exercise without sharing the actual prompt. If there's a public link to it, lmk and I'll add it.
Re:We compiled a library of realistic engineering take-home ...
by noisenotsignal on Thursday August 25, 2022 @06:54PM
(#32601035)
You’re right, I don’t think their exercise is public. I just wasn’t sure if you knew about it and felt it was good enough to call out.
This is awesome to hear! I did check out your website but wasn’t sure how closely it tracked with the GitHub method.
Honestly, I had a thought to build something like this after my GitHub interview but wasn’t sure how much traction it would get. It’s cool that you’re working on it and that my random thought was validated; best of luck!
Edit: to be clear, the interview was live with an interviewer. So it wasn’t a take home in the scheduling sense either.
I agree that take homes can be simplified with your suggestions above, and that certainly makes a better experience for the candidate. The hybrid format is also great - future interviews become an extension of your previous work, so it’s more comfortable than having to context switch for a new challenging problem each round.
I didn’t find this in your linked database, but I also enjoyed GitHub’s take home. I only recall spending 45-90 minutes on it, and the setup process was seamless. A recent blog post describes their approach here: https://github.blog/2022-03-31-how-github-does-take-home-tec...