November 14, 2012

Now Hiring –> JavaScript / HTML5 Engineer

by with 4 comments

We’re looking for an excited JavaScript hacker to join us and help us
advance state-of-the-art technology implementation in
JavaScript. We’re looking to do some Cool New Things on the web that
have been traditionally limited to our desktop client, and need
someone who can help us push that along.

Do you enjoy trying to push the bounds of browser-boxed computing?
Have you experience with cryptography? Enjoy getting that last little
bit of performance out of V8 as Chrome makes your computer levitate
with the cooling fans spinning up? We want you! You’ll be working with
our existing team of web engineers to bring out new technology and
products allowing people to use SpiderOak in a private fashion no
matter where they are or what kind of device they are on. You’ll be
working on HTML5 webapps with more and more JavaScript getting pushed
further and further beyond the competition.

To hop on board and immediately get rolling, we expect that you
have a grasp of or can very rapidly come up to speed on a wide variety
of technologies around HTML5, including but not limited to:

You’ll have to be comfortable dealing with SQL for data, as well as a
Unix platform for deployment (Ubuntu, specifically). We have an
emphasis on test-driven development that you will be jumping in
to. Finally, our backend software is all in Python, and knowing that
is a major plus but not immediately necessary- if you already know
the above, chances are you can learn a new language if it comes to

If you want to join in on our merry adventure, you will need a
functional grasp of English (don’t worry, we have several staff
on-board already for whom it’s a second or third language). You will
also be expected to occasionally travel (at company expense) to have
some quality face-to-face time. Important cities in the SpiderOakVerse
are San Francisco, CA, Kansas City, MO, and Chicago, IL (for
reference, these three cities make up about half of SpiderOak). A
sense of humor is always appreciated and welcome.

Still interested? Send an email to including “web engineer” in
the subject with a little about yourself and your experience to date
(a ‘cover letter’ if you will). NOTE: Resumes are not required as who
you are is more important than what your resume may or may not say. If
we enjoy your thoughts and feel like you will be a good fit, we will
send you a small task to complete. Please do be sure to tell us a bit
about yourself, what you can do, and why you’d like to work for
us. English only, please.

We know there’s talent in everyone regardless of what little papers
might say, so we have no “minimum” requirements for degrees. We’re
also super-equal-opportunity: quality hacking knows no bounds for
race, gender, nationality, sexual orientation, species[1], or
religion. If you can meet what we need, we’ll do amazing things
together, no matter who, what, or where you are.


1: The Management would prefer llamas with experience in piloting
luxury yachts.

  1. Glad you guys are adding to your team.
    Some stuff I think you should also address in here, for us js dev's who would be more interested if you were a little more specific about certain things imo:

    workplace: Is this a work from home position or do you have to move to the above mentioned cities.

    libs: jQuery, Backbone, and handlebars are nice, sure. But are you stuck with those? What is the dev environment like, do you push a standard or is this a best tool for the job based on research kind of thing.
    I've found it's Really important to find that out right away. I'm a best tool for the job kind of guy. While I certainly think backbone has a place. It's definitely not the right tool for every job. I just finished writing some extensions to make backbone more like angular for a current contract because the client insists on using backbone as that is their rigid standard.
    So it's good to know whether or not developers are allowed to make the right decisions on their projects.

    management structure: what kind of management structure are we looking at?

    furthering education: how much time do employees get for r&d, how much of a budget do we have to get things like books, and to attend conferences?

    hours: what are the hours Really like? c'mon be honest, no b.s. like, 40 hours strict, you never have overtime. Because only newb's fall for that one ;).

    meetings: how often do we have meetings, how long are they. Do you have meetings to schedule meetings?

    workflow: agile? get it done? waterfall? freedom to choose? which do you prefer, because that's important. I personally just like to get the job done, an opt in system is the best imo, but it's good to know this going in.

    communication: whats your company structure look like, is it flat, or do your employees have to wait to make decisions as its passed up and down the chain?

    developers: you have them, how important are they to your company. some devs are a dime a dozen, some are incredibly hard to find. whats your real balance?

    management: who makes the final decision on projects, is it a highly skilled programmer, or is it the group who is working on the project arriving at consensus.

    lastly, why don't you have your developers write the job descriptions ;) it would save time, get you better applicants, and actually be an informative hiring post (rare to find). I get stuff like this all day.
    I use SpiderOak and recommend it to everyone I know, you did a ton of things right. Thanks for making such a sweet product.

  2. Everyone at SpiderOak is telecommute, work from anywhere, on your own schedule.

    It's definitely a "right tool for the job" sort of place most of the time. We've made a few things the convention, but make other choices as appropriate to a situation.

    Management: Mostly flat. Loose teams around projects. Less than 30 people total so we try to keep things informal. Very rarely are we blocking on management decisions.

    Hours: Actually we don't track hours at all, since it's all telecommute and we don't pay by the hour. So I have no idea how many hours SpiderOak people work. I probably work about 5 and 1/2 days a week, but I'm a founder.

    Workflow: None of the agile/scrum techniques seem to apply to telecommute companies and we've developed our own style over time. Probably the best way to describe it is to say that SpiderOak development happens much like a typical open source project.

    Developers: SpiderOak is very much a developers company, since it was created by developers. Usually teams make most of their own decisions, usually with some peer review. Occasionally I get involved and set specific directives, but overall SpiderOak is very much a place for self directed people.

    And just FYI, Matt (who wrote this post) is indeed a developer.. He just his own approach to writing.. :)