caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yaron Minsky <yminsky@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] [JOB] OCaml Developer at Jane Street
Date: Tue, 25 Oct 2011 18:29:21 -0400	[thread overview]
Message-ID: <CADKNfhJKcSGENkAP2_CpyEm=G1M=+msP7kBZ7PS8578nZv=CWw@mail.gmail.com> (raw)
In-Reply-To: <20111025222529.GW30146@janestreet.com>

[-- Attachment #1: Type: text/plain, Size: 2383 bytes --]

Whoops.  The link to the post on Async was busted, but it is now fixed.

On Tue, Oct 25, 2011 at 6:25 PM, Yaron Minsky <yminsky@janestreet.com>wrote:

> Jane Street is looking to hire functional programmers for our offices
> in New York, London and Hong Kong.  We're looking for both interns for
> this upcoming summer as well as full-time hires.
>
> Jane Street has the largest team of OCaml developers in any industrial
> setting, and probably the world's largest OCaml codebase. We use OCaml
> for running our entire business, supporting everything from
> statistical research to systems administration to automated trading
> systems.  If you're interested in using OCaml to solve real-world
> problems, there's no better place.
>
> Jane Street has (in my humble opinion) a great work environment.  It
> has a very informal feel --- if you dress much nicer than a t-shirt in
> jeans, you'll look out of place --- but it's also an intellectually
> challenging place where you get to wrestle with hard problems and
> learn about the subject matter of trading, a fascinating field in its
> own right.  There's also a strong focus on education, with both on the
> job training and a system of formal classes.
>
> We also have a strong commitment to OCaml and to open-source software.
> We released our Core suite of libraries a few years back, and we
> continue to extend the reach of our public releases.  And we have and
> will continue to financially support projects to improve the OCaml
> ecosystem.
>
> Compensation is more than competitive, and no prior experience with
> finance is required.
>
> Here are some resources you can use to learn more about Jane Street
> and what we do.
>
> - A talk I gave at CMU about how and why we use OCaml
>  <http://ocaml.janestreet.com/?q=node/61>
> - Our technical blog: <http://ocaml.janestreet.com>
>
> If you want to get a flavor of our approach to software, you might be
> interested in looking at Async, a monadic concurrency library we just
> released:
>
>  http://ocaml.janestreet.com/?q=node/100
>
> Follow this link to apply:
>
>  http://janestreet.com/apply
>
> y
>
>
>
> --
> Yaron Minsky
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>

[-- Attachment #2: Type: text/html, Size: 3382 bytes --]

      reply	other threads:[~2011-10-25 22:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25 22:25 Yaron Minsky
2011-10-25 22:29 ` Yaron Minsky [this message]

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='CADKNfhJKcSGENkAP2_CpyEm=G1M=+msP7kBZ7PS8578nZv=CWw@mail.gmail.com' \
    --to=yminsky@gmail.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;
as well as URLs for NNTP newsgroup(s).