Peter Hill

Current

• Sr. Network Engineer at Amazon.com

Past

• Sr. Network Engineer at University of Washington
• Network Engineer at Amazon.com
• Network Engineer/Architect at Carnegie Mellon University

• Technology Coordinator at Central Catholic High School
• Manager at Dunnings
• Presenter at Carnegie Science Center
• Electronics Technician 2nd Class at United States Navy

see less...

4 more...

Education

• US Navy Nuclear Power School

Recommended

9 people have recommended Peter

Connections

431 connections

Industry

Computer Networking

Peter Hill’s Summary

I have had the pleasure of working with three different enterprise networks. The first major network at Carnegie Mellon where I had the pleasure of working closely with a small team of SDEs whose tools were able to provide a level of automation and self service that I have yet to see matched.

Amazon taught me all about scalability of systems. I learned first hand how to build a network of services with the ability to withstand large outages without end user knowledge. It was very energizing to work with such a great team of people. Everyone worked hard to solve the latest problem and deliver great products at an amazing pace.

I enjoy engaging with other teams and finding places we can create non-zero-sum opportunities. I like to take processes and systems and look at them from different points of view to see if they can be optimized. I enjoy working with people who also want to improve their knowledge and skills.

Peter Hill’s Specialties:

large networks, tcp/ip troubleshooting, scalable application infrastructure, team building, thinking outside the box

Peter Hill’s Experience

• Sr. Network Engineer

  Amazon.com

  (Public Company; 10,001 or more employees; AMZN; Internet industry)

  December 2007 — Present (2 years )

• Sr. Network Engineer

  University of Washington

  (Educational Institution; 10,001 or more employees; Higher Education industry)

  July 2006 — December 2007 (1 year 6 months)

  Our group of engineers are responsible for the main and branch campus networks, the UW Medical Center network, the state of Washington's K-20 (Junior College) backbone network, and the Pacific Northwest Gigapop. We operate a wide range of hardware and physical layer technologies. We use a mix of Juniper and Cisco routers. Different networks are using different IGPs, OSPF and ISIS. We are deploying MPLS in the Gigapop to create a unified multi-service network that will enable us to provide different services (Internet2, commodity, NLR) to different participants. We are almost done deploying our state wide DWDM ring that will permit us to quickly roll out new or improved services to our customers. We work closely with both the Architecture group and the NOC to bridge the gap between concept and supportable implementation.

• Network Engineer

  Amazon.com

  (Public Company; 5001-10,000 employees; AMZN; Retail industry)

  July 2004 — July 2006 (2 years 1 month)

  The Network Engineering group at Amazon kept the packets flowing through Amazon's global network. Our work required us to stay on the cutting edge of technology. We worked closely with vendor developers in order to manage the growth in network services. The Engineers at Amazon are all fantastic to work alongside.

• Network Engineer/Architect

  Carnegie Mellon University

  (Educational Institution; 5001-10,000 employees; Higher Education industry)

  April 2002 — July 2004 (2 years 4 months)

  Worked on the team that provided the highest level of support for the campus wired and wireless network.
  
  Helped design a forklift upgrade of the entire campus network.
  http://www.net.cmu.edu/docs/imp/imp-2004-01.pdf
  
  Gave a presentation on our efforts to manage our campus bandwidth usage through user participation in the process.
  http://www.net.cmu.edu/pres/jt0803/
  
  Created the greenfield network design for the CMU-Qatar network. This required many discussions with the system service owners so that we could attempt to create a platform that could operate independently of the Main campus, despite being thousands of miles away.
  
  Carnegie Mellon showed me the power of a small cross function team led by a focused manager to create elegant solutions quickly.

• Technology Coordinator

  Central Catholic High School

  (Educational Institution; 51-200 employees; Primary/Secondary Education industry)

  October 1999 — April 2001 (1 year 7 months)

  The IT department of a private High School. Responsible for all aspects of the schools IT infrastructure, including email, web, file and print servers, and the network.
  
  I was the first full time technical employee for the school. I inherited a patchwork of systems and worked hard to create a unified environment that could be managed by a single employee. This was where I received my first experience with Cisco routers and switches. I had an excellent mentor, an outside consultant the school used for the Networking projects. It was through his encouragement that my passion for Networking was born.

• Manager

  Dunnings

  (Computer Networking industry)

  1993 — 1999 (6 years )

• Presenter

  Carnegie Science Center

  (Non-Profit; 501-1000 employees; Museums and Institutions industry)

  November 1991 — December 1994 (3 years 2 months)

  As a Presenter at the Science Center, I interacted with the public to stimulate their interest in science and technology. We performed many different demonstrations of physics, chemistry, and biology. I spent a good deal of time working in the kitchen theater where we would talk about proteins in bread and eggs and why one adds cream of tarter to make a meringue. This was the position where I developed my customer service skills. We would average 5,000 guests on a weekend and thousands of children during week while school was in session. A friendly face and a listening ear did wonders to keep the public happy.

• Electronics Technician 2nd Class

  United States Navy

  (Government Agency; 10,001 or more employees; Military industry)

  August 1987 — May 1991 (3 years 10 months)

  The first year in the Navy was spent in a six months of classes on electronics. I instinctively use the core of the troubleshooting process we learned when working on network problems.
  
  The next six months was spent in Nuclear Power school. This second school focused on chemistry, mathematics, physics, nuclear theory, materials, and anything else you could imagine you would want a reactor operator to know.
  
  With the foundations in place, we then went to a prototype nuclear reactor to learn how to take the theory and put it into practice. I was the second person out of a few hundred to receive my qualification as Reactor Operator.
  
  Following this I then moved on to serve aboard the U.S.S. Atlanta. We spent the majority of the first Gulf War in a dry dock getting retrofitted. It was a different experience then most 21 year olds, but one where responsibility and accountability are an imperative.

Peter Hill’s Contact Settings

Interested In:

• career opportunities
• new ventures
• job inquiries
• expertise requests
• reference requests
• getting back in touch