I enjoy problem-solving. My goal is to be the Gregory House of Internet/systems troubleshooting. My attempts to cultivate an acerbic personality have been fruitless thus far, however, since I'm too easy to get along with.
I am an extremely fast learner with excellent diagnostic skills, making me an asset in any troubleshooting position or as an evaluator of new technologies. My background is in programming and operational support of large application infrastructure, including:
I have root at Google. I'm on the team supporting Google's production infrastructure. Half of this involves production support and troubleshooting obscure, interesting problems that only occur at "Google scales". I have direct, primary supervision of "many thousands" of machines and responsibility for keeping our team's services running smoothly on those machines, alongside a batch processing load of thousands of users.
The other half of this role is automation and monitoring. I evaluate our needs in this area and write software and scripting (primarily in C++, Python, and shell) to perform routine tasks automatically, and to identify problems before they have a chance to hurt us.
As a Technical Architect, responsibilities included providing technical guidance and strategy for multiple development teams, developing standards for technologies used by these teams, and acting as a technical consultant and web subject matter expert. Designed and implemented a "large-scale" ("scare quotes" because I had no idea what "large scale" really meant until I started work at Google) distributed LDAP infrastructure for “Single Sign-On” web authentication. Other responsibilities included acting as the organizational representative for fraud and threat management and the technology standards board and a core member of the application server standards committee.
Unofficial side projects included setting up an internal tools server for common web development tasks, a mirror of various Internet repositories, and spearheading efforts to cut through bureaucracy to allow web developers to do their jobs in the face of an oppressive corporate work environment. I was also an early supporter (and author) of internal blogs as a way of sharing information internally in a time where documentation was tightly controlled and never easy to find.
As Sr. Analyst, I provided 24x7 operational support for web and application servers in the capacity of a technical lead. These systems were high-profile and acted as the primary production servers for www.sbc.com (and eventually www.att.com) and several major revenue-generating applications. I also provided a lot of automation and scripting, as a Perl subject matter expert.
Worked the helpdesk, responding to telephone and e-mail support for the Internet Service Provider. Focus turned to public-facing web site development, Perl programming, and producing customer documentation, ultimately producing several Intranet sites and applications for monitoring the health of the ISP's services and performing common helpdesk and maintenance tasks.
I am not currently soliciting employment. Non-specific and uninteresting inquiries will be ignored.