DevOps / SRE Engineer | Wilkes & Liberty

The role

Wilkes & Liberty needs a DevOps / SRE Engineer who treats the release path and production behavior as part of the product. You will make changes repeatable, failures visible, recovery testable, and day-to-day operation sustainable for the client team that inherits the system.

This role is distinct from Infrastructure / Platform Engineer. Infrastructure owns the environment — compute, network, and platform substrate. You own how software moves through that environment and how it behaves in production.

What you will own

Design and maintain CI/CD for the engagement's applications and services so builds, tests, and promotions are repeatable.
Define release, rollback, and promotion paths that match the engagement's risk posture.
Set service objectives and instrument systems with actionable telemetry — metrics, logs, traces, and alerts operators can act on.
Verify recovery through restore, rollback, and failover paths that have been exercised, not only described.
Monitor dependency health and reduce toil in the delivery and operations path.
Harden operational controls, including secrets handling, least privilege in pipelines, and change evidence.
Define support, escalation, and recovery boundaries that match the contracted service.
Partner with Infrastructure / Platform on environment boundaries without absorbing infrastructure ownership.
Support forward-deployed work when embedded reliability is part of delivery.

What you bring

You have owned CI/CD and production reliability for real systems, not only one-off deploy scripts.
You design observability and recovery that operators can use under pressure.
You work across application and platform boundaries with engineering teams.
You write clear operational documentation and treat reliability as delivery design.
You prefer concrete pipeline and incident evidence over tool-name lists.

Helpful experience

Containerized delivery, GitHub Actions or comparable pipelines, and common observability stacks used as estate examples rather than fixed requirements.
CMS/web platform estates such as Drupal and Next.js.
Regulated or federal-adjacent environments where change control and evidence matter.
Service-level objectives, dependency monitoring, and toil reduction programs.

Equal opportunity and accommodations. Wilkes & Liberty considers qualified candidates without regard to protected characteristics. Reasonable accommodations are available during the application process.

The role

What you will own

Design and maintain CI/CD for the engagement's applications and services so builds, tests, and promotions are repeatable.

Define release, rollback, and promotion paths that match the engagement's risk posture.

Set service objectives and instrument systems with actionable telemetry — metrics, logs, traces, and alerts operators can act on.

Verify recovery through restore, rollback, and failover paths that have been exercised, not only described.

Monitor dependency health and reduce toil in the delivery and operations path.

Harden operational controls, including secrets handling, least privilege in pipelines, and change evidence.

Define support, escalation, and recovery boundaries that match the contracted service.

Partner with Infrastructure / Platform on environment boundaries without absorbing infrastructure ownership.

Support forward-deployed work when embedded reliability is part of delivery.

What you bring

You have owned CI/CD and production reliability for real systems, not only one-off deploy scripts.

You design observability and recovery that operators can use under pressure.

You work across application and platform boundaries with engineering teams.

You write clear operational documentation and treat reliability as delivery design.

You prefer concrete pipeline and incident evidence over tool-name lists.

Helpful experience

Containerized delivery, GitHub Actions or comparable pipelines, and common observability stacks used as estate examples rather than fixed requirements.

CMS/web platform estates such as Drupal and Next.js.

Regulated or federal-adjacent environments where change control and evidence matter.

Service-level objectives, dependency monitoring, and toil reduction programs.