Senior DevOps Engineer

Role Summary
 

As Senior DeveOps at CAMP, you will own secure, scalable, and automated software delivery across products—and mature this function into a practice. You will set and enforce standards for pipelines, deployments, cloud operations, and security by default; hire and coach engineers; define capability maps and career paths; guide budgets and guardrails; and partner with product and platform leaders to continually improve speed, reliability, and audit readiness. You will be responsible for practice-building initiative and lead the effort to implement it.
 

Our platform commonly uses TeamCity for continuous integration, Octopus Deploy for continuous delivery, Bitbucket for Git workflows, Amazon Web Services for cloud, and security platforms such as Veracode, UpGuard, and Invicti—these are representative tools; experience with equivalent platforms is welcome.
 

What You Will Do
 

·         Lead and grow the team, define roles and rotations, build a skills matrix, and run enablement, certifications, and outcome-based reviews.
 

·         Architect and standardize reusable pipeline templates and quality gates so builds and releases are fast, observable, and auditable.
 

·         Make sure cross-team influence comes through by convening design and release reviews, driving alignment across engineering groups, reducing friction points, and landing decisions that scale.
 

·         Define and uphold Git workflows—branch protection, merge policies, and review service-level agreements—aligned to a predictable release cadence.
 

·         Design and operate secure deployments on Amazon Web Services across compute, containers, networking, identity and access management, and infrastructure as code, with availability, scalability, cost efficiency, and disaster recovery in mind.
 

·         Integrate application and dependency scanning into pipelines using a platform such as Veracode; include dynamic application security testing using a platform such as Invicti; close findings quickly with developer feedback loops.
 

·         Monitor external attack surface and third-party risk with a platform such as UpGuard; drive remediation to closure; publish posture trends to stakeholders.
 

·         Make monitoring, logging, alerting, incident response, and post-incident reviews part of “done,” and continually reduce mean time to recovery and change failure rate.
 

·         Run a recurring disaster-recovery test cadence with clear pass/fail criteria and track corrective actions to completion.
 

·         Publish and maintain DevSecOps standards for naming, tagging, environment strategy, change control, and access; keep Confluence audit-ready and Jira the source of delivery truth.
 

·         Enforce safe data refresh for lower environments (masking and anonymization) and secrets hygiene across all stages.
 

·         Provide concise dashboards for cloud cost, build minutes, artifacts, and environment footprint; set budgets and guardrails; deliver quarterly efficiency gains.
 

·         Convene design and release reviews that align diverse engineering groups on paved-road approaches, reduce friction points, and land decisions that scale.
 

·         Communicate status, risks, and decisions early and clearly, offering options with trade-offs and a recommended path forward.
 

·         Track and improve delivery, reliability, and security outcomes—lead time, deployment frequency, change-failure rate, mean time to recovery, time-to-remediate application security findings, and a minimum external posture rating.
 

Requirements

Technical Skills – Must Have
 

·         Hands-on expertise with a continuous integration system (for example, TeamCity) and a continuous delivery system (for example, Octopus Deploy), including reusable templates and quality gates.
 

·         Proficiency with modern Git workflows (for example, Bitbucket), including branching strategy, protection rules, and code-owner boundaries.
 

·         Strong background in Amazon Web Services application delivery (compute, containers, networking, identity and access management) and infrastructure as code (for example, CloudFormation or Terraform).
 

·         Experience integrating code and dependency scanning into pipelines using a commercial or open-source platform (for example, Veracode) with policy enforcement and developer remediation loops.
 

·         Experience operating external attack-surface and vendor-risk monitoring with a platform such as UpGuard, with documented remediation and governance.
 

·         Experience running dynamic application security testing with a platform such as Invicti and incorporating results into release gates.
 

·         Security fundamentals: secrets management, least-privilege access, dependency and image scanning, baseline hardening.
 

·         Scripting and automation (for example, Python, Bash, or PowerShell) for pipelines, environment management, diagnostics, and reporting.
 

·         Containerization fundamentals (Docker and Kubernetes) and image policy management.
 

Technical Skills – Good to Have
 

·         Observability stacks (for example, CloudWatch, Prometheus, Elasticsearch/Logstash/Kibana, Datadog) and cost monitoring.
 

·         Experience in compliance-sensitive environments and change-management processes.
 

·         Policy-as-code, software bill of materials workflows, and supply-chain hardening (signing and provenance).
 

·         Multi-account landing zones and migration experience on Amazon Web Services.
 

Qualifications
 

·         Bachelor’s or Master’s degree in Computer Science, Engineering, or related field (or equivalent experience).
 

·         Ten or more years in DevOps, DevSecOps, or Site Reliability Engineering with ownership of cross-functional delivery initiatives.
 

·         Proven leadership scaling teams and practices—hiring, coaching, standards, budgeting, and governance.
 

·         Demonstrated success improving delivery, reliability, and security metrics and driving predictable releases.
 

·         Excellent stakeholder management and communication; crisp decision logs and status updates.
 

·         Willingness to participate in and lead on-call and incident-commander rotations.
 

 
 

How We Work
 

·         Agile cadence and regular releases; rollout, rollback, and verification are part of “done.”
 

·         Toolchain signals a modern environment, but equivalency is fine—we value capabilities and outcomes over specific brand names.
 

·         Culture: outcome-focused, ownership-driven, proactive communication, and “no-surprises” execution.