Derek Andree's answers

When I first started at Amazon.com, I was an engineer in the Network Tools and Analysis team. I started as

a Network Engineer I, and quickly (within three months of being hired) moved up to Network Engineer II with

project lead responsibilities.I worked with HP OpenView, MicroMuse Netcool, all Cisco software suites, and

freeware tools such as MRTG and RRDTool. I was project lead for all of our in house (Perl) monitoring

software applications including traffic graphing, network latency reports, alarm generation for on call

engineers, WAN circuit monitoring, and even uptime monitoring of our monitoring software. After 6 months

of employment, I was given the authority to prioritize my projects without intervention from management. I

was also given the freedom to create and prioritize new projects at my discrecion. I was also promoted to

project lead and delegated work load for my projects to our team of network tools engineers.I gained much

experience with Cisco products including all series of routers, switches, WAN switches (IGX/BPX), PIX

firewalls, LocalDirectors and Distributed Directors. I worked very closely with Cisco product

representatives, software engineers, development engineers and network engineers to drive their development

of their software and hardware to meet our requirements and unique needs. I participated in our on-call

rotation, providing tier 2 support of our global network including all network related hardware and

software. I was later promoted to the tier 3 support oncall team. This was an honor for me as all other

engineers in this group were senior network architects.One of the greatest skills I learned at Amazon was

the ability troubleshoot any networking related problem, many which had never previously been discovered in

the technical community. As a result of my oncall experiences, I voulunteered for the responsiblity of

driving vendor product development and bug fixes. Many times I was required to engineer work arounds when

the vendor could not provide a satisfactory solution or time to resolution. I also furthered my experience

with OSPF and BGP routing protocols....

I'm proud to have worked at the world's largest online retailer. As a senior engineer in
the Network Architecture team, I was exposed to the cutting edge of computer networking.

Notable experiences include:

Lead architect for network monitoring and analysis projects

I wrote much of the software we used to monitor our global network. Created a network database
to track all equipment and provide a source of record for other monitoring tools. Regularly
wrote custom software to integrate existing monitoring software. Wrote graphing software to
display data about network metrics gathered by a collection agent I wrote. The agent was modular
to allow for any arbitrary collection module to be integrated, and I wrote the SNMP and automated
login module for the collector.

Actively involved in data center network designs

I was involved in creating standards and repeatable designs for rapid data center deployment.
Contributions to this project included IP allocation standards, device configuration standardization,
automation of monitoring for newly deployed equiment, and procedural documentation for datacenter
technicians who deployed new equipment.

Lead architect for all remote site VPN/WAN networks

Soley responsible for network design for all remote sites including remote offices, distribution
centers and customer service centers. Managed timelines and resources across multiple groups to
ensure timelines were met for our extremely aggressive schedule. Deployed over 50 remote sites in
one calendar year, which would not have been feasible without standardization I introduced.

Responsible for subnet assignment and management

I was solely responsible for all IP space at Amazon.com, and wrote software to manage both current
subnets and new allocations. The application would also monitor which subnets were found in router
forwarding tables and would display the information accordingly.

Administration of network monitoring servers (Unix and Windows)

I was our system administrator for our monitoring servers. Most servers were Linux or Solaris, but
a few were regretably running Windows.

At Amazon.com I was exposed to nearly all models of Cisco network equipment. I regularly evaluated yet-to-be-released equipment from various vendors, and provided buying descision guidance. I had daily interaction with load balancers, routers, switches, and firewalls....