{"id":71,"date":"2011-06-04T23:18:08","date_gmt":"2011-06-04T23:18:08","guid":{"rendered":"http:\/\/www.ryanmatte.com\/?page_id=71"},"modified":"2026-03-27T23:00:55","modified_gmt":"2026-03-27T23:00:55","slug":"resume","status":"publish","type":"page","link":"https:\/\/www.ryanmatte.com\/","title":{"rendered":"Resume"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Work Experience
<\/span><\/h4>\n
\n

Senior Site Reliability Engineer at NVIDIA<\/span>
<\/strong>May 2021 – Present (4 years)<\/p>\n

    \n
  • Develop and maintain monitoring, automation, and tooling for NVIDIA HPC server farms.<\/span><\/li>
  • Debug and resolve complex issues impacting farm sites.<\/font><\/li>\n
  • Perform various types of admin work in the farms.<\/span><\/li>\n
  • Relevant skills: <\/span>APIs, Amazon Web Services (AWS), Ansible, Apache, Bash, Consul, Docker, Elasticsearch, Git, Google Cloud Platform (GCP), JSON, JavaScript, Jenkins, Kafka, Kibana, LDAP, LSF, Linux, MySQL, NIS, Nginx, OpenSearch, Perforce, Perl, PostgreSQL, Python, RabbitMQ, Redis, Ruby, SRE Methodologies, Sensu, Unbound, YAML.
    <\/span><\/li>\n<\/ul>\n

    Site Reliability Engineer at Zenoss<\/span>
    <\/strong>May 2021 – May 2022 (1 year)<\/p>\n

      \n
    • Performed development and operational tasks related to the Zenoss Cloud SaaS product.<\/span><\/li>\n
    • Operational tasks included ensuring the stability of the Zenoss Cloud SaaS product through monitoring and resolution of issues as they arose, onboarded new customers, tuned and scaled existing customer instances.<\/span><\/li>\n
    • Development tasks included debugging code, resolving defects, developing automation and monitoring solutions as required.
      <\/span><\/li>\n<\/ul>\n

      Senior Support Engineer at Zenoss<\/span>
      <\/strong>August 2013 – May 2021 (7 years 10 months)<\/p>\n

        \n
      • Provided advanced support with various technologies used in the product such as: docker, redis, memcached, hbase, opentsdb, mysql \/ mariadb, rabbitmq, zope \/ zodb, elasticsearch \/ kibana.<\/span><\/li>\n
      • Debugged code (Python \/ Java \/ Javascript \/ Golang).<\/span><\/li>\n
      • Investigated and reported product defects.<\/span><\/li>\n
      • Repaired database corruption issues.<\/span><\/li>\n
      • Performed development tasks such as authoring ZenPacks or creating patches (primarily in Python).<\/span><\/li>\n
      • Investigated and resolved performance issues (generally on large production systems).<\/span><\/li>\n
      • Provided guidance to Level 1 Engineers with any issues that they were having difficulty resolving.<\/span><\/li>\n
      • Required knowledge of many mainstream IT technologies as we have packages to monitor them and are required to support \/ debug monitoring issues related to them.
        <\/span><\/li>\n<\/ul>\n

        MSP Tools Team Lead \/ Senior Systems Engineer at Nova Networks<\/span>
        <\/strong>January 2011 – August 2013 (2 years 8 months)<\/p>\n

          \n
        • I retained all responsibilities which I previously had as a Systems Engineer, but I was the lead for the NOC toolset.<\/span><\/li>\n
        • I was responsible for day to day maintenance and configuration of the NOC toolset.  This included software such as our ticketing system (OTRS), our customer management database (CMDB), our monitoring tools (Zenoss and SolarWinds), our network config backup tool (ZipTie), and several custom pieces of integration code.<\/span><\/li>\n
        • I managed DNS, LDAP, and the NOC web proxy (which allows customers to connect to their servers).<\/span><\/li>\n
        • I was responsible for the development (coding), integration and deployment of new monitoring \/ reporting tools.<\/span><\/li>\n
        • I authored a ZenPack to monitor Windows Services via SNMP as we were having repeated issues monitoring several devices with WMI.  This allowed us to use WMI monitoring in a much more targeted fashion which improved the reliability of our monitoring.<\/span><\/li>\n
        • I was involved in the design and implementation of an advanced network monitoring solution for one of our clients which involved Netflow, QoS and IPSLA.  I developed \/ configured our monitoring \/ reporting components for these protocols.<\/span><\/li>\n
        • I developed a new automated customer notification system which integrated with our ticketing system as well as our new CMDB system (that is used to track customer device information such as data circuits, locations, contacts, service contracts, etc…)<\/span><\/li>\n
        • I performed a migration of a production MySQL database that was 17GB in size with over 70 million records in it.  It was migrated from MySQL 5.0 directly to MySQL 5.5 on a new server with less than 10 minutes of production downtime.  It was a query level migration, not binary, as the binary migration was not reliable between those versions.
          <\/span><\/li>\n<\/ul>\n

          MSP Tools Specialist \/ Systems Engineer at Nova Networks<\/span>
          <\/strong>January 2009 \u2013 January 2011 (2 years 1 month)<\/p>\n

            \n
          • Implemented and managed several Zenoss monitoring servers (26 at last count) in a NOC environment.<\/span><\/li>\n
          • Attained a high level of knowledge of VMWare ESX.<\/span><\/li>\n
          • Developed and maintained template ESX images to be used when setting up new Zenoss VMs.<\/span><\/li>\n
          • Performed commissioning of several clients in to the Zenoss monitoring system (one client having over 1000 devices, being a mix of Cisco routers, switches, and Windows servers).<\/span><\/li>\n
          • Compiled all publicly available Cisco Mibs in to Zenoss and released it publicly as a ZenPack.<\/span><\/li>\n
          • Created custom scripts to collect performance data from Windows servers via standard SNMP (no snmp-informant required).  Packaged the scripts and templates as ZenPacks and released them publicly.<\/span><\/li>\n
          • Created several custom device templates, event mappings \/ transforms, and reports.  Packaged them in to ZenPacks and deployed them across all servers.<\/span><\/li>\n
          • Created custom python scripts for various purposes including automated updating of hosts files from Zenoss, a command that standard users can execute to get UP \/ DOWN status of all devices from the commandline on each Zenoss server and python scripts that duplicate existing Zenoss reports (availability, interface, cpu and memory) for the purposes of report automation.<\/span><\/li>\n
          • Created a python daemon which watches for Zenoss events and automatically creates tickets in our ticketing system (OTRS), then automatically moves the events to history.<\/span><\/li>\n
          • Scripted and configured any other customizations that were requested by management.<\/span><\/li>\n
          • Maintained documentation pertaining to Zenoss in our Wiki system (including training documentation).<\/span><\/li>\n
          • Configured Zenoss core to use LDAP and to have assigned roles based on LDAP groups.<\/span><\/li>\n
          • Managed our LDAP system as required.<\/span><\/li>\n
          • Managed our DNS system as required.<\/span><\/li>\n
          • Was named \u201cZenoss Master\u201d by Zenoss Inc. due to my knowledge of Zenoss as well as my dedication to the Zenoss community.<\/span><\/li>\n<\/ul>\n

            Senior Network Analyst at Nova Networks<\/span>
            <\/strong>August 2008 \u2013 December 2008 (5 months)<\/p>\n

              \n
            • I performed the same responsibilities as listed below for Nuvo Network Management.<\/span><\/li>\n
            • I took on much more of a leadership role.<\/span><\/li>\n
            • I was responsible for auditing tickets that were worked outside of my shift to ensure that proper procedures were being followed.<\/span><\/li>\n
            • I would contact analysts to provide advice or assistance when required.<\/span><\/li>\n<\/ul>\n

              Network Analyst at Nova Networks<\/span>
              <\/strong>May 2008 \u2013 July 2008 (2 months)<\/p>\n

                \n
              • I performed the same responsibilities as listed below for Nuvo Network Management.<\/span><\/li>\n<\/ul>\n

                LAN Administrator at Transport Canada<\/span>
                <\/strong>May 2007 \u2013 April 2008 (1 year)<\/p>\n

                  \n
                • Personally supporting any type of computer related issue for over 240 clients.<\/span><\/li>\n
                • Ensuring that any issues are resolved in a timely fashion to meet strict SLA requirements.<\/span><\/li>\n
                • Communicating with clients via Phone, E-Mail, and in person.<\/span><\/li>\n
                • Managing permissions on network file shares.<\/span><\/li>\n
                • Managing Active Directory Group Policy Objects for application deployments, and permissions.<\/span><\/li>\n
                • Requesting the purchase of new computer hardware and BlackBerries.<\/span><\/li>\n
                • Managing the deployment of new hardware as part of yearly lifecycle process.<\/span><\/li>\n
                • Supporting any BlackBerry related technical issues.<\/span><\/li>\n
                • Assisting in relocation of computer equipment.<\/span><\/li>\n
                • Performing setups of computer equipment in boardrooms.<\/span><\/li>\n
                • Authoring scripts and macros to automate tasks when necessary.<\/span><\/li>\n
                • Performing hardware \/ software setup for new users.<\/span><\/li>\n
                • Ensuring that tickets for issues were logged in the ticketing system (Tivoli) and routed to other support groups as necessary.<\/span><\/li>\n<\/ul>\n

                  Network Analyst at Nuvo Network Management<\/span>
                  <\/strong>May 2006 \u2013 April 2007 (1 year)<\/p>\n

                    \n
                  • Monitoring customer networks \/ servers via HP OpenView and Nebula.<\/span><\/li>\n
                  • Working tickets that were auto-generated in our ticketing system (Remedy).<\/span><\/li>\n
                  • Dealing with outages in a timely fashion when detected to meet strict customer SLA agreements.<\/span><\/li>\n
                  • Following customer\u2019s strict notification \/ problem handling procedures as to meet contractual obligations.<\/span><\/li>\n
                  • Contacting carriers to have data circuits tested and escalating with them as necessary.<\/span><\/li>\n
                  • Contacting sites to assist in verifying equipment (generally Cisco routers \/ switches, but we supported a wide array of different types of networking equipment and servers).<\/span><\/li>\n
                  • Logging in to devices once they have regained connectivity to determine the cause of connectivity loss.<\/span><\/li>\n
                  • Monitoring client tape backups and logging in to the backup servers to resolve any issues when detected.<\/span><\/li>\n
                  • Implementing changes as required (on Cisco routers \/ switches as well as on servers).<\/span><\/li>\n
                  • Changes could include IOS upgrades on switches \/ routers, patching of servers, device reloads, device swaps, modification to configurations on routers and switches including route addition and interface configuration as well as many other types of changes.<\/span><\/li>\n
                  • Configuring ports on Cisco switches running both IOS and CatOS on demand as requested by on-site techs.<\/span><\/li>\n
                  • Performing tape changes in our communications room as scheduled.<\/span><\/li>\n<\/ul>\n

                    Level 2 Help Desk Analyst at HP Enterprise Helpdesk<\/span>
                    <\/strong>May 2005 \u2013 April 2006 (1 year)<\/p>\n

                    Evening shift duties included:<\/em><\/p>\n