SUMMARY:

• Over 15 years in high end computer systems, focused on investment Banking, government and internet.
• Team leader experience
• Strong troubleshooting / problem solving skills.
• Strong knowledge of TCP/IP protocols
• Currently focused on virtualization
• Managing the Internet. No Kidding.
• Getting inside stuff, I just have to know how things work.

SYSTEMS AND SOFTWARE:

• SunOS, Solaris, BSD, Linux, SCO Unix, Interactive Unix, some AIX and HP/UX.
• Egenera, XEN hypervisor, PAN manager, VMware ESX and GSX., QEMU
• C systems programming, Perl, and shell programming
• Exposure to C++, java, and other OOP methods
• Veritas Netbackup, Veritas filesystem (VxFS), Veritas volume manager, ODS
• IPv6, SSL, public key cryptography, web services, sendmail, NAT,SSH, rsync
• Tcp wrappers, TIS toolkit, firewall technology, tcl/tk, python
• Apache and i - planet webservers, directory services (LDAP)
• Exposure to Tomcat, and Weblogic.
• TCP/IP and PPP/SLIP networking, including LAN/WAN and campus solutions
• Very strong DNS, XNTP, NFS, NIS experience
• All aspects of 802.3 networking, from MAC layer to application layer

PROFESSIONAL EXPERIENCE:

Confidential, Sterling, VA

Responsibilities:

• I was able to build, commission, and maintain 6, 32 core ESX hypervisors.
• Once built, provisioning a new server moved from a 10 day project to less than a day.
• Although real day to day technical challenges were sadly rare, the satisfaction of tidying things up was my reward.

Confidential, Dulles, VA

Responsibilities:

• Managing the .com, .net and various other Confidential nameservers.
• These servers were placed in key infrastructure points around the world, so travel was a requirement.
• The internet 'A' root servers required very special treatment.

Confidential, Gaithersburg, MD

Linux/Solaris/HP-UX systems Engineer

Responsibilities:

• 3rd line role involving troubleshooting, initial build, maintenance and assisting operations. A typical engineering or 3rd line role.
• We were expected to fix anything which the 1st and second line couldn’t.
• The most enjoyable aspect was being able to develop and train the junior system administrators.

Confidential

Commissioning Engineer

Responsibilities:

• Architect and commission 8, 16 way Confidential to act as preprocessors to the core derivitives trading systems, which were comprised of 4 fully populated E25k’s.
• This was a relatively simple project on the surface, but made very difficult by the fact that we were allowed no absolutely no downtime or testing against the core systems.
• It had to work first time.

Confidential

Responsibilities:

• Support both internal HP/UX billing systems and client owned servers. I specialized in performance tuning focusing on SAN and Gigabit networking. I became the firms technical troubleshooter. Even though the internal systems were mainly HP/UX, I still find this an awkward unix to deal with.
• The client owned hosts were mainly Linux and Solaris, and being client owned, varied enournmously in their requirements for build, maintenance and administration. These hosts were subject to penalty SLA’s

Confidential

Responsibilities:

• Various short term contracts to assist Large Sun clients, including a large DNS and firewall infrastructure for Vodaphone UK, and installs for British Telecom

Confidential

Global Engineer

Responsibilities:

• The firms highest troubleshooting team, expected to go anywhere in the world at short notice.
• Design, Implementation and testing of Solaris software to be deployed throughout the firm on a global basis. All aspects of deployment were fully automated, running flawlessly on over 3,500 hosts worldwide
• ‘Buck stops here’ problem resolution, from the network layer through to the application. I was responsible for fixing anything which the normal system administrators could not
• Patching and hand upgrades on a per host basis were eliminated, we developed a single system image capable of supporting all platforms, from sparc10 to Starfire
• All applications required by the firm were supported by one software image. No special engineering or exceptions were allowed, or required.
• Implement the security baseline standards in the core Solaris builds.

Team Leader

Confidential

Responsibilities:

• Responsible for a team of six system administrators running 220 live trading hosts. 30% of all stock trading on the London stock exchange originated on the hosts. Downtime was not an option
• Seamlessly moved these 220 hosts from one location to another, with no application downtime whatsoever
• Turned discrete location based teams into a global, fully integrated ‘follow the sun’ support team. This proved to be of great value to the firm as trading systems merged to form one continuous trading day

Confidential

Webmaster and Sr. System Administrator

Responsibilities:

• This Startup ISP quickly won the contract to host all of sites for the Confidential, and consequently required extreme security measures to defend against hackers and maintain uptime. I was able to secure these sites against sustained malicious attacks, and keep the government websites online

Confidential

Network Engineer / System Administrator

Responsibilities:

• Confidential group is Europe’s largest multimedia production house
• A pioneer in the field of digital video, EMG storage and network performance requirements some of the most extreme that I have ever encountered
• The network consisted of Silicon graphics servers, Unix, NT and NeXT hardware.
• Maintaining a dynamic infrastructure in a company doubling in size every 4 months

Confidential

Open Systems Consultant

Responsibilities:

• The birth of the open systems revolution brought about a new beginning in the industry, one which we were able to take advantage of.
• Designing and building system from scratch
• Focused on leading clients away from very expensive proprietary hardware and software, to open, highly integrated cost effective solutions
• Often able to replace all a firms hardware and software for less than the cost of the annual maintenance contract on proprietary systems
• TCP/IP and SQL were our core components

Confidential

Research Technician

Responsibilities:

• Assisting first and second year students during lab work.
• Produced the first year physical chemistry lab course, and built the lab from scratch
• Assisted in the design and build of magnet systems for CAT scanners
• Build specialist hardware from exotic materials to support the research team
• Conducted intricate enzyme extractions, and tested these enzymes in vivo