Job Description Summary

Job Description

Leadership and Scope

·   Act as a technical leader for DevOps and software delivery, taking ownership of complex initiatives from problem definition , implementation, through adoption and measurable results.

·   Work across the Controls organization, not only with DevOps or individual developers, to understand needs, align priorities, and establish common approaches for build, test, release, environments, and support.

·   Set practical standards and reusable patterns, explain the reasoning behind them, and influence teams to adopt them while respecting product and project needs.

·   Use lean principles to identify waste, reduce handoffs and manual effort, remove bottlenecks, and lead continuous improvement based on data, feedback, and lessons learned.

·   Coach and mentor junior and mid-level engineers, manage supplier and contractors, create opportunities for knowledge sharing and raise the quality of engineering decisions across the team.

·   Contribute to technology strategy and roadmaps, evaluate options with clear cost, benefit, risk, and security considerations, and represent DevOps in cross-functional technical discussions.

Key Responsibilities

·   Lead the design, implementation, and continuous improvement of CI/CD pipelines for software build, test, packaging, and deployment across supported environments.

·   Develop automation and infrastructure-as-code solutions that are maintainable, secure, scalable, and usable by multiple Controls teams.

·   Guide the use of cloud, source control, artifact management, containers, and deployment tooling, including Azure, AWS, Git, Jenkins, JFrog Artifactory, Docker, Kubernetes, MATLAB, ToolboxST, and relevant internal tools.

·   Establish effective approaches for configuration management, branching, code review, release coordination, versioning, and concurrent development across products.

·   Partner with development teams across the Controls Subsystem and with systems, testing, architecture, and operations stakeholders to translate requirements into dependable delivery solutions.

·   Improve monitoring, logging, alerting, and operational dashboards so teams can detect issues early, understand root causes, and restore service quickly.

·   Lead resolution of complex build, integration, deployment, infrastructure, and environment problems, ensuring corrective actions address root causes rather than symptoms.

·   Support security, access management, secrets handling, compliance, and governance; promote least-privilege and secure-by-design practices.

·   Use AI-assisted engineering tools responsibly to improve productivity and analysis, while validating outputs and maintaining traceability, quality, security, and intellectual-property controls.

·   Capture and share lessons learned, define improvement measures, and communicate progress, risks, decisions, and outcomes to technical and non-technical stakeholders.

Desired Qualifications and SPB3 Expectations

Bachelor's degree in computer science, software engineering, electrical engineering, or a related discipline, or equivalent practical experience. Significant experience in DevOps, software engineering, cloud operations, infrastructure engineering, or a related field is expected.

·   Strong experience with CI/CD, Git-based development, automation scripting, cloud platforms, infrastructure as code, artifact repositories, and container-based delivery.

·   Working knowledge of monitoring, diagnostics, identity and access management, network security, REST APIs, and secure software delivery. Familiarity with PowerShell, Python, Bash, YAML, JSON, MATLAB, C++ or C# is beneficial.

·   Ability to explain technical topics clearly, facilitate decisions, manage stakeholders, and coordinate work across teams with different priorities.

·   Demonstrated progression beyond task execution: independently leads ambiguous, cross-team problems; mentors others; improves processes; and turns successful practices into standards that can be reused.

·   Ability to connect day-to-day engineering choices to product reliability, customer value, safety, security, schedule, and long-term Controls strategy.

What Success Looks Like

·   Controls teams use reliable, secure, and standardized delivery practices with less manual effort and fewer avoidable handoffs.

·   Cross-team improvements are adopted, measured, and sustained; bottlenecks and recurring issues are reduced through lean problem solving.

·   Complex delivery and environment issues are resolved quickly, with clear root-cause actions and improved observability.

·   Engineers are mentored, knowledge is shared, and teams collaborate effectively across DevOps, development, systems, testing, architecture, and operations.

·   The role is recognized as a trusted technical leader who can make sound decisions, influence beyond the immediate team, and shape the roadmap for Controls software delivery.

Additional Information