Peter Marks Email & Phone Number

New York, New York, United States

Remote

I joined Signiant as part of an effort to modernize and redesign existing software running on traditional hardware into a containerized solution both for easier management and further augmentation. My efforts started by taking the existing proof-of-concept developer work and develop code-driven infrastructure built on EKS using Terraform and Helm.After several months of working with the traditional product, a team was created to design a new SaaS product on the Signiant platform based on this technology. I accepted the role as Team Lead for the first year or so as the platform was iteratively developed. The tech stack included an event bus inside the cluster based on Istio, Knative, and Triggermesh for purposes of in-cluster communications as well as integration with existing SNS topics and SQS queues. During this time, I was also responsible for running Agile ceremonies and project management.Once the platform was stable, I passed the Team Lead role onto the project's lead developer and focused on migration efforts along side implementing CI/CD automation. This included migrating code and pipelines off of GitHub and Azure DevOps and onto BitBucket and BitBucket Pipelines, respectively. This included retraining developers and assisting them with transitioning to the new engineering practices and peer review guidelines.As the product matured and was approaching a full production release, my efforts changed to focus on production readiness, system hardening, observability, and monitoring. While the platform and its automation was maturing, the developer experience was worsened due to the complexity of locally managing Minikube, the event bus architecture, and an increasing number of microservices. To resolve this, I developed a Python script to fully automate the process and enable developers to build and customize an environment without knowledge of working in Kubernetes, which ultimately truncated the developer feedback loop and reduced toil.

New York, New York

Engaging in SRE principles and best-practices, I was part of Peloton's SRE team and wore many hats as the team grew into multiple teams and evolved. Starting out as an SRE generalist, the team managed all platform operations in AWS using both EC2 and EKS, managing IaC through Terraform and Chef, as well as CI/CD through Jenkins, Circle CI, and GitHub Actions.One of my first specialized projects was building, maintaining, and handling training for a company internal DSL written in Chef for declarative management of Jenkins servers and job definitions. This included using the DSL for writing Jenkins jobs for automating and managing build and release operations.I also was a founding member of the Production Readiness team, responsible for curating the company's production readiness checklist and running readiness reviews on all new platform services, as well as working with developers through the process by evangelizing SRE principles.Finally, I was also a founding member of Peloton's Developer Experience team, tasked with supporting and managing Peloton's developer tooling, including automated Terraform deployment operations, CI/CD automation tooling, as well as an emerging developer portal built on Backstage.

Fair Lawn, Nj

As a DevOps Engineer, I was responsible for modernizing company infrastructure both in AWS and in a private data center. I worked on deploying a 10-node OpenStack cluster to enable cloud-type operations while retaining a physical data center for sensitive telecommunications systems. This included the migration of physical or virtualized systems into containerized workloads on the cluster, as well as integrating with an emerging AWS server presence. I was also part of the on-call rotation, handling incident response and following-up on open issues. This included both the standardization of physical servers through managing servers via Chef roles, maintenance of Docker images for containerized workloads, and monitoring of running systems with Nagios.

Hackensack, New Jersey, United States

As an operations engineer, I was solely responsible for all data center operations for a Parsippany colocation center, as well as remote server management for all company systems, including multiple VoIP telecommunications systems built on Asterisk and Kamailio. This included an on-call rotation for handling all company incidents, either through proactive monitoring or through a support hotline. During the workday, I mostly worked on new server provisioning, enhancing monitoring through SolarWinds, and followed-up on incidents for continuous system improvements.

Jersey City, New Jersey, United States

At ICAP, I was a second-level system engineer working in a global operations center responsible for monitoring and responding to incidents for a low-latency money market system deployed across 13 worldwide data centers and approximately 5,000 servers. Systems were predominantly Linux, but also included Solaris, Windows, and VMS systems.My primary role was to ensure all server-based incidents were resolved quickly to comply with strict SLAs and minimize financial impacts. In addition to my incident response duties, this included coordinating and managing all server data center operations, including scheduling system maintenance and repairs and directing field engineers with detailed instructions.

Hasbrouck Heights, New Jersey, United States

I was responsible for all on-site IT operations for the NJ office, including the on-site server room handling development systems based on Linux and HP-UX, as well as internal servers handling local systems and email. I was also responsible for building a JIRA-based trouble-ticketing system that allowed customer interaction and integrated with developer projects and planning.

Master Of Business Administration (M.B.A.), Business Administration And Management, General

Bachelor Of Science (Bs), Computer Science