/ TEAMS · Specialist engineering · DevOps / Platform
Find DevOps specialists for CI/CD, infrastructure as code, Kubernetes and production reliability.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
Terraform infrastructure as code
Kubernetes deployments
GitOps delivery
CI/CD pipelines
observability SLOs
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Mid+ DevOps / Platform Engineer
Available6+ years of experience · Lithuania
DevOps / Platform Engineer with 6 years in production systems, focused on Terraform infrastructure as code and Kubernetes deployments.
Languages: Lithuanian, English B2+
Senior DevOps / Platform Engineer
Inquire availability7+ years of experience · Poland
DevOps / Platform Engineer with 7 years in production systems, focused on Kubernetes deployments and GitOps delivery.
Languages: Polish, English B2+
Senior DevOps / Platform Engineer
Available10+ years of experience · Bulgaria
DevOps / Platform Engineer with 10 years in production systems, focused on GitOps delivery and CI/CD pipelines.
Languages: Bulgarian, English C1
Mid-level DevOps / Platform Engineer
Available3+ years of experience · Bulgaria
DevOps / Platform Engineer with 3 years in production systems, focused on CI/CD pipelines and observability SLOs.
Languages: Bulgarian, English B2+
Find DevOps specialists for CI/CD, infrastructure as code, Kubernetes and production reliability.
Discuss your hiring requirement ↗We assess relevant production responsibilities, evidence of implementation work and technical discussions with your team. A list of tools alone is not proof of experience.
Under staff augmentation the client usually directs the backlog and reviews. Team leadership and project-delivery ownership must be agreed separately.
The profiles indicate sourcing options, not verified available individuals. Availability, start date and fees are confirmed for the actual request.
Assess infrastructure as code, CI/CD, observability, Kubernetes, access control and incident response in the context of the platforms you operate. Confirm production access, on-call expectations, security boundaries and ownership before engaging a specialist.
/ Engineering teams
Onectus uses its active engineering network and regional recruiting partners to search against concrete systems, environments and responsibilities. We evaluate practical experience rather than treating a framework mention or certification as proof of delivery. Particular availability and engagement terms are confirmed after an enquiry. For this role, practical knowledge of Terraform infrastructure as code, Kubernetes deployments, GitOps delivery helps define the engineering search.
/ Technical specializations
The right profile depends on your actual architecture, performance constraints, integration boundaries and operational responsibilities.
DevOps / Platform responsibilities include terraform infrastructure as code, related kubernetes deployments, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
DevOps / Platform responsibilities include kubernetes deployments, related gitops delivery, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
DevOps / Platform responsibilities include gitops delivery, related ci/cd pipelines, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
DevOps / Platform responsibilities include ci/cd pipelines, related observability slos, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
DevOps / Platform responsibilities include observability slos, related secrets management, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
DevOps / Platform responsibilities include secrets management, related terraform infrastructure as code, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
/ Project scenarios
Build auditable delivery pipelines. Define constraints around terraform infrastructure as code, map dependencies and test how the proposed implementation behaves under real operating conditions.
Standardize cloud infrastructure modules. Define constraints around kubernetes deployments, map dependencies and test how the proposed implementation behaves under real operating conditions.
Improve incident alert quality. Define constraints around gitops delivery, map dependencies and test how the proposed implementation behaves under real operating conditions.
Reduce deployment rollback risk. Define constraints around ci/cd pipelines, map dependencies and test how the proposed implementation behaves under real operating conditions.
/ Practical evaluation
A senior engineering interview should surface directly relevant implementation details, debugging history and operational judgment.
Describe a production issue involving Terraform infrastructure as code and what evidence led to a fix.
Which decisions around Kubernetes deployments and GitOps delivery were you personally accountable for?
Describe a production issue involving GitOps delivery and what evidence led to a fix.
Which decisions around CI/CD pipelines and observability SLOs were you personally accountable for?
/ Sourcing process
Define platform versions, deployment constraints, traffic patterns, required integrations and ownership.
Search the active network and partner channels for platform-specific engineering experience.
Discuss real systems, code or configuration decisions, troubleshooting and change control.
Confirm role boundaries, location or remote access, availability, security and interviews.
Profiles, availability and engagement terms are confirmed for each request.
/ Questions
Yes. Tell us the relevant versions, operational environment and the responsibilities connected to Terraform infrastructure as code. We qualify hands-on experience during each search.
These can be included when central to the project. We distinguish practical implementation work from general familiarity and ask about failure scenarios and testing.
We look at production decisions, trade-offs, incident diagnosis, code or infrastructure ownership and the ability to explain decisions without relying on a technology checklist.
Share your architecture, technical constraints, collaboration model and priorities. We can then discuss relevant sourcing channels, evaluation criteria and next steps.
/ Onectus · TEAMS
Tell us the technology, production responsibilities, experience level and working model. We'll activate the appropriate engineering sourcing channels.
