PROFESSIONAL SUMMARY:

• I have over 22 years of proven experience with Systems Engineering/Service Engineering, as well as network/system administration, and web development as well as building automated scripting solutions. I am quite knowledgeable and adept to troubleshooting and maintaining small to enterprise level environments.

SKILL:

• Automated Scripting, Back End Programming, C/C++, Git, JavaScript, JSON, PHP, Python, Systems Development
• System Engineer, Lamp Stack, LAMP, NGINX, APACHE2, SaaS, Security Expert, Web Servers, Linux, Unix, Database Engineer, Service Engineer, Shell Scripting, MariaDB, MySQL, MongoDB, Network Engineer, Virtual Machines, Hyper - V, VMWare, Virtual Box, Gnome Boxes, Docker, Kubernetes, IAAS, PAAS, Cyber Security, Lead Systems Engineer, Open Source Software, Software Imaging, Data Dog, Service Now, SCCM, SCOM, Jira, Security Policies, Azure Engineer, Azure Architect, Systems Analyst, MVC, Engineering Documentation, VISIO, WMI, XML, CSS, HTML5, DNS, AWK, SED, RADIUS, DHCP, VPN, Bash, Scrum, Excel, Confidential Defender, Azure DDos Protection, Azure RMS, Custom internal monitoring systems built at Confidential .

WORK EXPERIENCE:

Principal Software Architect | Principal Systems Engineer

Confidential

Responsibilities:

