Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Owen Gunden <ogunden@janestreet.com>
To: caml-list@inria.fr
Subject: Sysadmin/programmer combo positions at Jane Street
Date: Thu, 27 May 2010 14:23:27 -0400	[thread overview]
Message-ID: <20100527182327.GA3097@nyc-qws-038.delacy.com> (raw)

In addition to the more conventional development positions described in
Yaron Minsky's recent email, we are hiring people with skills at both
functional programming and systems administration.

Most of our systems automation software is either written in ocaml or
will be sooner or later.

-----

Sysadmin/Programmer combo
(aka Systems Automation Specialist)

Seeking:

Responsible, careful, passionate and skillful technology specialists to help
build and maintain our increasingly automated technology infrastructure.

You'll need to be adept with unix (specifically linux) administration. For
example, you want to be able to format filesystems, install bootloaders, and
make rpm packages. It's even better if you understand system calls, kernel
parameters, IO schedulers, and other lower level internals.

You'll also need to be a good programmer. We only want people who've had
experience writing significant amounts of real-world code. OCaml is our
language of choice, but it's okay if you don't know it so long as you can learn
it. Experience in ruby, python, php, perl, scheme, haskell, erlang, and others
are all acceptable.

About us:

Jane Street is a proprietary trading firm with offices in NYC, London
and Hong Kong (respond to this ad if you're interested in any of the
above). We have about 200 employees total, the majority of whom work in
NYC. While this makes us a medium-sized business, the culture
more closely resembles that of a small startup: The atmosphere is casual and
informal; we care about doing good work more than dress codes or hours put in;
there's not much room for office politics; and, there's a lot of financial
upside if you do great work.

We have a large datacenter on-site and several colocation facilities, with
hundreds of servers total. We manage all of this with just a small team by
leveraging our programming skills to create scalable, automated systems. We use
a lot of open source tools and write the rest ourselves.

Our systems team is tightly integrated with the rest of the company so you get
exposure to a broad range of concepts and ideas. Unlike at other large
financial firms, our technology group is highly regarded and central to our
business, not just a footnote.

Perks:

In addition to our excellent benefits which you can read about here:

  http://www.janestreet.com/workplace/benefits.php

we have on-site classes taught by employees on subjects ranging from
programming to finance to trading to bridge (yes, the game).


If this sounds like a match to your background, skills, and disposition, let us
know. Send a cover letter indicating why you think you're a good fit, along
with your resume, to ogunden@janestreet.com.


             reply	other threads:[~2010-05-27 18:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 18:23 Owen Gunden [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-24 13:55 Owen Gunden

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100527182327.GA3097@nyc-qws-038.delacy.com \
    --to=ogunden@janestreet.com \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox