DevOps Engineer

About the role We need a DevOps engineer to own and extend CI/CD and platform delivery for CDX and LogIT. You will maintain Jenkins Multibranch and Deployments pipelines, a shared Groovy library, Nexus publishing/promote flows, and config/app deploy paths onto Mule hosts (and related AWS where assigned). You partner with Mule developers daily, but the core of the role is pipeline correctness, environment promotion, and operational reliability —not primary API feature development. What you’ll do Own Jenkins Multibranch and Deployments jobs (CDX, Log-IT folders): branch indexing, job definitions from devops-tools, and health of automated triggers Maintain the shared library (devops-functions / jenkins-shared): checkout helpers, deploy triggers, Nexus publish steps, SSH/host sync, notifications Operate config deploy for cdx-configs (dev / logit/dev → DEV / LOGIT_DEV), including Multibranch filters, mule-config-checkout, and host rsync/restart behavior Support app and domain deploy pipelines: Nexus snapshots/releases → host hot-deploy (mule-app-*-deploy, domain/policy jobs); debug failed builds and parameter/env mismatches Build and improve promote workflows (e.g. partner/docker/raw Nexus promote, DRY_RUN vs live) Manage credentials and access patterns for Jenkins/Nexus/Bitbucket (no secrets in git); help provision Jenkins users and deploy credentials as needed Collaborate on AWS / infra adjacent work as required (EKS/LogIT runtime context, Terraform for shared services such as Nexus/Jenkins hosts—depth depends on assignment) Use Bitbucket (SSH remotes, PRs, default reviewers) and Jira (CPD) for change tracking; keep runbooks and pipeline maps current Troubleshoot across agent logs, Publish-over-SSH, systemd/Mule restarts, and post-deploy verification Required qualifications 3+ years (mid) / 5+ years (senior) in DevOps / platform engineering with production CI/CD ownership Strong Jenkins experience: Pipeline-as-code, Multibranch, shared libraries (Groovy), parameterized Deployments-style jobs Solid Git / Bitbucket (or GitHub) workflows and PR-based delivery Hands-on with artifact repositories (Nexus or Artifactory): publish, promote, snapshots vs releases Comfortable with Linux , SSH, systemd services, and reading detailed job/console logs Clear written communication for runbooks, Jira, and PR descriptions in a regulated/federal-adjacent setting Nice to have MuleSoft / Java Maven build familiarity (enough to support app teams, not necessarily primary Mule developer) AWS (EC2, EKS, IAM, SSO/profiles), Terraform Helm / Kubernetes deploy experience (LogIT Cosmos / partner Helm path) Teams/Slack notifications from pipelines FedRAMP / DoD or similar compliance-aware change practice Success in the first 90 days Reliably operating CDX + LogIT deploy paths and explaining them to app engineers Shipping at least one durable pipeline/library improvement (e.g. Multibranch indexing for logit/dev config auto-deploy, promote job hardening, docs/runbooks) Independently diagnosing and unblocking failed Multibranch or mule-config-checkout / app-deploy builds How we work Small team: DevOps partners tightly with Mule app engineers Tooling: Jenkins, Bitbucket, Nexus, Jira (CPD), shared Groovy library, environment-specific Mule EC2 hosts Prefer automated, reviewed pipeline changes over one-off host edits