Mayphus Tang

Hangzhou, China

Professional Summary

Experienced across CI/CD platforms, production operations, Linux systems, networking, and embedded hardware. At State Street, supported an internal delivery platform spanning GitHub Enterprise, Jenkins shared libraries, Ansible, AWS, databases, and Databricks, tracing failures across build, scan, approval, release, and deployment stages. Earlier roles covered physical and virtual infrastructure, VPNs, containers, reverse proxies, databases, and board-level camera and recorder repair. Strongest at turning incomplete signals into a clear failing boundary, a safe recovery plan, and a reusable operational handoff.

Core Skills

Systems

Linux, FreeBSD, TCP/IP, routing/firewalls, DNS/TLS, incident troubleshooting, ZFS

CI/CD & Automation

Jenkins, GitHub Enterprise, Ansible, YAML, Bash, Python, Racket, release troubleshooting

Cloud & Platform

AWS, EC2, Alibaba Cloud, Kubernetes, KVM, Docker/Podman, Databricks

Professional Experience

  1. 2022 - 2025
    DevOps / CI/CD Platform Engineer

    State Street Technology (Zhejiang) Co., Ltd.

    Technical environment: GitHub Enterprise, Jenkins shared libraries, YAML, Ansible, AWS, EC2, databases, Databricks

    • Supported engineering teams using an internal CI/CD and self-service deployment platform built on GitHub Enterprise, Jenkins shared libraries, YAML, Ansible, and release approval gates.
    • Investigated failures across build, security scanning, approval, release, and AWS deployment stages, including EC2, database, and Databricks workflows.
    • Correlated pipeline logs, shared-library behavior, configuration, automation output, application dependencies, and infrastructure state to isolate the failing layer.
    • Documented root cause, ownership boundary, safe workaround, reproduction path, and next action so teams could recover without relying on raw logs alone.

    CI/CD Failure Analysis Method

    • Start with the failed stage and its nearest authoritative signal: source or YAML input, shared-library execution, scan result, approval state, automation output, or downstream service response.
    • Compare expected inputs and outputs across adjacent stages to isolate the boundary between application configuration, delivery-platform behavior, automation, and dependent infrastructure.
    • Before recommending a retry, verify the current release state, the downstream resource condition, and whether the original failure left partial work that changes the recovery path.
    • Summarize each investigation as evidence, reproduction path, affected boundary, safe workaround, responsible owner, and next action rather than forwarding raw logs alone.
  2. 2020 - 2022
    Infrastructure Operations Engineer

    Hangzhou Fuzamei Tech Ltd.

    Technical environment: Linux, physical and virtual servers, Docker, Nginx, OpenVPN, WireGuard, monitoring, databases, blockchain

    • Operated physical servers, virtual machines, cloud resources, office networks, VPNs, domains, and TLS certificates as one production service estate.
    • Managed routing, firewalls, OpenVPN, WireGuard, monitoring, Docker build environments, Nginx, databases, and the runbooks used for daily delivery.
    • Supported deployment of blockchain-backed NFT and inclusive-finance services, covering reverse-proxy routing, database setup, service configuration, and release verification.
    • Diagnosed deployments end to end across network, host, container, application, and data layers before production handoff.
    • Converted working configurations and verification commands into repeatable operating and recovery procedures.

    Infrastructure Deployment Verification Method

    • Model a deployment as one service path: domain and certificate, routing and firewall policy, VPN or public reachability, reverse proxy, host, container or process, application, and database.
    • Verify the path from the outside inward so a healthy local process is not mistaken for a reachable and production-ready service.
    • When a check fails, move to the adjacent layer and distinguish connectivity, host state, runtime execution, application behavior, and data dependency before changing configuration.
    • Use production-readiness checks to confirm routing, certificate validity, service configuration, database access, monitoring visibility, and the expected external response.
    • Capture the final working state, verification commands, rollback or recovery steps, and ownership notes in a reusable runbook.
  3. 2018 - 2019
    Technical Support / Camera, NVR & DVR Repair Engineer

    Zhejiang Dahua Vision Technology Co., Ltd.

    Technical environment: Linux, ARM, HiSilicon, u-boot, TCP/IP, FTP, cameras, NVR, DVR, embedded hardware

    • Diagnosed and repaired cameras, NVRs, DVRs, servers, and network-connected embedded systems used in customer deployments.
    • Separated hardware, firmware, storage, boot, and network faults across Linux, ARM, HiSilicon, u-boot, TCP/IP, and FTP environments.
    • Performed board-level component replacement and full startup, storage, networking, recording, and device-function validation before return to service.

    Embedded Device Diagnostic Method

    • Use a fixed diagnostic order: power and board condition, bootloader and boot progress, firmware, storage, network configuration, service connectivity, then device-specific functions.
    • Classify the first abnormal stage before replacing components, separating boot-chain, firmware, storage, configuration, hardware, and connectivity faults.
    • Use TCP/IP reachability and FTP transfer results as independent evidence so network or deployment-environment problems are not misclassified as device failure.
    • After a repair, repeat the full startup path and validate storage, networking, recording, and device-specific behavior rather than checking only the repaired component.
    • Apply the same sequence across cameras, recorders, servers, and other network-connected embedded devices while adapting the final functional checks to the equipment type.

Selected Public Work

Education

Mechanical Design, Manufacturing and Automation 2014 - 2018

Changsha University

  • Built embedded and Linux systems through projects involving ROS robotics, 8051 MCU control, OpenWrt firmware, and Linux kernel module customization.
  • Combined mechanical, electronics, and software skills in engineering competitions and smart-agriculture automation projects.

Languages & Credentials

Chinese (native), English (CET-4), NCRE Level 2