Senior DevOps​/Release Engineer

TrendAI™, the global AI security leader and enterprise business unit of Trend Micro, empowers organizations with full AI visibility and consolidated security that inspires confidence, drives innovation, and eliminates risk. At TrendAI™, we’re always seeking exceptional talent; people who want to collaborate with the best and push boundaries together. Here, your work goes beyond building a career. You will help protect what matters and play a vital role in shaping a safer, more trustworthy AI-powered future.

AI Fearlessly.

LOCATION:

On-Site / Hybrid (Austin, TX)

Position Summary:

TrendAI is seeking a Senior Dev Ops / Release Engineer to own the CI/CD, build, release, and infrastructure backbone for our on-premises network security appliance, shipped as both physical hardware and virtual editions. The appliance is a large Java monolith built through Ant and gated primarily by Git Hub Actions, with a shrinking legacy Jenkins footprint you will help retire as its current build-toolchain versions reach end-of-life/end-of-support.

A blocking-mode agentic PR reviewer and an AI-based PR responder already run in production against it: a live system to mature, not a greenfield one to invent. You will build automated gates protecting release branches, sign and stage releases, and keep self-hosted runners and lab infrastructure healthy, balancing the rigor of physical/virtual lab release cycles with the modernization of cloud microservices and agentic automation.

Secondary to that primary workload, you will extend the same CI/CD and infrastructure discipline to a companion set of Go and Node microservices deployed to AWS via Terraform/Terragrunt and the Serverless Framework. This is a senior IC role with broad autonomy over tooling and infrastructure decisions, and a mandate to push AI-assisted automation into daily operations rather than treat it as a side experiment.

• 1. Own and operate the scheduled CI/CD pipeline suite (regression/BVT, integration, UI/functional, and nightly or on-demand workflows) for the on-prem appliance across main and release branches, triaging failures daily and distinguishing real regressions from lab or environmental noise.
• 2. Author, refactor, and maintain Git Hub Actions workflows and reusable actions for the appliance product, including migrating the remaining legacy Jenkins jobs onto Git Hub Actions ahead of their build-toolchain's end-of-life/end-of-support window, workflow-dispatch orchestration across multiple repositories, matrix builds, self-hosted runner targeting, and secrets/permissions hygiene.
• 3. Eliminate manual "build cop" duties by architecting and operating preventative branch gates:
  Git Hub Merge Queue (or equivalent), speculative/batch merging, and automated flaky-test quarantine that removes unreliable tests from the gate without removing signal, so main and release branches never break.
• 4. Administer Git Hub organization structure: repositories, branch protections, teams, user access, and the lifecycle of branches including cleanup of associated builds and artifacts when branches are deleted.
• 5. Modernize and maintain build/lab infrastructure supporting the appliance (bare metal and virtual), driving the transition toward ephemeral runners, automated patching, and declarative infrastructure-as-code, on both direct-managed hosts and machines shared with other teams.
• 6. Manage code signing and release packaging for the appliance: sign builds destined for continuous regression use, track and apply detection or definition-file updates through their PR lifecycle, and keep versioned build metadata consistent across the systems that consume it (test schedulers, release trackers).
• 7. Eliminate manual release bookkeeping by…