Is it just me or shouldn't we be moving towards projects rather than code interviews? I think you can recover far more about a person in a project setting than by asking them a couple of random questions to solve in X time.

Time wise it costs too much for the candidate.

Haha thanks for this, I actually signed up for this a while back and completely forgot the name of the site.

It looks pretty nice, I hope they didn't forget about concurrency and parallelism. I don't see anything talking about this in the iBook.

I'm sure that the main mechanism will be the existing dispatch queue libraries Apple's other languages use.

I actually was not, I didn't understand the relationship between the two languages. I see now that they are not related at all. By the way, it's "You're trolling"

Location: Toronto, Canada, Local/Remote/Relocation, Full Time (for the summer, graduate in December)

Stack: Go, Docker, Node, Javascript, Mongodb, D3, Python for Data Sci, R (but I prefer Python :))

Github: http://tinyurl.com/pb8wgk2

Contact: dluna132@gmail.com, more info on request

I'm comfortable doing any role. I've worked on backend, frontend at a startup and done data related activities on the side or through online courseware I've taken (I've done a lot of this).

Ideally I'd love to work at a startup where I work on a mix of backend and data/ML roles.