Hacker Newsnew | past | comments | ask | show | jobs | submit | brucify_'s commentslogin

Software Engineer - iTunes Store QA

Santa Clara Valley, California, United States Posted: Jul. 17, 2015

Job Summary

Write applications and frameworks that cross a variety of domains: user interface, backend services, realtime data visualization, etc…. A 40 hour work week is standard, but during those hours we push to design and write inventive code. Our work is constantly changing to meet new demands, but a list of our recent projects includes:

- Language agnostic harness for parallelizing execution of jobs across a cluster of hosts. - Communication protocol for developing system-sized applications. - Real time collection, storage and visualization of large datasets. - Rich, pageless, web applications. - Mock clients for a variety of systems. - Multiple iOS and OS X applications. - 3d user interfaces.

Description

We're offering the opportunity to work on a group that is focused on programming. Our team believes in the value of thinking about the software we write, improving the tools we use, and reflecting on the ideas behind it all. We spend little time dealing with non-engineering issues, and implement solutions with a freedom to choose technologies best suited for the task. Throughout the year our engineers also get the opportunity to explore new ideas that they believe could be interesting and of benefit. We work in a variety of languages and hire qualified candidates regardless of their language background. These are the languages we currently use, or that influence our thinking:

Clojure Erlang Java JavaScript Objective-C Python Smalltalk Self

And these are people who've inspired us: Alan Kay Rich Hickey Bret Victor

Education

BSCS or equivalent work experience is required.


For the first time Erlang 18 shipped under Apache License 2.0, it will likely have a meaning for Erlang's future development. The Industrial Erlang User Group has spent quite some effort on that.


Can you explain why, or link to a summary of the history? Wasn't it a license specific to erlang in the past? If so that's great as Apache is standard. But if it went from another common license I'm curious to know why.


It didn't come from another common license. It came from the EPL (Erlang Public License http://www.erlang.org/EPLICENSE). Erlang users have been asking for the change for years and OTP 18 finally delivered on the promise.


The previous versions of Erlang were using the Erlang Public License 1.1, a modified Mozilla Public License adapted with Swedish laws. https://en.wikipedia.org/wiki/Erlang_Public_License


Akka was actually inspired by Erlang's design principles, the philosophy "Let it crash", and the actor model.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: