DevOps Technical Delivery Manager

About Us:

BW Design Group is a fully integrated architecture, engineering, construction, system integration, and consulting firm committed to helping our clients realize their most critical goals from Strategy to Commercialization. As the only firm born from a manufacturing technology company to become an independent and fully integrated firm, we combine deep domain expertise in the manufacturing environment with an approach that is built to serve the dynamic needs of our clients. Rooted in our distinct culture of Truly Human Leadership, we cultivate the leaders who will define tomorrow and partner with our clients in the food & beverage, life sciences, industrial, and advanced technology industries to build the future of manufacturing and technology.

Barry-Wehmiller is a diversified global supplier of engineering consulting and manufacturing technology for the packaging, corrugating, sheeting and paper-converting industries. By blending people-centric leadership with disciplined operational strategies and purpose-driven growth, Barry-Wehmiller has become a $3 billion organization with nearly 12,000 team members united by a common belief: to use the power of business to build a better world.

Job Description:

Who You’ll Work With

You will join one of our 45 offices in the US, be part of a committed team of over 1500 professionals, and work in teams and directly with our clients doing work that is shaping the world around us. You will be welcomed into a rapidly growing business and team and empowered to make an impact. You will be valued, cared for, and challenged on your path to becoming a world-class professional consultant and surrounded by leaders who are committed to creating an environment that enables you to realize your own success and fulfillment.

As a DevOps Technical Delivery Manager for the Information Solutions team you will own delivery accountability for DevOps and platform engineering work across the firm’s client engagements. Acts as the single point of accountability for DevOps delivery commitments between clients, project teams, and the DevOps Engineering team, translating project and client needs into sequenced, achievable work and holding the team’s delivery commitments to scope, schedule, budget, and quality. Engineers retain direct technical dialogue with their client counterparts; this role owns the commercial scope, sequencing, and schedule commitments arising from that dialogue. Owns intake, prioritization, and delivery cadence for the DevOps backlog, and is the person Project Managers, Engineering Managers, and clients go to for a clear and predictable answer on platform work. This role has no direct reports; performance management and career development for DevOps engineers are owned by the DevOps Engineering Manager. Success is measured by client outcomes, on-time and on-scope delivery, and the throughput and predictability of the DevOps team.

What You’ll Do

• Serve as the primary client-facing point of accountability for DevOps and platform delivery across engagements

• Lead client and stakeholder conversations on platform scope, sequencing, dependencies, risk, and delivery expectations

• Translate client business and operational requirements into clear, sequenced DevOps delivery plans

• Set and manage delivery expectations proactively; communicate schedule and scope changes before they become escalations

• Run delivery status reviews, readiness checkpoints, and go-live coordination with client IT, OT, and operations stakeholders

• Negotiate and sequence platform work around client change-control constraints, including restricted deployment windows, change freezes, and the approvals required before any production system is restarted, and reflect those constraints in delivery commitments

• Own resolution of delivery escalations, coordinating the right technical resources and closing the loop with the client

• Represent the DevOps team at project kickoff, design review, commissioning, and startup milestones

• Build and maintain trusted relationships with client technical and business stakeholders that support account retention and growth

• Coordinate hand-off to Day-2 operations, whether retained by the client, delivered by the firm, or delivered through an external operations partner, with the operating model agreed before go-live rather than at it

• Act as the single point of intake for the DevOps team for all incoming project requests, capacity questions, technical escalations, and scope discussions

• Own intake, triage, and prioritization of the DevOps backlog, balancing project deadlines, client priorities, technical risk, and team capacity

• Insulate the team from one-off pulls and protect focus time for committed work

• Run the team’s delivery cadence (fourteen-day sprints with planning, stand-ups, reviews, and retrospectives), maintained on the team’s GitHub project board with per-issue sprint, size, and client attribution, without overhead creep

• Maintain visibility into each engineer’s current load and commitments; flag overload, idle capacity, and blocked work early

• Track and report delivery metrics, including throughput, cycle time, commitment reliability, escaped defects, and client satisfaction

• Partner with Project Managers and Engineering Managers across the firm to integrate DevOps scope into broader project plans and report progress consistently

• Surface prioritization conflicts and trade-offs that require a decision above this role to the DevOps Engineering Manager and the Practice Co‑Leads

