From: Yaron Minsky <yminsky@janestcapital.com>
To: caml-list@inria.fr
Subject: Re: Job Announcement
Date: Thu, 08 Jun 2006 16:16:58 -0400 [thread overview]
Message-ID: <1149797818.32046.82.camel@quant9.janestcapital.quant> (raw)
In-Reply-To: <1149719748.32046.73.camel@quant9.janestcapital.quant>
A quick note: my email was down earlier today, but is back up now, in
case anyone was trying to reach me.
Yaron
On Wed, 2006-06-07 at 18:35 -0400, Yaron Minsky wrote:
> I'm pleased to announce that Jane Street Capital is yet again actively
> looking to hire some top-notch functional programmers.
>
> Jane Street Capital (http://janestcapital.com) is a proprietary
> trading company located in Manhattan, and we're looking to hire
> developers interested in working on trading systems and
> infrastructure, all built in OCaml.
>
> Jane Street is an open and informal environment (you can wear shorts
> and a t-shirt to the office), and the work is technically challenging
> and wide-ranging. Pay is competitive, and we're a reasonably small
> company (around 100 employees), so advancement is pretty quick for
> someone who performs well.
>
> Here's what we're looking for (in no particular order):
>
> - Strong programming skills. Pretty much all of our programming is
> in OCaml, so being a solid Caml hacker is a big plus. Extra points
> for deep knowledge of OCaml internals and experience wrapping
> thorny libraries. But we're also interested in great programmers
> who we are convinced will be able to pick up OCaml quickly, so
> anyone with a high-level of proficiency with functional languages
> would be a good match.
>
> - A commitment to the practical. Our work is tightly integrated with
> our trading operation, and we work very hard to keep our work
> relevant. One of the big attractions of the job is the opportunity
> to apply serious ideas to real-world problems.
>
> - Great communication skills. We need people who can explain things
> clearly and cogently.
>
> - Strong mathematical and analytic skills. We want people who can
> solve difficult technical problems, and think clearly and
> mathematically about all sorts of problems.
>
> - Strong Unix/Linux skills --- We're looking for someone who knows
> their way around the standard Unix tools, can write makefiles,
> shell scripts, etc. We're also very interested in people with
> serious systems administration and architecture experience.
>
> If you're interested (or have any students you think might be a good
> match) and would be willing to relocate to New York, please send a
> cover-letter and resume to:
>
> yminsky@janestcapital.com
>
> And you can get more information about us here:
>
> http://www.janestcapital.com/ocaml.html
>
> Note for foreign applicants: it is never too early to apply! The
> quote for this year for H1-B visas is already filled, so the earliest
> possible hiring date is October 2007.
>
>
--
Yaron Minsky <yminsky@janestcapital.com>
next prev parent reply other threads:[~2006-06-08 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 22:35 Yaron Minsky
2006-06-08 20:16 ` Yaron Minsky [this message]
2006-12-22 18:52 Yaron Minsky
2007-10-03 19:43 Yaron Minsky
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=1149797818.32046.82.camel@quant9.janestcapital.quant \
--to=yminsky@janestcapital.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