Director, DevOps Engineering

M3 (  ) is a leading provider of hospitality-specific software solutions, delivering cloud-based tools for hotel accounting, financial reporting, labor management, payroll, and business intelligence. Built by hoteliers for hoteliers, M3 empowers hotel owners, operators, and management companies to streamline back-office operations, reduce costs, gain real-time insights, and drive portfolio performance across thousands of properties in North America and beyond.

• Supervises all roles assigned to the Dev Ops Engineering department, personally or through subordinate leads, including recruiting, training and development, performance management, motivation, corrective action, or termination in conjunction with HR if necessary.
• Owns the architecture, design, and continuous maturity of the organization’s CI/CD pipelines end-to-end, standardizing pipeline tooling and patterns (e.g., Git Hub Actions, Git Lab CI, Jenkins) across engineering teams to enable fast, reliable, and repeatable software delivery.
• Leads adoption of Dev Sec Ops  practices by embedding automated security checks directly into CI/CD pipelines, including static application security testing (SAST), dynamic application security testing (DAST), software composition analysis (SCA)/dependency scanning, container and image scanning, secrets detection, and infrastructure-as-code policy checks.
• Partners with the security team to define pipeline gating criteria, vulnerability severity thresholds, and remediation SLAs; implements policy-as-code in the pipeline to enforce security and compliance requirements defined by the Cloud Infrastructure Director and Security at build and deploy time.
• Designs, builds, and operates ephemeralam environment infrastructure that provisions on-demand, short-lived environments per branch or pull request, enabling engineers to validate changes under production-like conditions without manual environment requests.
• Owns automation for the ephemeralam environment lifecycle, including provisioning, data seeding and masking, teardown, and cost controls to prevent unused environments from accumulating spend, operating within capacity guardrails established by the Cloud Infrastructure Director and consulting that role before changes likely to materially shift baseline Azure spend.
• Owns release management for the organization, including release cadence and calendaring, versioning strategy, release train coordination across engineering teams, and change approval gates for production releases.
• Defines and leads the organization’s deployment strategy, implementing progressive delivery patterns such as Blue/Green and Canary deployments, automated rollback, and metrics-based promotion criteria to reduce release risk.
• Evaluates and introduces deployment and progressive-delivery tooling (e.g., Argo Rollouts, Flagger, service mesh or load-balancer-based traffic shifting, feature-flag platforms) to support safe, incremental rollout of changes.
• Owns workload-level orchestration and deployment routing within Kubernetes clusters; consults the Cloud Infrastructure Director on any change affecting cluster-level networking, ingress, or the underlying load balancer/VNet.
• Maintains infrastructure-as-code and automation practices in support of pipeline, environment, and deployment tooling, conforming to IaC standards and module conventions set by the Cloud Infrastructure Director rather than maintaining a separate convention, and escalating pipeline-specific needs into that standard.
• Establishes KPIs for pipeline reliability, deployment frequency, change failure rate, and mean time to recovery (DORA metrics); drives continuous improvement through metrics, feedback loops, and formal retrospectives for release- and deployment-caused incidents, following the same RCA/AAR rigor used for infrastructure incidents.
• Participates in joint incident triage with the Cloud Infrastructure Director per the shared decision tree, with both Directors paged simultaneously on production degradation; co-authors joint RCA/AAR, reviewed by the VP, for any incident where both release and infrastructure signals were present.
• Builds, leads, and mentors a…