• We use Jira heavily for SCUM and Agile boads. It is mainly used for documentation such as steps to complete a docker container build it and push it to the cloud. I also use it to heavly document all my API calls for future .I hold meetings with my developers every morning to set sprints for the work needing to be done on time, as well as making sure that all backlog tasks are being moved into production development, and switching non essential tasks to backlogs.
• I hold daily SCRUM meetings with the CEO to make suggestions on our 30/60/90 plans and how we can find a good ROI state for the company.
• I help with finance's as well so we can run the best systems at the most reasonable prices.
• I keep up with the latest technology stacks so I know what software would run best for our company on new technologies mainly in the cloud as it is moving very fast, both the .net stack as well as the Open Stack suite.
• I build all our environments out(Test,Pre-prod,Production). As well as our code repo using Git and Git Hub. I make use of the full azure cloud stack such as PAAS, SaaS, IAAS, IOT
• I have created Azure run books and init scripts, so I can pop off a Virtual Machine and have either my Power Shell Scripts setup a windows server, or Python/Bash Scripts in Linux.
• I am in charge of all security related issues including setting front end servers as well as back end servers that are accessible only internally, internal firewalls that we use are usually fortinet or Azure Security Groups.
• I have full knowledge of the Confidential Web Stack as well (HTML4/5, IIS, C#.net, SQL Server, ASP. Net, .net Core).
• I have a full knowledge of the web stack on the Linux wide as well using the LAMP stack(Linux, Apache, Maria Db, PhP).
• I have started doing testing on NGINX to use it as a reverse proxy server instead of a full Web Server as well as looking into server less computing.
• I have setup a WSUS server with a Vb Script to pick only what we want downloaded and updated the very few windows servers we are running(we are phasing out for Linux).
• On they Linux side simple bash and python scripts running daily to make sure that all our open source Linux servers are always up to date.
• I have created a in house monitoring system leveraging Python. If needed I do still program in C/C++ if we need very intense background work which is far few in between.
• I am currently working with my client on a refresh on one of his sites(i take care of 4 of them). We are trying out REACT.JS with NodeJS, using backend API’s.
• I am the architect for our whole infrastructure/networking/Cloud Systems as well as Cyber Security Policies.

Lead Sr. Systems Engineer

Confidential

Responsibilities:

• Moving shards from our MongoDB to alleviate it from its broken state.
• Held meetings to decide if we are going to take our services to the cloud or on prem.
• Meeting with the Database Developers to get them to quiet down the email noise.
• Fixed many Windows Issues as well as Linux issues. Patched Windows as well as Linux Servers.
• Created power point presentations for my director and manager that show our current environment state and to see if we needed any more dev/test/prod servers as well as diagram our whole RSM project.
• Used VMWare ESXI with all our Virtual machines and had to re-purpose them as well as move them around to different servers.
• Used the following scripting languages to make our mundane tasks easier by using Power Shell, Python, Bash, XML
• We held daily scrum meetins first thing in the morning, and would go over our Jira Boards to move ceartin projects into the back log as well as move more time sensitive issues into the Jira Board.
• I oversaw running the Service Now cleanup. This involved lining up all the environments so Gizmo and Service Now matched server records.
• I was put on the project of finding servers that were no longer in our environment and contacted the customer to get clarification on decommissioning the server, this included cleaning up AD Objects, Nutanix and VMWare servers.
• I would look at our ticket queue every morning to see what tickets needed attention and worked the tickets from start to close.
• I looked for gaps In the environment to see if there was a way to automate certain aspects of our duties, such as running bash scripts to pull reports from Gizmo/Service Now/Prism/VMWare/Nutanix.
• I had to build servers out for customers both Windows and Linux per there specifications this included heavy use of VMWare and Nutanix for VPS.
• I had to act quickly when a monitor went off and assess the issue and see if it was fixable on my end if it was not then I had to engage the on-call SE for the service.
• I was in charge of troubleshooting both Windows and Linux operating system's as well as systems in the cloud(AWS). I had to update KB articles when monitoring solutions changed as well as how to fix frequent issues that came up for other technicians could help customers in a timely manner.

Operations Engineer

Confidential

Responsibilities:

• I oversaw monitoring all of our Bidding and Ad Serving to customers and fix our Linux Servers that went down and caused critical financial damage to the company.
• I wrote numerous Bash scripts to automate some of our tasks.
• I oversaw running Ansible Run books to help automation across multiple services.
• I used Confluence/Ganglia/Grafana/Bamboo/Mesos programs for our primary tools set. I oversaw the Voldemort a user base for our customers information
• I was in charge of over 600 Linux Servers(CentOS)
• I had to monitor bidding and ad-servers in our F5 pool, if servers were down we had to take them out of the pool so they would no longer take traffic as well as enable servers that were previously disabled so they would be able to take traffic again. We had about 4 different pools to administer.

Service IT Engineer II

Confidential

Responsibilities:

• I was on call 24/7 365 supporting over 100k users as a Confidential Service Owner I had to ensure that ALL Confidential employees could reach the internet/internal applications as well as our cloud infrastructure.
• I was the DHCP and PROXY Service owner for the entire corporate Confidential environment. My main duties were to keep the services healthy and to find the current gaps in the services and improve to close those gaps. I had to run multiple projects at the same time and meet the deliverable deadlines that the stakeholders put in place.
• Two of the main projects that were focused on were creating a redundant environment for the DHCP service as well as adding a monitoring solution to keep track of the service health.
• We added DHCP fail over services utilizing Windows Server 2012 and the Active/Active feature provided with that platform. I played a part in the design and architecture work for this project by deciding which cities across the globe would host our new DHCP Servers as well as write the engineering documentation for the new service. Power Shell was used extensively to create all of our automation tools for administration as well as configuration work.
• I was tasked with creating a monitoring solution for our new DHCP Service that we rolled out over the summer, this was done by evaluating various products such as Men and Mice, IPAM and SCOM. I also was in charge of creating dashboard solution which consisted of custom ASP.NET (MVC) and C# code.
• A side project that I was asked to consult on was creating a test lab for the entire PAIX organization so employees could create VM's on the fly for their testing purposes. We accomplished this task by using Hyper-V and current HP SAN technologies.
• I was also the fill in service owner for the entire TMG PROXY Service across the Confidential environment. My main project was to retire the whole proxy infrastructure so we could replace it with new Fortinet firewall solutions as well as troubleshoot and correct any issues that users experienced while the service was being decommissioned.

Service Engineer

Confidential

Responsibilities:

• I assisted all of the infrastructure service owners when they needed help with various troubleshooting activities for customers and server build outs that would be consumed by all of Confidential employees.
• The services that I helped with were: PROXY; DHCP; DNS; DIRECT ACCESS; VPN; RADIUS; ACTIVE DIRECTORY; IPSEC
• I was the first point of contact for all critical escalations for the proxy service, I had to triage as well as fix the issue for the end user.
• I was in charge of keeping all servers belonging to our group up to date with critical security updates using internal WSUS servers, I also was tasked with documenting and creating an update plan for the PAIX organization. I built out all new proxy servers when we needed to add more capacity to our current environment. I also helped new hires understand current and emerging IT security policies.
• I created a metrics system for our group manager to keep track of what projects vendors were working on and how long it was taking them to complete their tasks that were assigned to them this data was then given to our director to view. This system was created in Asp. Net/C#.

Principal Security Engineer

Confidential

Responsibilities:

• was in charge of Confidential 's anti virus program And I had to actively monitor over 80k clients and Server’s at Confidential as to which Antivirus program was on there computers as they were actively pushed out in beta.
• I had to then create a power shell script as well as use WMI and Vbscript for workarounds on older systems. The main power shell script was able to identify all older versions of Confidential 's Antivirus program uninstall them and install the RTM version of the software all in the background. Vbscript was used on older machines such as Windows 2003 which has WMI turned off by default install and I was able to disable it with the script and WMI did the rest.
• I stood put many WSUS servers so we could patch only what was needed in our environment instead of the full load of updates as it could have had implication’s on our servers. We wrote policies that would push out all updates to regular clients machines every patch Tuesday after hours.
• I was tasked with building a Virtual Server environment using SCVVM as the automation system where I could make policies for certain OS images, such as Developers had access to bigger virtual machines as they had a good case reason for it, then for everyday users they were restricted to smaller images. SCCM was used to orchestrate the virtual environment and add packages that were needed. This was all built from the ground up, using 5 high end HP servers and a 6th for the main SCVVM host where all my images were stored I also had to do the networking which was split into many VLANS, using all CISCO switches and routers.
• I had to also do SDET work where I mentored and taught employees how to program in the C#.net ASP.net realm of programming also. I was the one in charge of taking the failed test cases to the developers and attended meetings with my manager as well as theres to get things straightened out and what we needed to do better on getting everyone up to speed.
• I wrote over 20 power shell scripts that monitored linux and windows machines to make sure that all resources were good on our clients and server systems. And if anything was not right, it would be reported back into the SQL Warehouse that I built for that purpose, some simple as checking for disk space to kernel dumps. And would have to do a RCA(Root Cause Analyst) and show my GM as well as the VP of the group what went wrong and how we can be more pre-active instead of reactive so the issues would be taken care of and not happen again.
• I was one of the few people on the team that knew Linux at a very deep level. I was one of them and worked with a co-worker using metasploit to poke holes in our Linux Systems as Confidential does run all flavors of Operating Systems(Windows/linux/Unix).

SR. Systems Engineer

Confidential

Responsibilities:

• My main project's during my time at Confidential were to test all new servers with spec bench marking software and report our data to their main website so customers could compare the data with competitor's hardware. The other project consisted of finding the best suitable solution to deploy operating system images to a container full of servers in a quick amount of time.
• The main tools that I used to test our custom servers was Spec CPU, Spec Web and Spec Power these tools had to be compiled from scratch and all data was uploaded to the SPEC website for customers to view and compare data with rival competitors.
• We created a custom solution which consisted of taking an empty semi-truck container and loading it up with custom Rackable Servers, my job was to figure out which operating deployment method we would use that would push out both Windows and Open Source Operating Systems. In the end we picked a Linux based solution that suited our needs. Both Hyper-V and VMWare were used in for testing scenarios.
• I was also the point of contact for our Amazon customers, I created many custom scripts in bash to support their server needs. Power Shell was also used for our Windows customers.
• I converted all of the company's physical infrastructure servers into Virtualized servers running on the Hyper-V platform. This saved the company money and space while extending the life of the IT services. compile the next version of windows as well as custom versions of legacy office applications for customers around the world.
• I was in charge of creating and maintaining all of the windows images that were deployed to bare metal servers, custom scripts were also created using Power Shell and Vb Script for deployment purposes.I lead a project to convert all the old Windows NT and Windows 2000 servers to a compact Virtualization environment to free up space for more up to date physical servers. This was done using Hyper-V and Power Shell scripts to convert P2V live migrations.
• I had to make sure that all server hardware was fully operational every day and react to server outages and replace failed hardware such as Hard Drives, Mother Boards, Network Cards and other peripheral devices.
• My main project was focused on removing old server hardware and putting in brand new server hardware in various labs across the Confidential campus. I also had to deal with Confidential SQL, IIS troubleshooting as well as hardware troubleshooting for the remaining servers before they were decommissioned. I also had to install new operating systems on the newly acquired and racked servers.

Operations Analyst

Confidential

Responsibilities:

• As an operations analyst at Confidential I worked in the pre - production data center, my main duties were to revive downed servers due to software or hardware issues.
• I also was responsible for troubleshooting IIS and SQL Server issues to resolution such as HP and EMC2 SAN Storage units were also our responsibility.
• We had to add user space to LUN's as well as make sure the SAN heads stayed operational. Every patch Tuesday we were responsible for making sure all the servers in the environment were up to date with their latest security patches, this was achieved through WSUS servers and IPAKS.
• I helped create various scripts using Power Shell for other administrators to use so they could finish their tasks more quickly.

Confidential

Tier III Data Service Engineer

Responsibilities:

• My main duties were to keep the MSN Data center Production servers up 24/7/365. I had to take ticket requests for problem servers and investigate the issues and work them to a resolution. This involved mostly hardware issues which could be taken care of quickly such as failed hard drives or complete mother board replacements. I also was in charge of racking and cabling the servers and then installing images on the bare metal servers with Altiris Imaging Software. All networking was also configured before being handed off to the customer.