To solve problems that involve everything from operations, all the way to front/back-end development. Particularly interested in high-availability systems, Amazon Web Services, and information security.
Advanced knowledge of Amazon Web Services; holding multiple AWS certifications.
Primarily a Linux (Ubuntu) user, but also experienced with Windows and OSX.
Solid grasp of server ops, system architectures and information security best practices.
Good knowledge of design principles (typography, golden ratio, colour theory, etc).
Responsible for automating and improving infrastructure, using Chef for configuration management.
Designed and wrote tools in Ruby to automate third-party application configurations.
Seamlessly transitioned AWS infrastructure from EC2-Classic to VPC, overhauled AWS accounts to follow latest security best practices, reduced AWS costs by over 30%, and wrote documentation.
Lead PagerDuty's major incident response process; Act as Incident Commander during major incidents, wrote extensive documentation, provide training, and built chat tooling.
Strong focus on security; Designed and delivered company-wide security training for all employees, wrote formal security incident response plan, overhauled public vulnerability reporting process, and wrote extensive documentation on security processes and best practices.
Spoke about PagerDuty's Failure Friday program at an Advanced AWS Meet-up in 2015.
Led the Server Engineering and Operations team for Global Professional Services at Gracenote's San Francisco office. Building products and tools for both internal initiatives and international clients such as Bang & Olufsen, NET Serviços, and Sony.
Responsibilities included designing and developing new back-end services, maintaining and expanding our AWS infrastructure, and providing mentorship to others on my team.
Provided continuous 24/7/365 primary on-call support for all server applications and systems.
Responsible for app/system security. Continually performed reviews to ensure compliance with InfoSec directives. Stayed up-to-date with latest vulnerabilities to proactively mitigate new threats.
Built a variety of proof-of-concept web prototypes to demonstrate Gracenote's latest APIs and technologies, which are used as sales demos at trade shows and conferences.
Managed team resources, and liaised with other teams to provide project scopings and deliverables.
Gravity Mobile was a wholly owned subsidiary of Gracenote, who subsequently merged with them in May 2013.
Operations; Responsible for provisioning, maintaining and improving upon server infrastructure, split between physical data centres and AWS. Also provided 24/7/365 on-call support.
Wrote scripts/tools to fully automate application deployment, configuration, self-repairing, and monitoring. Experience with F5 BIG-IP and Synology hardware, and VMWare ESXi.
Amazon Web Services; As a passionate advocate of AWS within Gracenote, I migrated my department from a physical data centre environment to AWS. I also designed, built, and deployed a multitude applications utilizing almost all of the AWS stack (Including EC2, R53, S3, RDS, DynamoDB, SQS, IAM, and EMR), focussing on high-availability, fault tolerance, and auto-scaling.
Back-end Engineering; Migrated applications from monolithic to service-oriented architecture.
Built several stand-alone applications from the ground up, including a service framework, event logging system, “big data” (10TB+) analytics platform, and various content management tools.
Designed and built the PHP services/APIs that support some of Gracenote's mobile applications, such as MusicID and HABU. Also wrote extensive documentation, unit tests, and tools for all apps.
Responsible for design and development of a new baggage messaging framework, interacting with sortation, reconciliation, tracking and security/screening systems. This resulted in faster and easier to maintain code, compatibility with more baggage systems, and fewer corrupted messages.
Heavily involved in airline cut-overs, ranging from small/domestic to large/international airlines.
Constructed a variety of internal monitoring/investigative tools using Java and PHP, in my spare time; and maintained other internal tools written in Perl, Python and Ruby. My tools were used by dev and support teams, and became the preferred method of investigating baggage issues.
Attended airline face-to-face meetings as the Amadeus baggage systems expert.
Primary and secondary production on-call as needed, resolving production issues in real-time.
Acting manager of the Baggage Team during manager absence, and for a 12 week transition period.