369 karma · joined October 27, 2010
Audiomack (http://www.audiomack.com) is a fast-growing music sharing and discovery website. We are looking for a generalist engineer to work with us in a contracting role on a full-time (or nearly FT) basis. You would be welcome to work out of our SoHo NYC office, remotely, or some combination. We are looking for candidates who can contribute immediately to both backend and frontend projects.
Between destkop & mobile sites, embeds on other sites, plus iOS and Android apps we generally have 5-20k simultaneous users, 2-3 million streams per day, resulting in 30+ TB daily bandwidth use. We are looking for someone who is passionate about designing and implementing efficient systems that millions of users will interact with daily.
Skills & Requirements:
- excellent coding skills and proven track record of delivering value
- several years of experience with full-stack web development: backend, frontend, database
- (if working remotely) proven telecommuting skills: self-motivated, highly productive, maintains open lines of communication with the team
- able to make sense of existing code and seamlessly integrate new features without breaking current functionality
- good coding habits: writing tests, matching existing coding style, intelligent decision-making on when to refactor, etc.
Key Technologies:
- PHP / Zend Framework
- Redis / Redis Cluster
- The usual frontend technologies (HTML5, CSS3, JavaScript + common libraries, AJAX)
- AWS (EC2, CloudFront, S3, etc)
- Git / Github
Bonus for candidates with experience in:
- music fingerprinting
- extensive HTML5 audio/video development
- soundmanager2 or some other audio API/framework
- redis clusters
- sysadmin-related tasks
If interested, please contact us: management at audiomack.
Such a tease. What cool features did you come across?
For example, if your job is cranking out CRUD apps or "online brochure" websites for various clients and you do it for 5 years, there's a good chance that while you're very good at those things now, it hasn't really gained you the same experience as if you'd been doing something a bit more demanding.
3 year heavy EC2 reservations pay for themselves in ~7 months, cloudfront reserved bandwidth is just a 12 month agreement so that costs nothing up front. You might want to experiment with some different instance types though, depending on your resource utilization. Personally I really like using the new c3.large instances for my web servers and anything else that needs more CPU than memory, proportionately. If the standard instances suit your needs better you still might want to move to the m3 class.
Aside from those two items it looks like you are sending out a considerable amount of stuff from EC2->internet (27 TB transfer out from US-East to internet). I'd recommend looking at whether you could set up a cloudfront distribution with your EC2 servers as its origin.
sorry, I don't buy any apologizing for comcast/verizon failing to deliver HD video from netflix/youtube yet somehow able to do it under the same network conditions (same time) just this time through an encrypted VPN. if it was an isolated report... maybe. this is far too widespread to be anything but intentional.
If you use a lot of cloudfront bandwidth without setting up a reservation, yeah... you're gonna pay through the nose.
I wrote most of the code for Audiomack. Free music hosting for artists. Predominantly hip-hop/rap because my cofounders have had other ventures aimed at that genre over the past decade or so, but audiomack accepts everyone. We'd particularly like to make inroads into electronic & dance music.
Started it in our spare time, launched Feb '12 and I went full-time in May '13.
edit: interview with my cofounders for anyone interested in the ideas behind audiomack http://www.youtube.com/watch?v=6S1Vb0PE7w4
I think Solr and Sphinx pretty much tick the same boxes in terms of features and performance though, so use what you know and like.
Built it in our spare time early last year, went live around the end of Feb 2012. Been growing like a weed ever since, and this year it's just been too much work to keep making progress on AudioMack in addition to having a full-time job.
Never really plugged it on HN because it didn't seem like quite the right crowd and I feel awkward about shameless self-promotion. :)