6 ms·

Also of note, the largest contributor to the package manager is Max Howell (mxcl), the creator of Homebrew: https://github.com/apple/swift-package-manager/grap

Also of note, the largest contributor to the package manager is Max Howell (mxcl), the creator of Homebrew: https://github.com/apple/swift-package-manager/graphs/contributors https://github.com/apple/swift-package-manager/graphs/contri...

ihuman 11y ago
Thanks for the link. The repos weren't up when I made my comment.
smikhanov 11y ago
It looks like he managed to go through a whiteboard coding exercise in the end! As far as I know, Apple follows roughly the same hiring practices as Google. Well done (no sarcasm here, it's probably great to work at Apple)!
throwaway6497 11y ago
The same guy who wasn't offered a job at Google because he didn't do well in the interview (or was it code in the interview?)
- jkyle 11y ago
  Google doesn't provide feedback on why they reject you. For example, you could be the world's foremost expert on Erlang. But the department interviewing you needs a C++ programmer. You'd never know that was the reason. You'd just be notified that you weren't called back for another interview and asked to please check back for more positions in a few months.
  - deleted 11y ago
    [deleted]
  - rgovind 11y ago
    Actually, you can extract some info from the recruiters. Just ask them, tell them you need it to prepare better next time, tell them you know the reason but want to cross check etc. They will tell you
  - thaumasiotes 11y ago
    I was just rejected by Google. They will give feedback -- in my case, the recruiter said that they were worried I didn't seem to care whether my code would actually work as written. They recruited me through the code jam, but hey.
akramhussein 11y ago
Interesting to also see Mattt Thompson helped out.
- cmyr 11y ago
  Yea that's great; he's has a clear understanding of what it means to write and maintain a third party package[1] and he's also exceptionally good at writing documentation and code samples[2]. 1: https://github.com/Alamofire/Alamofire https://github.com/Alamofire/Alamofire 2: http://nshipster.com http://nshipster.com

ihuman 11y ago

Thanks for the link. The repos weren't up when I made my comment.

smikhanov 11y ago

It looks like he managed to go through a whiteboard coding exercise in the end! As far as I know, Apple follows roughly the same hiring practices as Google. Well done (no sarcasm here, it's probably great to work at Apple)!

throwaway6497 11y ago

The same guy who wasn't offered a job at Google because he didn't do well in the interview (or was it code in the interview?)

jkyle 11y ago
Google doesn't provide feedback on why they reject you. For example, you could be the world's foremost expert on Erlang. But the department interviewing you needs a C++ programmer. You'd never know that was the reason. You'd just be notified that you weren't called back for another interview and asked to please check back for more positions in a few months.
- deleted 11y ago
  [deleted]
- rgovind 11y ago
  Actually, you can extract some info from the recruiters. Just ask them, tell them you need it to prepare better next time, tell them you know the reason but want to cross check etc. They will tell you
- thaumasiotes 11y ago
  I was just rejected by Google. They will give feedback -- in my case, the recruiter said that they were worried I didn't seem to care whether my code would actually work as written. They recruited me through the code jam, but hey.

akramhussein 11y ago

Interesting to also see Mattt Thompson helped out.

cmyr 11y ago
Yea that's great; he's has a clear understanding of what it means to write and maintain a third party package[1] and he's also exceptionally good at writing documentation and code samples[2]. 1: https://github.com/Alamofire/Alamofire https://github.com/Alamofire/Alamofire 2: http://nshipster.com http://nshipster.com