Hacker News Reader

Comment by gkoberger | Hacker News Reader

Yup! We have projects and ideas ready to go if they don’t have one :)

For people like this, though, I’ve seen many use it as an opportunity to work on something they’ve been wanting to for a while and never had the time! A Hello World in a new language, merging in PRs on an old repo, writing a script to automate something or even a take home coding exam for another company.

View on HN

In the example interview schedule in your blog post there's only an hour allocated for BYO project discussion. Is that representative of your typical interview schedule? The scope of some of your examples in the blog post may be challenging to cover in much detail in the first hour working with brand new collaborators, although perhaps is enough for calibration. Are you able to share any examples of the fun projects/ideas you have as suggestions for candidates that don't have a project of their own?

Yup, we do an hour. After that, it feels like there's diminishing returns. There's absolutely no expectation anyone will "finish", and we make that clear. It's the journey we're interested in, not the destination.

One that we tend to do a lot is creating an image gallery using Flickr or Unsplashed's API. It's vague enough that people can take it in whatever direction they want, and simple enough that you can get pretty far in an hour.

I was surprised it was that long, I can talk about a project for much longer than an hour but the average interviewer won't give a shit past 15-30 minutes.

It's not just talking, you'd also be adding a feature or fixing a bug or something like that :)

Could expand on that? I only have 45 minutes and can't have them bring in a project unfortunately.

Do you have some legal/security issues?

I ask people to send me code they've written via email or links to projects and go through that.

Reply on news.ycombinator.com