Retired

In this role I am primarily responsible for the continued upkeep and improvements to our customer facing production platforms. This involves working closely with the product to understand trends as well as issues over time to further our products. In this role I routinely work with other teams to set business standards around procedures involving mostly change control, release management, and maintenances. Some of the work streams include:- Commonly visit with teams to understand pain points so that we can deliver better experiences to teams supporting our products. - Weekly review of issues to formulate with team ideas to solve. - Generate metrics and reports from where restructuring and automating is required.- Project development to solve for deficiencies in processes. - Bringing of teams together to avoid silos and streamline our communication.- Deliver monitoring solutions to have teams across the business have insight into customer resources.- Continued capacity management and automation of build outs.- Holding continued brown bag sessions to help teams improve their awareness on how things work.- Attend other team meetings to provide constant communication around progress.In this role I manage a team of 14 Operations Engineers where we work together to ensure uptime across over 4000 systems, provide devops functions, as well as run with large projects surrounding new features and improvements.

Responsible for the continued improvement of our offering as well as building a strong collaborative team. Currently managing 10 system administrators ranging from level 1 responsibilities to 3 including engineering related functions. Team is split between 6 Linux System Administrators and 4 Windows Administrators.Focused on encouraging team collaboration, improving our processes, encouraging ideas, setting team / personnel expectations, improving communication both within our team and cross team, improving awareness, improving accountability, and finding areas for system improvement.In this role I am in charge of performing one on one reviews, holding team meetings, building team schedules, writing out performance reviews, and helping employees map their career growth.

Responsible for leading a team of 8 System Administrators. Overcame many difficult obstacles to continue building a strong team.This role was split between being a Team Lead and continuing my previous role as a system administrator. This was mainly because we needed all the help we could get on the systems side.Responsibilities included having consistent one on ones with employees to guide them through their career progression. Also performed mid year and and of year performance reviews.

In this position I was primarily responsible for the monitoring and upkeep of our cloud environment. Monitoring tools changed over the years. Initially Hyperic was utilized, then switched to Nimbus, and now Zenoss.This environment consisted of approximately 2,000 servers. The server's OS were either Debian or RedHat, including Windows.The software used varied from, LDAP, Apache, FTP, Postfix, NFS, MySQL, VMWare, PHP, Puppet.As I grew in this role, so did my responsibilities. At first I was responsible for the remediation of systems, handling escalations from support, and escalated customer tickets. This then grew towards being more proactive than reactive. This involved strategizing and collaborating with others on how we could improve our environment. This all lead towards a significant improvement of our offering.The responsibilities also involved building tools to more efficiently do our jobs. My expertise fail within general linux system administration. Basically finding issues affecting an operating system and taking steps towards addressing them.

Initially started as an intern to help answer customer calls. Primarily responsible for working directly with our customers regarding any hosting issues. This varied from email, dns, troubleshooting code (PHP / HTML / CSS / JS), and database (MySQL) connectivity.After 6 months I was brought on as a full time support specialist. After a short while I was promoted up the chain from a Level 1 technician to Level 3.Responsibilities grew where I was mainly in charge of handling escalations, documenting procedures, and providing mentorship to new hires.Part of this role involved building tools and knowledge bases for our support staff to more efficiently support our customers.I was responsible for leading many projects, some that have resulted in the continued use of them today (7 years later).