Last active
April 12, 2024 15:23
-
-
Save mrreyes512/91db4ee7d322c69ed3131fd586ae03b2 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"meta": { | |
"theme": "elegant" | |
}, | |
"basics": { | |
"name": "Mark Reyes", | |
"label": "Site Reliability Engineer", | |
"picture": "https://raw.githubusercontent.com/mrreyes512/resume/master/my_profile.png", | |
"image": "https://avatars.githubusercontent.com/u/6344935?v=4?s=460&u=38f220a2c9c658141804f881c334c594eb1642ac&v=4", | |
"email": "MrReyes512@gmail.com", | |
"phone": "(512) 790-0901", | |
"website": "https://registry.jsonresume.org/mrreyes512", | |
"summary": "As a proud Naval Veteran, I transitioned from four years of dedicated\nservice in the Navy as an IT to embark on a successful 14-year journey with\na major ISP in Austin.\n\nIn my latest role as a Site Reliability Engineer within IBM, I have shifted\nmy efforts to optimizing operational efficiency through automation. With a\nspecialized focus on our team's Security Compliance and alignment with CISO\nguidelines, I am dedicated to driving excellence and ensuring seamless\noperations within the organization.\n", | |
"location": { | |
"postalCode": "TX 78665", | |
"city": "Round Rock", | |
"countryCode": "US", | |
"region": "Texas" | |
}, | |
"profiles": [ | |
{ | |
"network": "LinkedIn", | |
"username": "mrreyes512", | |
"url": "https://www.linkedin.com/in/mrreyes512/" | |
}, | |
{ | |
"network": "GitHub", | |
"username": "mrreyes512", | |
"url": "https://github.com/mrreyes512/" | |
} | |
] | |
}, | |
"work": [ | |
{ | |
"position": "Site Reliability Engineer(Security Focal)", | |
"name": "IBM", | |
"website": "https://www.ibm.com/careers", | |
"startDate": "2022-03-01", | |
"endDate": "2024-04-12", | |
"summary": "As an SRE within IBM, my primary responsibility revolves around automating\nmanual tasks that reduce human time required for complex procedures or\ndeployments.\n\nAs a Subject Matter Expert in promoting new feature sets, I've led over 20\ndeployments within a Sprint-based release framework. By optimizing our\nprocedures, I've transformed the deployment process from a multi-day\nendeavor into a streamlined, repeatable procedure completed in just a few\nhours.\n\nIn my role as the team's Security Focal, I am dedicated to automating\nSecurity Compliance requirements outlined by ITSS across our VM\ninfrastructure. Over the past five quarters, I have served as the trusted\nTechnical Owner Delegate for our team's Quarterly Security Assessments,\nconsistently achieving successful outcomes with minimal findings requiring\nattention.\n\nI ensured Application Secuity by automating a pipeline in Jenkins for our\nCode Signing Services during the build process. Automated vulnerability\nscanning was achieved using Twistlock and published results to our\nArtifactory Repository.\n\nImplemented a Netbox-Driven Lifecycle for virtual machines, using webhooks\nto automatically generate Jira tickets upon changes in VM's state. This\nseamless workflow will extended into updating VM's description in vCenter.\n", | |
"highlights": [ | |
"Technical Owner Delegate for Security Assessments", | |
"Automated Code Signing Services", | |
"Image Scanning Automation using Twistlock during build process", | |
"Defined a repeatable procedure for BlueFringe Deployments" | |
] | |
}, | |
{ | |
"position": "Manager Network Development", | |
"name": "Spectrum Enterprise", | |
"website": "https://business.spectrum.com/", | |
"startDate": "2019-04-01", | |
"endDate": "2022-03-01", | |
"summary": "During my time as the Manager of a Network Development Team at Spectrum, I\nworked together with a management team to transition a team of twenty\nNetwork Engineers into Network Developers. This included guiding many into\nunclear territory as their job functions were transitioned. Discovering a\nclear career path and building a collaborative culture were some of the\nsmall difficulties to overcome.\n\nOnce our Service Reliability Engineering team was estabilished, I guided\nthem to continue development of scalable Ansible Playbooks for Automated\nDeployments in our Production Environment; Building automated regression\ntests using GitLab CI/CD and Jenkins; and Containerizing legacy\napplications in Docker.\n", | |
"highlights": [ | |
"Established an environment with three vertical slice teams involving over twenty developers and three Area Product Owners", | |
"Guided my development team to automate a manual process which saved Spectrum a projected estimate of one million dollars in Capital Expense", | |
"Deployment automations using Ansible Roles allowing a scalable cookbook" | |
] | |
}, | |
{ | |
"position": "Sr Network Developer", | |
"name": "Spectrum Enterprise", | |
"website": "https://business.spectrum.com/", | |
"startDate": "2014-07-01", | |
"endDate": "2019-04-01", | |
"summary": "At Spectrum Enterprise, our primary focus was to improve efficiencies of\nour work-order pipeline by means of automating the provisioning of network\nservices. We participated in regular code reviews and followed the\nprinciples outlined in gitflow. Our automated build pipeline(CI/CD) was\nrun through jobs executed by GitLab Runners and Jenkins Jobs. Daily\nStand-ups ensured communication and transparency among the Scrum Team. We\ndemonstrated our progress to Stakeholders and Product Owners at a per\nSprint Iteration. This would allow a project to fail-fast and be agile\nenough to take new direction at the speed of business needs.\n\nAs a secondary hat, I developed scalable playbooks with Ansible roles to\nsystematically deploy our network orchestrator. This effort cut down\ncountless human hours during our production deployments and regression\ntesting.\n", | |
"highlights": [ | |
"Project Lead: Port Activation", | |
"Testing Lead: Andromeda Project", | |
"Development Lead: Systematic Deployments with Ansible", | |
"Application Development: Coffee Reports" | |
] | |
}, | |
{ | |
"position": "Network Engineer", | |
"name": "Spectrum Enterprise", | |
"website": "https://business.spectrum.com/", | |
"startDate": "2012-04-01", | |
"endDate": "2014-07-01", | |
"summary": "With Spectrum Enterprise's Network Engineering team I was able to obtain\nmultiple Networking and Security Certifications from multiple platforms. I\nwas able to obtain a CCNP in Routing and Switching, CCNA Security, Juniper\nJNCIA, and Alatel NRS-1.\n", | |
"highlights": [] | |
}, | |
{ | |
"position": "NOC Analysist", | |
"name": "Spectrum Enterprise", | |
"website": "https://business.spectrum.com/", | |
"startDate": "2011-03-01", | |
"endDate": "2012-04-01", | |
"summary": "Spectrum's Regional Network Operation Center(RNOC) Level 1 and Level 2.\n", | |
"highlights": [] | |
}, | |
{ | |
"position": "Broadband Tech", | |
"name": "Spectrum Enterprise", | |
"website": "https://business.spectrum.com/", | |
"startDate": "2007-04-01", | |
"endDate": "2011-03-01", | |
"summary": "Layer 1 field installation and troubleshooting for residential customers.\n", | |
"highlights": [] | |
}, | |
{ | |
"position": "Information Systems Technician", | |
"name": "US Navy", | |
"website": "https://www.navy.com/careers/information-systems-technician/", | |
"startDate": "2003-02-01", | |
"endDate": "2007-02-01", | |
"summary": "My time in the Navy was a brief 4 years and arose through the ranks of\nE1-E5. I also rose to the challenge of obtaining my Enlisted Surface\nWarfare Specialist(ESWS) pin while still an E3.\n" | |
} | |
], | |
"skills": [ | |
{ | |
"name": "Security Compliance", | |
"level": "Intermediate", | |
"keywords": [ | |
"Security Compliance", | |
"Nessus", | |
"Twistlock", | |
"Mend / Whitesource", | |
"Garantir GaraSign", | |
"Skopeo" | |
] | |
}, | |
{ | |
"name": "Software Development", | |
"level": "Advanced", | |
"keywords": [ | |
"Ansible", | |
"Application Containerization", | |
"CI/CD", | |
"Docker Orchestration", | |
"Gitflow", | |
"Jenkins - GitLab - Travis CI", | |
"RESTFUL HTTP APIs", | |
"Test Driven Development" | |
] | |
}, | |
{ | |
"name": "Network Engineering", | |
"level": "Advanced", | |
"keywords": [ | |
"IP Filtering / ACLs", | |
"Network Protocols", | |
"Routing Protocols", | |
"Subnet Addressing" | |
] | |
}, | |
{ | |
"name": "Telecom", | |
"level": "Intermediate", | |
"keywords": [ | |
"Cable Attenuation", | |
"DOCSIS", | |
"Hybrid Fiber Coax" | |
] | |
} | |
], | |
"education": [ | |
{ | |
"institution": "United States Navy", | |
"area": "Information Technology", | |
"studyType": "Computer Sciences", | |
"startDate": "2003-02-01", | |
"endDate": "2007-02-01" | |
}, | |
{ | |
"institution": "Austin Community College", | |
"area": "Cisco Network Academy", | |
"studyType": "Network Engineering and Technology", | |
"startDate": "2010-02-01", | |
"endDate": "2011-06-01" | |
} | |
] | |
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment