Platform Engineer

Our platforms run where our clients decide: on-premises, in a private cloud or air-gapped, inside their own boundary. They are built to work without a public service in their decision path, and some sites take installation and updates only from signed offline media. That makes the platform part of the product: how we build, package, sign and ship matters as much as what the software does.

You will own that path from commit to installed release: the pipelines that build and test every change, the packaging for each deployment model, the hardening that ships by default, and the environments where we prove a release before a client sees it. You will work with the engineers who write the products and the delivery teams who install them, and turn every problem found in the field into an automated check.

What you will do

• Build and maintain CI/CD pipelines that produce versioned, reproducible and signed releases, with tests, dependency scanning and software bills of materials as gates that can stop a release.
• Package Rhinexa Niyantran, Rhinexa NMS and Rhinexa Sentinel for on-premises, private cloud and air-gapped installation, including signed offline update media.
• Keep build, staging and demonstration environments defined as code and reproducible from scratch.
• Ship hardening by default: least privilege, each service under its own restricted account, encrypted internal communication, and secrets kept out of images and logs.
• Build the health checks, monitoring and runbooks that tell us and our clients whether a deployment is healthy.
• Support installations and upgrades in client environments with our delivery teams, and turn each field issue into a check in the pipeline.

What you bring

• Strong Linux administration and troubleshooting: services, networking, storage, permissions and hardening.
• Production experience with containers (Docker and Compose), and working knowledge of Kubernetes or a comparable orchestrator.
• Experience building CI/CD pipelines and release processes, not only using them.
• Automation in Python and Bash, and infrastructure as code with a tool such as Ansible or Terraform.
• Solid networking fundamentals: TLS and certificates, DNS, reverse proxies and firewalls.
• A security-first habit: you assume a default will be left as shipped, so you ship it safe.

Useful, not essential

• Air-gapped or offline delivery: installation media, offline package mirrors and update bundles.
• Software supply chain security: software bills of materials, artefact and image signing, vulnerability scanning.
• GPU servers and locally hosted AI models, where regulated data must stay inside the client's boundary.
• Identity integration with OpenID Connect or SAML, and observability with Prometheus, Grafana or OpenTelemetry.