• Continuously improve how the team delivers: intake templates, backlog hygiene, estimation practice, runbook quality, hand-off documentation, on-call coverage, and sprint metrics

• Partner with the DevOps Engineering Manager on capacity forecasting and on the staffing implications of the forward pipeline

• Support business development through scoping, estimating, and proposal input for DevOps and platform work

• Own change order identification and the commercial impact of scope adjustments on DevOps work

• Track engagement financial health for DevOps scope, including hours consumed against budget, burn rate, and margin risk

• Maintain sufficient technical depth in Kubernetes, CI/CD, infrastructure-as-code, containerized industrial platforms, and the on-premises infrastructure this team operates (bare-metal clusters, distributed storage, and site networking) to challenge estimates, assess delivery risk, and hold credible client conversations without escalation

• Partner with the Principal DevOps Engineer on architecture decisions that affect delivery feasibility, sequencing, and cost

• Act as a positive role model of the firm’s culture and the Guiding Principles of Leadership

• Other duties as assigned.

• Billable Hour Target expectations will be provided by Leader during the on-boarding process.

What You’ll Bring

• Serve as the primary client-facing point of accountability for DevOps and platform delivery across engagements

• Lead client and stakeholder conversations on platform scope, sequencing, dependencies, risk, and delivery expectations

• Translate client business and operational requirements into clear, sequenced DevOps delivery plans

• Set and manage delivery expectations proactively; communicate schedule and scope changes before they become escalations

• Run delivery status reviews, readiness checkpoints, and go‑live coordination with client IT, OT, and operations stakeholders

• Negotiate and sequence platform work around client change‑control constraints, including restricted deployment windows, change freezes, and the approvals required before any production system is restarted, and reflect those constraints in delivery commitments

• Own resolution of delivery escalations, coordinating the right technical resources and closing the loop with the client

• Represent the DevOps team at project kickoff, design review, commissioning, and startup milestones

• Build and maintain trusted relationships with client technical and business stakeholders that support account retention and growth

• Coordinate hand‑off to Day‑2 operations, whether retained by the client, delivered by the firm, or delivered through an external operations partner, with the operating model agreed before go‑live rather than at it

• Act as the single point of intake for the DevOps team for all incoming project requests, capacity questions, technical escalations, and scope discussions

• Own intake, triage, and prioritization of the DevOps backlog, balancing project deadlines, client priorities, technical risk, and team capacity

• Insulate the team from one‑off pulls and protect focus time for committed work

• Run the team’s delivery cadence (fourteen‑day sprints with planning, stand‑ups, reviews, and retrospectives), maintained on the team’s GitHub project board with per‑issue sprint, size, and client attribution, without overhead creep

• Maintain visibility into each engineer’s current load and commitments; flag overload, idle capacity, and blocked work early

• Track and report delivery metrics, including throughput, cycle time, commitment reliability, escaped defects, and client satisfaction

• Partner with Project Managers and Engineering Managers across the firm to integrate DevOps scope into broader project plans and report progress consistently

• Surface prioritization conflicts and trade‑offs that require a decision above this role to the DevOps Engineering Manager and the Practice Co‑Leads

• Continuously improve how the team delivers: intake templates, backlog hygiene, estimation practice, runbook quality, hand‑off documentation, on‑call coverage, and sprint metrics

• Partner with the DevOps Engineering Manager on capacity forecasting and on the staffing implications of the forward pipeline

• Support business development through scoping, estimating, and proposal input for DevOps and platform work

• Own change order identification and the commercial impact of scope adjustments on DevOps work

• Track engagement financial health for DevOps scope, including hours consumed against budget, burn rate, and margin risk

• Maintain sufficient technical depth in Kubernetes, CI/CD, infrastructure‑as‑code, containerized industrial platforms, and the on‑premises infrastructure this team operates (bare‑metal clusters, distributed storage, and site networking) to challenge estimates, assess delivery risk, and hold credible client conversations without escalation

• Partner with the Principal DevOps Engineer on architecture decisions that affect delivery feasibility, sequencing, and cost

• Act as a positive role model of the firm’s culture and the Guiding Principles of Leadership

• Serve as the primary client-facing point of accountability for DevOps and platform delivery across engagements

• Lead client and stakeholder conversations on platform scope, sequencing, dependencies, risk, and delivery expectations

• Translate client business and operational requirements into clear, sequenced DevOps delivery plans

• Set and manage delivery expectations proactively; communicate schedule and scope changes before they become escalations

• Run delivery status reviews, readiness checkpoints, and go‑live coordination with client IT, OT, and operations stakeholders

• Negotiate and sequence platform work around client change‑control constraints, including restricted deployment windows, change freezes, and the approvals required before any production system is restarted, and reflect those constraints in delivery commitments

• Own resolution of delivery escalations, coordinating the right technical resources and closing the loop with the client

• Represent the DevOps team at project kickoff, design review, commissioning, and startup milestones

• Build and maintain trusted relationships with client technical and business stakeholders that support account retention and growth

• Coordinate hand‑off to Day‑2 operations, whether retained by the client, delivered by the firm, or delivered through an external operations partner, with the operating model agreed before go‑live rather than at it

• Act as the single point of intake for the DevOps team for all incoming project requests, capacity questions, technical escalations, and scope discussions

• Own intake, triage, and prioritization of the DevOps backlog, balancing project deadlines, client priorities, technical risk, and team capacity

• Insulate the team from one‑off pulls and protect focus time for committed work

• Run the team’s delivery cadence (fourteen‑day sprints with planning, stand‑ups, reviews, and retrospectives), maintained on the team’s GitHub project board with per‑issue sprint, size, and client attribution, without overhead creep

• Maintain visibility into each engineer’s current load and commitments; flag overload, idle capacity, and blocked work early

• Track and report delivery metrics, including throughput, cycle time, commitment reliability, escaped defects, and client satisfaction

• Partner with Project Managers and Engineering Managers across the firm to integrate DevOps scope into broader project plans and report progress consistently

• Surface prioritization conflicts and trade‑offs that require a decision above this role to the DevOps Engineering Manager and the Practice Co‑Leads

• Continuously improve how the team delivers: intake templates, backlog hygiene, estimation practice, runbook quality, hand‑off documentation, on‑call coverage, and sprint metrics

• Partner with the DevOps Engineering Manager on capacity forecasting and on the staffing implications of the forward pipeline

• Support business development through scoping, estimating, and proposal input for DevOps and platform work

• Own change order identification and the commercial impact of scope adjustments on DevOps work

• Track engagement financial health for DevOps scope, including hours consumed against budget, burn rate, and margin risk

• Maintain sufficient technical depth in Kubernetes, CI/CD, infrastructure‑as‑code, containerized industrial platforms, and the on‑premises infrastructure this team operates (bare‑metal clusters, distributed storage, and site networking) to challenge estimates, assess delivery risk, and hold credible client conversations without escalation

• Partner with the Principal DevOps Engineer on architecture decisions that affect delivery feasibility, sequencing, and cost

• Act as a positive role model of the firm’s culture and the Guiding Principles of Leadership

• Bachelor’s degree in Computer Science, Software Engineering, Engineering, or a related technical field, or equivalent combination of education, training, and professional experience.

• Minimum of 8 years of professional experience in technical delivery, platform engineering, DevOps, or engineering project leadership.

• Minimum of 3 years owning delivery accountability for a technical team, as a delivery manager, technical program manager, scrum master, or equivalent.

The approximate pay range for this position is $140k-$170k. Please note that the pay range provided is a good faith estimate for the position at the time of posting. Final compensation may vary based on factors including but not limited to background, knowledge, skills, and abilities as well as geographic location of the pos_ition_.

#LI-CG1

At Barry-Wehmiller we recognize that people come with a wealth of experience and talent beyond just the technical requirements of a job. If your experience is close to what you see listed here, please still consider applying. We know that our differences often can bring about innovation, excellence and meaningful work—therefore, people from all backgrounds are encouraged to apply to our positions. Please let us know if you require reasonable accommodations during the interview process.

Barry-Wehmiller is an equal opportunity employer. M/F/D/V This organization uses E-Verify.

Applicants may be subject to pre-employment screening which may include drug screening, reference checks, employment verifications, background screening and/or skills assessments.

Company:

Design Group