I work with a team of talented engineers to build and support infrastructure for Dataminr.

I was on Trust SRE team as the tech lead. During that time, I was almost exclusively focused on the Anti-Abuse portion of our services. I worked with my manager, teammates and developer partners to create a program to increase our team’s depth and bring our operations closer to the embedded SRE model. I also was part of a virtual team which delivered training on Azure to SRE staff throughout the company.I was also part of the Fabric Lifecycle Automation team, where I was focused on building infrastructure as code for running the LinkedIn stack on Azure. I was also part of the Source of Truth team, which owns crucial low level infrastructure systems that power LinkedIn.

- Senior Principal Software Engineer• I was part of the Compute IO team - this included SELinux rollout planning and early due diligence. I also helped establish better SDLC practices within the team.• I was part of the Dyn Edge team - this was mainly Python development for a service that rendered zone files for Bind from tenant data we consumed from an upstream service, and operational work on the same service- Senior Principal Security Analyst, Cloud Operations• I was part of the Cross Services - SaaS/PaaS/IaaS organization• I contributed to several virtual teams in the Cross Cloud org• My first virtual team role focused on image builds for OCI (Oracle Cloud Infrastructure) using Jenkins and Packer• I was also a member of a virtual team focused on managed Kubernetes for OCI. This team was responsible for an internal deployment tool of Kubernetes and also some related CI tooling (Docker, Jenkins, etc)• Another virtual team I was on focused on building an OCI native service. This team is where I have spent the most time and contributed the most• In the scope of Cross Cloud virtual teams, my role includes understanding OCI at a deep level (including what is not visible to the public), and building resources in the cloud with a variety of tools, including Hashicorp Terraform as well as custom tools talking directly to the API. There is also a large amount of cross-team and cross-org collaboration• While most of my focus has been on OCI and virtual teams, I also contributed to the technical leadership and road maps within the Cross Services organization, and helped drive technical, infrastructure, and process improvements• I was part of a small team that handled all technical interviews and improved and refined our hiring process. We made a lot of improvements and hired some amazing people as a result, while also avoiding missteps• Part of my role within Cross Services was also to function as an ambassador or bridge from OCI-C (OCI-classic) to OCI

• I was part of the Enterprise Platforms Engineering team• I was one of two team leads for a team of about 15 engineers• My team did PaaS for the business side of Facebook, and also supported some core infrastructure services• My primary focus was leading our OpenStack efforts, which included leadership of a smaller sub-team that was focused nearly exclusively on OpenStack• I Built a PoC and then our test, stage and production instances of OpenStack, using Mitaka, Newton, and Ocata releases, using IPv6 for the control plane and dual stack IPv4/IPv6 for the data plane• Facebook uses Chef for configuration management; I contributed a small amount to Chef, but it was not a core focus• I also contributed to our OpenStack automation, written in Ansible • I collaborated with other engineers throughout our organization to coordinate our efforts and make sure that we were all moving in the same direction and things we were working on would fit together• I was active in the OpenStack community• I made some modest contributions to OpenStack and collaborated with leadership and legal to be able to contribute code on behalf of Facebook• I was an OpenStack mentor for the Women in OpenStack group at the OpenStack Summit in Boston (2017)• I worked with vendors to evaluate software, and participated in an on call rotation, which covered a massive amount of services including all of our virtualization platforms and ancillary services.• I delivered training for OpenStack to my team for about 6 months in a one hour session each week, including lectures, hands on labs, and break-fix scenarios• I regularly presented in large talks about the direction of our team, and our organization based on the projects delivered by me and my team, with guidance from my management chain, including our org director. These varied between tech talks, roadmap updates, lightning talks, and longer deep dives, depending on the needs of the team and the org

• I worked on the Content SRE team at LinkedIn in San Francisco; we were responsible for site reliability engineering of several very visible portions of linkedin.com, including groups, publishing, pulse, and sharing.• My teammates and I worked with several development teams to ensure product releases were stable and we monitored key metrics, like queries per second, latency, and errors.• My team and I authored operational tools to interact with LinkedIn's monitoring framework (check out the LinkedIn engineering blog for some of the technologies we worked with).• I tackled problems related to scale and design, and participated in design forums and reviews with other senior engineers and developers.• My role included participation in a 24x7 on call rotation, and we worked closely with both development and the NOC on escalations or outages related to our products when they occured.• We investigated and resolved both internal and user facing issues from the bottom to the top of the stack.• My team and I supported an ELK instance, several Memcache and Couchbase instances, as well as a large number of microservices that composed the user facing services we supported.• I migrated many of our static services and instances running on bare metal to an internal containerization platform that leveraged cgroups and namespaces for co-location as part of a horizontal initiative.• I worked with my management chain and several teams to decommission a legacy service.

• I worked on the hardware engineering team at Twitter, where we characterized performance of all server hardware and network OEM hardware before it was purchased; we also collaborated with ODMs and deployed designs co-authored by our team and hardware vendors.• I was the frontend platform lead systems engineer for the hardware team, and the lead system engineer for all GPU/deep learning platforms.• I also did a small amount of configuration management with Puppet.• I collaborated with several service engineer teams (SRE), as well as OS team, kernel team, and PE (deployment automation team).• All the System engineers on my team (including me) contributed to the code base for automating deployment.• My role included maintaining our test lab infrastructure (devops for my team). This included core infrastructure services like DNS, as some other more esoteric services specific to our environment.• I developed and maintained a widely used custom liveOS, using open source tools (livecd-tools); this OS included many specialized tools, as well as open source tools and was built on CentOS. I made several build flavors available for different testing purposes.• I wrote several tools in Python, including a tool for power qualification and regression testing, and wrappers for industry benchmarks like fio, SpecCPU, SpecJVM, and stream. I significantly improved our memory qualification testing automation. I also wrote several test cases for autotest, and integrated the most popular tools I wrote into the autotest suite. I also automated log shipping between us and a key vendor, to enable us to determine the quality of that vendor’s testing and other deliverables.• I mentored other engineers, including system engineers, and some of the more hardware focused people on my team as well. Primary areas of mentorship included Linux, Python, and Bash.

• I worked with a small team of engineers to maintain the core services for deployment and development tools for all of Yahoo! These services included bugzilla, twiki, etc. (devtools), and (deptools) services that provide system role data, system state data, and package repositories (for the internal/proprietary package system yinst) and lastly the deployment engine (pogo).• Within my team, I rotated around and worked on the properties/services that were problematic, and stabilized them. My first challenge was our deployment engine; once the deployment engine was stable and performance was far improved, my next focus was the system roles service. Most of the services were focused on a REST API and passed data around with JSON, and the most common language for tools and services was Perl. • I contributed policy where appropriate on best practices to improve the scalability/maintainability of the services within the group.• I authored and commited scripts, packages and patches, both of my own creation and in collaboration with development on their existing code base.• I was part of an on-call rotation.• My daily tasks included primarily system and log analysis and troubleshooting, as well as Perl authoring and debugging.

• I worked with a small team of engineers as the bridge between support and development engineering.• I analyzed complex problems, and when appropriate, filed defects and worked with development engineering to provide insight into the problem. • I authored many tools for myself, my team, and some for the entire support organization. Almost all of those scripts were in Perl. I used subversion for version control on a Fedora Linux sever, for which I was also the System administrator.• I also worked with customers during serious outages and recovery scenarios. This ranged from re-cabling and replacing components to running commands on the console (serial or ssh) of various system components to recover and prevent data loss (in the scale of TeraBytes to PetaBytes)• I was part of an on-call rotation.• I was the Linux, UNIX, and scripting SME (Subject Matter Expert) for my team and organization.• My daily tasks included log analysis and troubleshooting, Perl and bash scripting (mostly Perl), and mentoring of new ASE (Advanced Support Engineer) members, as well as TSE (Technical Support Engineers, or first-level support)

• My duties were to operate, build, test, and support the production AAA application environments within a fast paced WiMAX network.• I also worked with other groups to enhance network reliability and support new features. As the WiMAX standard was enhanced, and vendors added new features, our network grew and changed to accommodate. As our subscriber count grew, so did the technology required to support those subscribers.• Worked with the appropriate vendors toward resolution when problems cannot be solved in house• My day to day tasks included Solaris and Linux administration, scripting, and networking tasks. This included but was not limited to: log analysis, packet capture and analysis, network troubleshooting, load balancer config, package and OS install/config, Perl/shell scripting, and database usage.• I was on-call 24x7, and the only engineer responsible for the production AAA instance after only a month. I held this responsibility for the remainder of my tenure at Clearwire.

