DevOpsEngineering

What we do

We take over the work your senior developers do reluctantly at six in the evening: pipelines, automation, environments, monitoring. The result is a product team that ships, and a delivery infrastructure that someone actually owns.

• CI/CD pipelines: automated build, test and release on GitLab CI, GitHub Actions or Jenkins.
• GitOps and infrastructure as code: declarative, reproducible, versioned environments.
• Observability: metrics, logs and alerts that tell you what is happening before a customer does.
• Toil automation: everything done by hand today, and not tomorrow.
• Incident readiness: runbooks, post-mortems, operational hygiene.

How an Overlay engineer works

Inside your tools and your rituals: standup in the morning, pull requests and reviews during the day, documentation where you keep it. CET time zone, working languages French and English. Distance is not a separate process: it is one more desk on your team.

Every engineer has passed a technical screening with seniors, a hands-on test on real scenarios and training on your stack before day one.

When it makes sense

• A DevOps role that has been open for weeks and nobody manages to close.
• Delivery slows down because seniors do operations instead of product.
• The word “deploy” raises anxiety in the office.