/ TEAMS · Ceph Engineering
Need Ceph expertise for a live storage cluster? Define the release, RADOS/OSD topology, CRUSH placement, MON/MGR health, recovery and capacity limits before starting a specialist search.
2,000+ active engineers · Regional recruiting network
/ Ceph Storage
Technical layers to scope an accurate Ceph engineering brief.
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Senior Ceph Engineer
Available13+ years of experience · Czechia
Ceph Engineer with 13 years in production systems, focused on Ceph RADOS and OSD and RBD and CRUSH.
Languages: Czech, English B2+
Senior Ceph Engineer
Inquire availability8+ years of experience · Lithuania
Ceph Engineer with 8 years in production systems, focused on RBD and CRUSH and Linux storage.
Languages: Lithuanian, English B2+
Mid-level Ceph Engineer
Inquire availability3+ years of experience · Poland
Ceph Engineer with 3 years in production systems, focused on Linux storage and Ceph RADOS and OSD.
Languages: Polish, English B2+
Mid+ Ceph Engineer
Available5+ years of experience · Bulgaria
Ceph Engineer with 5 years in production systems, focused on Ceph RADOS and OSD and RBD and CRUSH.
Languages: Bulgarian, English B2+
/ Specialist sourcing
Need Ceph expertise for a live storage cluster? Define the release, RADOS/OSD topology, CRUSH placement, MON/MGR health, recovery and capacity limits before starting a specialist search.
Assess a real incident involving slow recovery, degraded placement groups or OSD failures. Ask how the engineer diagnosed risk and kept client I/O available.
Role-specific sourcing, not a promise of current candidate availability.
/ A relevant sourcing result
One recent Ceph engineering requirement was matched with a suitable specialist within approximately one month. That experience informs how we approach infrastructure searches: understand the actual system, activate the right sourcing channels and assess operational depth before presenting a candidate.
A past sourcing example, not a fixed recruitment lead-time commitment.
/ Where Ceph expertise applies
Ceph intersects Linux operations, cluster design, networking and the workloads above storage. The role specification should reflect the components and failure scenarios the engineer will actually manage.
Cluster health, OSD lifecycle, data placement, recovery, capacity planning and the operational impact of rebalancing.
Block storage for virtual machines and private clouds, provisioning, snapshots, performance and operational integration.
Metadata servers, client behavior, availability, storage access patterns and file-system operations.
S3-compatible object gateways, multi-site considerations, identity, bucket lifecycle and application-facing integrations.
cephadm/orchestration, monitoring, release planning, maintenance windows and safe change procedures.
Hardware layout, NVMe/HDD economics, network topology, latency, replication and observable storage performance.
/ Project situations
Plan architecture, failure domains, capacity, hardware assumptions and a staged rollout.
Review cluster health, recovery behavior, alerting, operational runbooks and upgrade readiness.
Align RBD/Cinder, Kubernetes storage, virtual-machine workloads and access permissions.
Investigate latency, OSD contention, network constraints, placement and workload behavior.
/ Technical qualification
A Ceph CV is only a starting point. Candidate discussions are structured around real duties, operational decisions and the surrounding technology.
Which cluster sizes, storage types, workloads and uptime expectations has the engineer actually supported?
How do they reason about degraded placement groups, OSD loss, rebalancing and maintenance safety?
Do they know when RBD, CephFS and RGW differ, and how clients, network and storage interact?
What is their hands-on experience with Linux, cephadm, observability, upgrades, automation and incident response?
/ Engagement
A Ceph engineer can join your existing storage team, partner with OpenStack and Linux engineers, or support a defined infrastructure initiative. We align the role, working hours, communication and technical selection process with your delivery model.
Ceph version, cluster footprint, RBD/RGW/CephFS usage, bare-metal or cloud integrations, technical ownership.
We search relevant engineers in our active talent pool and engage regional recruiters and focused sourcing channels.
Review hands-on experience, interview candidates against your technical context and coordinate the client selection.
Align availability, contract model, onboarding, access and collaboration.
/ Questions
Yes. Describe your Ceph storage services and OpenStack integration points—such as Cinder, Nova or Glance—so we can prioritize engineers whose experience spans both environments.
Yes. Include server and drive configuration, network topology, operating system, performance requirements and any on-site access expectations in the technical brief.
A previous Ceph search produced a suitable match in approximately one month. For a new request, the timeline depends on the stack, region, seniority, interview process and engineer availability.
Yes. We can source complementary Linux, OpenStack, networking, Kubernetes and platform engineers as individual contributors or as a coordinated team.
/ Onectus · TEAMS
We will align the right recruitment channels and technical evaluation to the infrastructure you are operating.