• Technical support for clustered storage running Isilon’s OneFS (based on FreeBSD) • Support integration with Active Directory (via Samba), OpenLDAP, and NIS • In depth troubleshooting, including packet capture and analysis of network traffic, tuning for CIFS and NFS, and other various break/fix issues. • Log analysis, remote support, configuration, and troubleshooting. It is very common for me to leverage remote access to resolve customer issues on demand. • Hardware troubleshooting • Identify workarounds for existing bugs and identify/escalate new bugs to Application Engineering

• Perl development: development of utilities, reporting, and automation for multiple UNIX platforms. EPM Packaging for deployment on Linux, Solaris, HP-UX, and AIX. Similar shell scripting. • Member of Global Data Center Operations Team. We support Oracle’s critical, high visibility, high uptime environments, and critical internal operations. • Manage Petabytes of backups per month in the Oracle’s largest, primary Data Center in Austin, Texas, which houses more than 12,000 servers. • Provisioning of new systems, per company build SOP.• Contributor to development of Oracle Enterprise Linux Certification. • Deliver internal training on backups and infrastructure. • Part of weekly On Call rotation; it's a 24x7 operation. • Management of large tape libraries such as the ADIC/Quantum Scalar i2000. • Some SAN/NAS administration.

• Support and administer a lab of roughly 300 systems, running many versions of various operating systems, including RedHat Linux, SuSE Linux, OpenBSD, AIX, HP-UX, Sun Solaris, Windows, and Netware• Administrator for all high end hardware, including a Sun Fire E6900, an EqualLogic iSCSI device, and our more esoteric/expensive platforms, such as PA-RISC, PPC, and Itanium. • Administrate network devices and infrastructure, including firewalls, routers, switches, DNS, DHCP, etc. • Support testing for both our database and integration products, which means testing on several releases of many products on all platforms. Some applications I manage include Oracle, Microsoft SQL, MySQL, PostgreSQL, Informix, and IBM DB2. • Support testers and developers using various combinations of operating systems, applications, and network services• Assist with production network responsibilities, similar to lab responsibilities.

• Support and administer all machines in Zebra Imaging network, primarily focusing on Linux clusters. We had 5 clusters: one test cluster of only 4 nodes, three production clusters with 16-20 nodes, and a cluster of 50 nodes, running on ppc. We also had about a dozen infrastructure Linux machines, in two sites, and about 6 important windows machines for active directory and corporate users.• Supported development environment, developers, and the cutting edge technology Zebra developed. Most of the code base was written in C, C++, TCL, and an extension of TCL. • Managed data integrity, backups and security for the entire organization. This includes developing maintenance plans, password and security policy, and implementation. • Scripting in Perl and Bash• System monitoring and performance tuning.• Redesign, implement and reconfigure two sites to meet government security, auditing, integrity, and availability standards (DCID6/3) for processing Top Secret data (SCIF).

POD Server Support Analyst • 06/2005 – 10/2005• Linux, VMWare ESX, Active Directory, Exchange, MS Cluster Services, HPCC, Dell Open Manage skill sets• Enterprise hardware and software, advanced configuration, deployment and disaster recovery; this includes calls that require billable software resolutions, with emphasis on complex software configuration. Took calls with end to end case ownership in a “Top Tier” support role• One of the highest escalation points at DellCSD Network / Tech Analyst • 08/2004 – 06/2005• SME (Subject Matter Expert) for Active Directory, Exchange, and Linux• Troubleshooting of issues from break-fix to advanced configuration and deployment / disaster recovery• Enterprise level hardware and software support, such as SCSI, RAID, ClusteringNetwork Tech / CSD • 12/2003 – 08/2004• Networking and Escalations SME (Subject Matter Expert)• Wireless support• Troubleshooting of various issues from basic break-fix to advanced configuration