- EphBlog - http://ephblog.com -


Ace Eph hacker Travis Vachon ’06 writes with job openings at WeatherBill. Any senior CS major thinking of a career in programming should contact him (even though you probably don’t have all the prerequisites).

Alas, it looks like the Google group for Ephs in Technology is completely dormant. Any online group without regular new content is doomed to fail. Still sad to see that EphTown closed up, although some pages live on. (Previous discussion here.) Many Eph hackers read EphBlog, so perhaps the job posting will be of use.

For current students, my advice is to take CS 134 and 136 even if you don’t want to be a programmer when you graduate. The world is filled with growing companies like WeatherBill. Even if you don’t want to write code for them, they are much more likely too hire you if you are interested in and knowledgeable about the heart of their business.

We’re looking for engineers with solid backgrounds in finance
applications, along with sales/bus dev/general risk management folks.
If you happen to know anyone (Ephs in particular :) ) that might be a
good fit I’d be much obliged if you could forward this along. I’ve
attached the job description for the financial engineering position
below, and we have a careers page with more descriptions of open
positions here.

Software Engineer – Risk Management Systems

WeatherBill, as featured in the Economist, Wall Street Journal,
Financial Times & Newsweek (see articles below) is a fast-growing
A-list funded early-stage startup founded by ex-Google execs. We are
looking for a superstar Software Engineer with experience developing
financial software to join the team building our groundbreaking online
financial products and services for managing weather-risk. Candidates
will use their strong engineering/analytical skills and personal drive
to further innovate and maintain leadership in our new and
fast-growing industry.

Your Qualifications:

* Ambitious, driven and talented with the desire to work on
challenging and potentially world-changing problems
* Team player who feels at home in an open and flat-structured
environment, and takes pride in a job well done
* At least five years of experience developing with Java or C++
(at least two years of recent Java)
* Strong knowledge of Internet Technologies, Java server and
backend/database development
* Strong all-round engineer who writes well-structured, easily
maintainable, well-documented code
* Experience building risk management and portfolio analysis tools
* Comfortable with quantitative finance
* Experience designing and developing large scale, fault-tolerant
and high performance distributed applications preferred
* Proficient in a Unix/Linux environment
* BA/BS in Computer Science or related technical field from good
university with high GPA; Masters/PhD preferred

What You’d Do:

* Architect, build and support tools to manage WeatherBill portfolio risk
* Develop and expand infrastructure to process high volume
financial transactions and run fault-tolerant compute-intensive
mathematics applications
* Tackle a wide variety of engineering problems as needed – we are
a small team and we all share roles
* Brainstorm with the team and prototype new concepts and ideas rapidly

What We Offer:

* A driven, motivated, and talented team that believes in working
hard and playing hard
* Energetic, idea-driven and transparent work environment
* Exciting world-changing opportunity – we are striving to do
something very big about something that affects everyone
* Award-winning South of Market office across the street from South Park
* Competitive salary and great benefits

Comments Disabled (Open | Close)

Comments Disabled To "WeatherBill"

#1 Comment By Jonathan ’05 On October 9, 2008 @ 3:01 pm

Another reason to take 134 and 136 is it’s damn fun, if you have the right kind of mind, a tinkering mind. Writing code is just like shop class (which has been cut out of curriculum most places, right?) Outside of studio art and some theatre, there aren’t many chances to build something useful in Williams classes (and we could debate is art if “useful”). I took 134 and 136 my senior year, far too late to really improve my marketability, but in plenty of time to have a ball with those lab exercises.

And, actually, it turns out I have had to use programming code to make parts of a survey I am doing for my thesis research; just shows you never know when your forays into random subjects will pay off.