Skip to content

Instantly share code, notes, and snippets.

@julesfern
Created April 28, 2009 11:36
Show Gist options
  • Save julesfern/103088 to your computer and use it in GitHub Desktop.
Save julesfern/103088 to your computer and use it in GitHub Desktop.

Good news everyone!

We at Videojuicer are currently working on our next-generation API product, and we have a vacancy for a Ruby application developer to join our small team.

Our product is an API-led platform for generating leads from online video. It's designed to work in any situation where you have a video, and want it to drive traffic back to your product. That means it's good for screencasts, movie trailers, music videos, product commercials - you name it.

Our environment is a distributed team in the UK, US and Canada. We communicate mainly with Skype. Your working hours will be flexible, and you'll be able to work from your home, our London office or from a Brighton coworking venue if you so choose.

We work with Merb/Rails/Rack, DataMapper, Flex, Git, and jQuery. We use a series of futuristic moon-standards including HTML5, OAuth, OEmbed and SMIL3.

You, our ideal candidate, will:

  • Be able to conceive, wireframe, build, test and integrate new features
  • Have a strong eye for user experience
  • Write beautiful, readable, properly-factored Ruby
  • Write elegant, semantically-accurate cross-browser markup
  • Write comprehensive tests for your code
  • Be able to quickly and easily pick up new tools, libraries and techniques
  • Be able to work to milestone deadlines
  • Enjoy working independently and in pairs/groups
  • Be based in London or Brighton (we're flexible on this for the right candidate)
  • Have demonstrated your caring, sharing side by contributing to or creating open source code

To apply: Send your CV and a covering letter to dan+jobs@videojuicer.com with the phrase 'Ruby Developer' in the subject line. It is absolutely okay to write to us with questions before applying formally. Please no agencies.

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