Skip to content

Instantly share code, notes, and snippets.

Created Nov 19, 2012
What would you like to do?


What we're doing

We're Aframe. We're a company developing a new workflow for people producing video content. We're considered disruptive.

We've been going for a few years now. We still consider ourselves a startup but we have real paying customers using the system including the (elided for this posting. I think marketing gave me a hard time about this list and I can't remember which ones I'm allowed to include). Our system runs on our own hardware, operating out of three data centers spread across London, New York and LA, each with their own large file storage. Our London storage (which has been running the longest so is the largest) has about two and a half million files in it, some of which are approaching about 500GB for a single file.

Right now we're supporting two tracks of work: We've got a long term road map with important feature development to come but we also have to support the existing system and make it more robust and fully featured for our current and incoming customers. We have a highly competent development team, but it's small enough that we simply can't keep up with supporting both tracks without more people on board.

Conveniently, we've recently raised a round of funding (£7M) and are ready to start using it to expand the team. That's where you come in.

What we want from you

  • Responsible development. We're very much out of the greenfield stage. There's more than enough new feature development to go around, but the emphasis is on doing it sustainably.
  • Willingness to get stuck in at any part in the software stack. We'll mostly want you on backend work, but would prefer it if you weren't one of those people who said "Oh no, that's Javascript, I don't understand that" if the problem strays into the front-end. Or anywhere else out of your comfort zone really.
  • Getting actively involved in design and architecture discussions
  • Refactoring skills. Our codebase is far from perfect (whose isn't?) but it's improved dramatically in the last year and we want to be able to say the same thing in a year's time. We'll need your help on that.
  • Problem solving and debugging. Bugs happen. You'll be one of the people fixing them when they do.

What our stack looks like

Here's a random sampling of some of the interesting moving parts in our stack, in no particular order:

That we run ourselves:

  • Ruby without Rails. We're running Padrino and DataMapper
  • PostgreSQL
  • Beanstalk
  • ffmpeg
  • A variety of other tools for working with media (e.g. mediainfo, mxflib, sox, ffmbc, handbrake)
  • A UDP based file transfer mechanism for accelerating transfer over high latency connections
  • A distributed file system

External services we use:

  • Pusher
  • Recurly
  • Sendgrid
  • Various analytics software

Familiarity with any or all of these is preferred but not required. You're probably going to have to get familiar with most of them though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment