The Mission
Grip operates at the intersection of enterprise content operations and advanced automation. As our platform footprint expands across global enterprise clients, infrastructure reliability, deployment velocity, and system observability are no longer support functions — they are strategic enablers.
The MidDevOps Engineer ensures our cloud infrastructure scales predictably, deploys consistently, and operates securely across Azure and AWS. This role exists to reduce manual operations, strengthen platform resilience, and turn infrastructure into a programmable, repeatable system.
You are not maintaining servers. You are building the foundation that allows engineering to ship faster, safer, and at enterprise scale.
Requirements
What You Will Do
Own and Evolve CI/CD Infrastructure
Design, implement, and maintain scalable CI/CD pipelines across GitLab CI, GitHub Actions, and Azure DevOps.
Improve deployment velocity while increasing reliability and rollback safety.
Standardize pipeline-as-code practices to eliminate manual configuration drift.
Partner with engineering teams to reduce build failures and deployment bottlenecks.
Measure and optimize DORA metrics (deployment frequency, lead time, MTTR, change failure rate).
Manage Multi-Cloud Infrastructure as Code
Build and maintain Azure and AWS infrastructure using Pulumi.
Ensure infrastructure is version-controlled, reproducible, and environment-consistent.
Optimize compute, storage, networking, and security configurations for performance and cost efficiency.
Contribute to infrastructure modernization initiatives as platform scale increases.
Implement automated cost-monitoring and capacity planning mechanisms.
Strengthen Kubernetes & Container Operations
Support Kubernetes cluster management, scaling strategies, and workload optimization.
Improve container orchestration patterns, resource allocation, and deployment strategies.
Standardize Docker image best practices and runtime security configurations.
Improve cluster reliability and automate failover strategies.
Contribute to automation of environment provisioning and cluster lifecycle management.
Elevate Monitoring, Observability & Incident Response
Maintain and improve Kubernetes dashboards, and system health metrics.
Enhance observability using Prometheus, Grafana, and ELK where applicable.
Reduce mean time to detection and resolution through proactive monitoring design.
Participate in incident response and contribute to root cause analysis.
Implement post-incident improvement actions and preventive automation.
Embed DevSecOps and Operational Discipline
Integrate secrets management, vulnerability scanning, and compliance checks into CI/CD pipelines.
Strengthen infrastructure security posture across environments.
Apply least-privilege access models and secure configuration baselines.
Contribute to DevOps best practices documentation and internal enablement.
Support hiring processes and participate in technical interviews.
Who You Are
You are a hands-on infrastructure engineer who builds systems instead of manual processes. You think in automation first, consistency always. You are comfortable owning problems from detection to resolution and improving the system afterward.
You Have:
3–5 years of DevOps or cloud engineering experience in production environments.
Proven experience with Azure and AWS (compute, networking, storage, IAM, cost optimization).
Solid hands-on experience with Pulumi for multi-cloud infrastructure as code.
Strong working knowledge of Docker, Kubernetes, and orchestration patterns.
Experience with CI/CD platforms such as GitLab CI, GitHub Actions, or Azure DevOps.
Exposure to monitoring stacks such as Prometheus/Grafana, or ELK.
Practical experience with scripting in Python, Bash, and YAML.
Working understanding of DevSecOps principles, secrets management, and vulnerability scanning.
You Think:
In systems, not tickets.
Automation over repetition.
Reliability as a product feature.
Prevention before firefighting.
Infrastructure decisions in terms of scalability and cost trade-offs.
Your Skills Are:
Translating infrastructure requirements into reproducible code.
Diagnosing distributed system failures under pressure.
Communicating clearly with developers, QA, and integration teams.
Balancing delivery speed with operational stability.
Contributing meaningfully in technical reviews and architectural discussions.
Why Join Grip?
The Enterprise Inflection Point.
Grip is operating at enterprise scale where infrastructure decisions directly impact global client operations. Your work will support high-volume, automated content systems used by some of the world’s largest brands.
The Platform Leverage.
You are building the underlying systems that power automation across the organization. Every reliability improvement, every pipeline optimization, and every security enhancement compounds across all engineering teams.
The Technical Maturity Curve.
Grip is actively evolving its infrastructure stack. You will contribute to modernization initiatives, multi-cloud optimization, and operational scalability — positioning you for growth toward Senior DevOps ownership.
The Ownership Culture.
Engineers at Grip are trusted to solve problems end-to-end. If you identify a systemic weakness, you are expected to fix it — not escalate it indefinitely.
The procedure
If you’re ready to bring your project management powers to a role where you can make a difference, we want to hear from you. Send your resume and portfolio in English via the link provided. If you have questions, contact our Recruitment Department at [email protected].
Grip handles and uses personal data of job applicants in line with its
Originally posted on