/ TEAMS · Specialist engineering · Slurm / HPC
Source engineers experienced in Scheduling, batch compute and high-performance cluster operations. for business-critical production systems, safe integrations and measurable technical ownership.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
Slurm job scheduling
partition policies
GRES GPU allocation
cgroup constraints
MPI integration
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Mid+ Slurm / HPC Engineer
Inquire availability7+ years of experience · Serbia
Slurm / HPC Engineer with 7 years in production systems, focused on Slurm job scheduling and partition policies.
Languages: Serbian, English C1
Senior Slurm / HPC Engineer
Inquire availability11+ years of experience · Romania
Slurm / HPC Engineer with 11 years in production systems, focused on partition policies and GRES GPU allocation.
Languages: Romanian, English B2+
Senior Slurm / HPC Engineer
Available14+ years of experience · Romania
Slurm / HPC Engineer with 14 years in production systems, focused on GRES GPU allocation and cgroup constraints.
Languages: Romanian, English B2+
Mid-level Slurm / HPC Engineer
Inquire availability3+ years of experience · Czechia
Slurm / HPC Engineer with 3 years in production systems, focused on cgroup constraints and MPI integration.
Languages: Czech, English B2+
/ 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 Slurm job scheduling, partition policies, GRES GPU allocation helps define the engineering search.
/ Technical specializations
The right profile depends on your actual architecture, performance constraints, integration boundaries and operational responsibilities.
Slurm / HPC responsibilities include slurm job scheduling, related partition policies, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Slurm / HPC responsibilities include partition policies, related gres gpu allocation, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Slurm / HPC responsibilities include gres gpu allocation, related cgroup constraints, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Slurm / HPC responsibilities include cgroup constraints, related mpi integration, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Slurm / HPC responsibilities include mpi integration, related accounting and fairshare, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Slurm / HPC responsibilities include accounting and fairshare, related slurm job scheduling, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
/ Project scenarios
Reduce queued GPU job backlog. Define constraints around slurm job scheduling, map dependencies and test how the proposed implementation behaves under real operating conditions.
Build fair tenant resource policies. Define constraints around partition policies, map dependencies and test how the proposed implementation behaves under real operating conditions.
Investigate failed distributed jobs. Define constraints around gres gpu allocation, map dependencies and test how the proposed implementation behaves under real operating conditions.
Improve cluster utilization monitoring. Define constraints around cgroup constraints, 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 Slurm job scheduling and what evidence led to a fix.
Which decisions around partition policies and GRES GPU allocation were you personally accountable for?
Describe a production issue involving GRES GPU allocation and what evidence led to a fix.
Which decisions around cgroup constraints and MPI integration 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 Slurm job scheduling. 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.
