Compute
- What to examine
Nova services, scheduling, cells
- Evidence to request
Trace a request and diagnose capacity placement
Define Nova compute, Neutron networking, Cinder storage, Keystone identity, Glance images, automation, upgrades, and operations. Then compare every candidate with the same job-related scorecard and evidence standard.
Start with the role, evidence, and evaluation criteria.
By ConnectDevs · Last reviewed Aug 04, 2026
To hire OpenStack developers, first define the exact workload, architecture, ownership boundaries, and risks the person will inherit. Evaluate candidates against Nova compute, Neutron networking, Cinder storage, Keystone identity, Glance images, automation, upgrades, and operations, using a consistent work sample and anchored scorecard instead of treating a technology keyword as proof of production ability.
Name the services and operating responsibilities the role owns. OpenStack application integration, service development, cloud architecture, and production operations require different evidence and should not be collapsed into one generic cloud profile.
The core work of the role, before tools and titles. Check that your brief, your interviews, and your scorecard all cover it.
Operate and extend OpenStack private clouds
Manage compute, networking, and storage services
Automate deployments and upgrades
Troubleshoot capacity and performance issues
Group requirements by area so the job post, the interview plan, and the scorecard test the same things.
Nova, Neutron, Cinder, Keystone, and Glance.
KVM, Open vSwitch, and storage backends.
Kolla-Ansible or similar deployment tools.
Most OpenStack Developers lean toward one of these. Name the one you need in the brief instead of listing every tool.
Running OpenStack day to day.
NFV workloads.
Moving to public cloud or Kubernetes.
Adjust weights to the workload, then define observable evidence for each rating before sourcing begins.
Nova services, scheduling, cells
Trace a request and diagnose capacity placement
Neutron topology and failure paths
Debug connectivity across the intended backend
Cinder services and backends
Explain attachment, availability, and recovery
Identity, upgrades, automation, telemetry
Plan a controlled change and rollback
Name the services and operating responsibilities the role owns. OpenStack application integration, service development, cloud architecture, and production operations require different evidence and should not be collapsed into one generic cloud profile.
The role brief should name the production environment, team interfaces, first ninety-day outcomes, and who owns incidents, security review, migrations, and technical decisions.
Choose four to six competencies and assign weights from the real job.
Define strong, mixed, and insufficient behavioral anchors for each competency.
Create a bounded exercise that tests compute and networking.
Ask every candidate the same core questions and document supporting evidence.
Review conflicting scores, missing evidence, and decision overrides before selection.
These are risks a weak hire in this role tends to bring. Turn each into a work-sample task or follow-up question that produces evidence for or against it, and score every candidate on the same set.
Can they trace a silent Nova instance boot failure across Keystone, the RabbitMQ message bus, and Nova-compute logs using Request ID correlation?
Have they architected Neutron networking to prevent the centralized L3 agent from becoming a single-point-of-failure bottleneck?
Can they execute a split-brain recovery on a distributed Ceph storage cluster serving both Cinder volumes and Glance images?
A starting draft built from this guide. Replace the bracketed parts, cut anything that does not apply, and keep every requirement tied to the work.
[Two or three sentences on the product, the team, and why this role is open now.]
A structured interview and a short work sample, scored against the same criteria for every candidate.
OpenStack clouds need dedicated operators, so full-time hiring is common. A contractor fits an upgrade or migration. Linux and networking depth matter most.
Direct answers for role scope, technical assessment, adjacent roles, and compensation research.
A useful job description names the product or platform, current architecture, ownership boundaries, first ninety-day outcomes, and operational responsibilities. For OpenStack developers, explicitly cover Nova compute, Neutron networking, Cinder storage, Keystone identity, Glance images, automation, upgrades, and operations. Separate essential evidence from preferences, and identify which decisions the hire owns independently versus which require specialist or team review.
Prioritize capabilities tied to the live workload rather than a long keyword list. The scorecard should cover Nova services, scheduling, cells, Neutron topology and failure paths, Cinder services and backends, and Identity, upgrades, automation, telemetry. Weight each area according to business risk, then define observable strong, mixed, and insufficient evidence before candidate interviews begin.
Use a short work sample based on a sanitized version of the real job, followed by a structured discussion of choices and tradeoffs. Ask every candidate the same core questions. Score the submitted artifact, reasoning, verification, failure handling, security, and communication separately, then record evidence before making an overall recommendation.
Name the services and operating responsibilities the role owns. OpenStack application integration, service development, cloud architecture, and production operations require different evidence and should not be collapsed into one generic cloud profile. Make that distinction explicit in the title, scorecard, sourcing criteria, and interview plan before sourcing begins.
Cost depends on location, employment model, seniority, domain, scope, and the market date. Use current local compensation sources and recent comparable roles, document every assumption, and show a dated range rather than a universal average. Add platform or recruiting fees separately so hiring teams can compare total cost consistently.
Planning this hire?
Book a DemoConnectDevs can support discovery and structured interview workflows, but the hiring team remains responsible for the role definition, evidence standard, final decision, compensation validation, and applicable legal review.