Job Title
Technical Project Manager (TPM) – Hands-On DevOps & Delivery

Key responsibilities

• Plan & track delivery
  • Break epics into INVEST-ready stories, maintain burn-down and surface risk early.
  • Own the monthly release train—branch cut, go/no-go, automated smoke tests, rollback playbook.
• DevOps & build automation (core duty)
  • Keep GitLab CI/CD green—write, debug and optimise pipeline YAML, runners and caches.
  • Automate build scripts (Bash / Python) for versioning, artefact upload and basic signing; extend to full desktop packaging as you ramp up.
• Quality automation
  • Design and maintain a lightweight smoke / regression harness (pytest, Playwright, k6 or similar) that runs in GitLab CI.
  • Ensure every new feature ships with at least one automated test; keep the harness green.
• Technical facilitation
  • Read production code (any modern language) to trace call flows, validate sizing and review small MRs; willing to pick up additional languages as needed.
• Cross-site coordination Run planning, stand-ups and retros across Hong Kong
  • Shenzhen pods.
  • Keep GitLab issue boards / labels and the team’s Definition-of-Ready / Done clean and current; publish concise release notes.
• Data-driven reporting
  • Maintain real-time dashboards (Grafana, Superset or similar) so leadership sees status at a glance—no surprises.

Must-have qualifications

• 3 + years leading technical programmes while writing or maintaining CI/CD automation for real products (fin-tech, trading, banking or SaaS all welcome).
• Hands-on proficiency with GitLab, GitHub Actions, or Jenkins pipelines—you can fix a red job without waiting for another engineer.
• Solid scripting in Bash or Python; comfortable automating build, test and release tasks.
• Demonstrated ability to read production code (Java, C#, Python, C++, TypeScript, etc.) and eagerness to learn unfamiliar stacks within six months.
• Working understanding of cloud fundamentals—containers, IAM, object storage—and interest in introducing an infrastructure-automation tool (Pulumi, Ansible, CloudFormation, etc.).
• Proven track record of keeping a regular release cadence (monthly or faster) on schedule.
• Clear written and spoken English; Mandarin or Cantonese is a plus for SZ collaboration.