Curriculum Vitae

In January 2009, I started working for IMC in Amsterdam, a marketmaker on exchanges worldwide, where I am a member of the Trading Solutions team. Trading Solutions is responsible for the infrastructure used by our traders on the different exchanges (Euronext, London Stock Exchange, Deutsche Börse, etc), including the UNIX and Windows machines, network connections and hardware and auxiliary equipment. My work is focused on the UNIX machines running our own proprietary and third party trading software.

I am currently working on the following projects :

• Improve monitoring of trading machines
• Improve systems management and maintenance environment
• Implement PTP to keep our machines in sync
• Migration of machines to a new datacenter

I have been a volunteer in the networking committee of Coloclue, a non-profit and UNIX-only colocation provider setup as a voluntary association for "clueful" individuals, since November 2006. The networking committee is responsible for the wellbeing of the Coloclue network, currently spread out over 4 different locations with Juniper routers (J2320's), HP ProCurve 2626 switches, Cisco and Livingston Portmaster serial console servers and Ingrasys iPoMan remote power switches.

Other responsibilities of the networking committee include handling IP address allocations for expanding and new users (including setting up RIPE objects for the allocated space), troubleshooting network issues, taking care of the UNIX machines running services for Coloclue and helping our members when they report problems using the Coloclue network.

Some of the projects I have worked on for Coloclue are :

• Setup IPv6 numbering plan
• Migrate our members from 2 /24's of PI space to a /21 PA space
• Migrate to our own /32 IPv6 space
• Set up reverse DNS for our IPv6 space
• Renumbering of UNIX user accounts of our members for easier maintainability

From May 2006 to May 2008, I have worked for Google, the global search engine, at the European engineering headquarters in Zurich, Switzerland. I was part of the Site Reliability Engineering (SRE) team whose responsibility it is to keep the different Google properties (both internal and external) available to our users.

As one of the first SREs in Zurich, I started with a 3 month training period in the USA (in Mountain View, CA and New York) where it was decided that I would be working on Google Maps. This meant working with the Maps developers to take over their production responsibilities. Our team rapidly grew from just me to four engineers and we have since been handling most of the changes in the production environment for Maps. The team is responisble for :

• Upgrading to new binary versions
• Changing production configuration (launching new features)
• Updating live indexes to newer versions (eg. for new country launches)
• Capacity planning and management (loadtesting, acquiring extra resources, moving services to new datacenters, etc.)
• Monitoring our services 24/7 and responding within tight SLAs (on-call)

In the two years that I have been working on Maps, we have changed several key infrastructure components of our architecture, while increasing traffic levels, reliability and performance to our product website. We have also gone through several upgrades of the underlying internal Google infrastructure as the company continues to strive for better utilization and managebility. In addition to the primary work on the publicly visible Google Maps website, Maps SREs are also responsible for supporting internal customers using our geocoding software, and for certain (geo-related) parts of regular websearch.

Finally, an important task for all Google engineers is interviewing candidates to expand our team. In two years I have done over 100 interviews, both on-site and over telephone. Focusing mainly on technical knowledge and expertise of the candidates, we try to establish if they are a good technical match for the position and if their personality would fit in our team.

From September 2004 to April 2006 I was employed at BIT, a business ISP in Ede, where I worked in a team of about ten engineers to keep the entire network including all its servers, routers and other equipment up and running.

At BIT, my work included managing Linux and BSD servers running a variety of internet services for ourselves and our customers, managing (mostly Cisco) CPE routers that terminate BIT DSL and other leased lines, configuring our Juniper routers and Extreme switches for high-bandwidth customers or for new BGP peers. My tasks were mainly focused on UNIX and the network level, but as a team we all helped think about solutions, including those for Windows-based environments.

I've worked on the following projects :

• Design and implementation of a UMTS firewall
• Implementing webmail and IMAP services for our customers
• Migrating NFS services for our mail platform from a NetAPP 720 to a NetAPP 840

For the Internet Opleidingen Centrum, a sistercompany of BIT, I taught a few courses on TCP/IP. For one of these courses I helped authoring the course material.

In October 2003 I began working at the internet hosting part of Versatel. In a team with five colleagues we kept the colo-network running. This involved a shared hosting platform for a large number of websites, colocation services, dedicated servers etc. Four of us, including myself, managed the UNIX machines, running Red Hat, Debian and FreeBSD.

My main responsibility was the mail platform, based primarily on FreeBSD servers running DJB's qmail software. We ran two relay servers for Versatel customers, a cluster to accept mail for approximately 80.000 users and provided backup MX services.

Other projects I worked on during my time at Versatel are :

• A redundant DHCP/DNS server for an ADSL provider
• Building a web based speed test for Versatel DSL customers
• Adding virus scanning to the mail platform

When I left ICT, a friend asked me if I could do some project-based UNIX system administration work at his company in Amsterdam. I joined prima, my fathers bureau for project and interim management, via which I then did some project work.

Unfortunately, we found it hard to keep me busy with other projects, so after six months we decided to stop this venture.

After X-Tern got taken over by ICT, I was asked for Unix- and Network administration of the entire ICT network (spanning 6 locations in The Netherlands). This involved system management for various Unix machines involved in ICT projects and the maintenance of the routers and Linux systems for the network connectivity between sites and to the internet.

At ICT I've worked with IBM AIX 4.1.3, HP-UX 11.0 and 10.20, Solaris 8 and 7, OpenBSD 3.x, Slackware 8.1 and 8.0, Red Hat 7.2 and other versions of UNIX. The hardware used ranged from a Bull Escala to HP J6000's and from Sun E250's to Dell PC's

An important project during my time at ICT was the deployment of the internet-related servers in a DMZ. Focusing mainly on security and maintainability I built a default server which could be employed for various tasks (firewall, webproxy, smtp, webserver etc.)

For X-Tern I provided first and second line support for both X-Tern and its customers, helped set up a new network including remote management connections to customers and was system administrator for Novell, Windows NT, HP-UX and IBM-AIX servers.

At Joosten Products I was responsible for a project which involved a full-scale inventory of hard- and software and a recommendation for internet and e-mail connectivity. In a second stage, I helped implement these recommendations.

Project in which I was part of the Information Centre of the Service Unit General. My tasks involved troubleshooting user problems, installing hard- and software and creating Novell accounts for new colleagues.