/ TEAMS · Specialist engineering · ScyllaDB / Cassandra
Source engineers experienced in Distributed databases, resilience and performance. for business-critical production systems, safe integrations and measurable technical ownership.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
partition key design
consistency levels
compaction strategies
repair operations
cluster topology
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Senior ScyllaDB / Cassandra Engineer
Inquire availability13+ years of experience · Lithuania
ScyllaDB / Cassandra Engineer with 13 years in production systems, focused on partition key design and consistency levels.
Languages: Lithuanian, English B2+
Senior ScyllaDB / Cassandra Engineer
Inquire availability8+ years of experience · Slovakia
ScyllaDB / Cassandra Engineer with 8 years in production systems, focused on consistency levels and compaction strategies.
Languages: Slovak, English B2+
Mid-level ScyllaDB / Cassandra Engineer
Available3+ years of experience · Croatia
ScyllaDB / Cassandra Engineer with 3 years in production systems, focused on compaction strategies and repair operations.
Languages: Croatian, English B2+
Mid+ ScyllaDB / Cassandra Engineer
Inquire availability7+ years of experience · Croatia
ScyllaDB / Cassandra Engineer with 7 years in production systems, focused on repair operations and cluster topology.
Languages: Croatian, English C1
/ 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 partition key design, consistency levels, compaction strategies helps define the engineering search.
/ Technical specializations
The right profile depends on your actual architecture, performance constraints, integration boundaries and operational responsibilities.
ScyllaDB / Cassandra responsibilities include partition key design, related consistency levels, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
ScyllaDB / Cassandra responsibilities include consistency levels, related compaction strategies, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
ScyllaDB / Cassandra responsibilities include compaction strategies, related repair operations, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
ScyllaDB / Cassandra responsibilities include repair operations, related cluster topology, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
ScyllaDB / Cassandra responsibilities include cluster topology, related p99 latency tuning, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
ScyllaDB / Cassandra responsibilities include p99 latency tuning, related partition key design, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
/ Project scenarios
Eliminate hot partitions in a distributed service. Define constraints around partition key design, map dependencies and test how the proposed implementation behaves under real operating conditions.
Plan a zero-downtime schema change. Define constraints around consistency levels, map dependencies and test how the proposed implementation behaves under real operating conditions.
Diagnose read-repair and tombstones. Define constraints around compaction strategies, map dependencies and test how the proposed implementation behaves under real operating conditions.
Stabilize multi-datacenter replication. Define constraints around repair operations, 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 partition key design and what evidence led to a fix.
Which decisions around consistency levels and compaction strategies were you personally accountable for?
Describe a production issue involving compaction strategies and what evidence led to a fix.
Which decisions around repair operations and cluster topology 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 partition key design. 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.
