Nexcess
Platform Engineer (Compute Solutions)
- Compensation
- Not disclosed
- Location
- Lemesos, Cyprus
- Work setup
- Not specified
- Seniority
- Not specified
- Employment
- Not specified
- Experience
- 5+ years
- Category
- Devops
- Posted
Skills
Must have
- 5+ years of experience working with cloud computing infrastructure and production environments.
- 5+ years of experience with Linux server administration.
- 5+ years of experience with configuration management and automation tools such as Ansible or Puppet.
- 5+ years of experience with KVM administration and virtualization environments.
- Strong understanding of compute infrastructure, virtualization, networking, storage, and production operations.
- Experience building, operating, and supporting highly available production infrastructure.
- Experience automating infrastructure configuration and operational processes.
- Experience participating in an on-call rotation and responding to production incidents.
- Ability to troubleshoot complex issues across multiple infrastructure layers.
- Ability to work effectively in unfamiliar or legacy environments and make safe, incremental improvements.
- Hands-on experience with AI-assisted engineering tools as part of day-to-day technical work.
- Clear written communication skills and the ability to work effectively in a remote, distributed team across multiple time zones.
Nice to have
- Experience with VPS, dedicated cloud, bare metal, or hosting infrastructure.
- Experience with storage systems used in virtualized or cloud environments.
- Experience in managed hosting, cloud platforms, or another high-availability service environment.
- Experience with infrastructure automation at scale.
- Experience reviewing infrastructure changes and mentoring other engineers.
Full description
Compute Solutions builds and operates the VPS, Cloud Dedicated, storage, and bare metal products our customers run their cloud infrastructure on.
You will own infrastructure changes end to end: the specification, the automation and configuration, the validation, and how they behave in production.
The pull request is the visible part. The job is the machine behind it: turning a loosely worded need into something precise enough to build against, naming what can break before it does, proving the change is correct rather than asserting it, and staying with it once it is live.
How we work
- Business alignment and focus come first. Engineering here exists to move the business, not to be busy. You will know which few things matter most this month and why, say so when the work in front of you is not one of them, and land what you committed to on dates the business can plan around, at a quality that does not come back as an incident or a customer escalation. Predictable, reliable delivery of quality software is the output of this job, and everything below is in service of it.
- This job gets more hands-on every quarter, not less. The volume of code goes up while the time you spend typing it goes down, so the value moves to the two ends of it: what you specify, and what you verify. You will stay close to production, run the AI harness daily, read code you did not write, and keep your technical judgment current rather than remembered.
- Whoever ships it owns it, regardless of what wrote it. Most code is AI-generated now, so the judgment moved to either side of it: specifying exactly what to build, and verifying that what came back is correct, secure and operable. An agent wrote it is not a defense. Your name is on the merge.
- You do not need to own the roadmap to know why the work matters. You will not be the Product counterpart at this level and you are not expected to be. You are expected to understand what the customer gets and what the business gains from the thing you are building, and to ask before you build the wrong thing correctly. The engineers who move fastest here are the ones who ask that question early rather than at the review.
- You go on call for what you build, and you take your turn on the rotation. Engineering declares risk and timelines in writing for the business to accept, and that includes yours: when a date is at risk you say so early, with evidence, rather than quietly.
Responsibilities
- Own infrastructure features end to end within the Compute Solutions domain. Take work from specification through implementation, testing, deployment, monitoring, and ongoing production support across VPS, Cloud Dedicated, storage, and bare metal services.
- Build and maintain cloud compute infrastructure. Work with Linux-based systems, virtualization platforms, configuration management, and supporting infrastructure to deliver reliable and scalable compute services.