Encuentra tu próxima oportunidad

Busca ofertas por puesto, competencia y ubicación. Revisa los requisitos antes de preparar tu candidatura.

Una buena búsqueda no termina al encontrar un título atractivo. Compara las tareas, los requisitos y las condiciones de cada oferta con tu experiencia. Esta guía te ayuda a crear una lista de oportunidades, preparar documentos relevantes y comprobar dónde enviar cada candidatura.

La interfaz está en español. Los títulos y las descripciones de las empresas se mantienen en el idioma original de publicación, que puede ser inglés.

Borrar filtros

Resultados: 8549

← Volver a los resultados

Platform Engineer (remote work)

CloudLinux

Trabajo remoto

Ubicación
Remote (Worldwide)
Publicado
8 oct 2026

Confirma que la oferta sigue abierta y revisa sus condiciones en el sitio web de la empresa antes de solicitar el puesto.

Descripción del puesto

La interfaz está en español. Los títulos y las descripciones de las empresas se mantienen en el idioma original de publicación, que puede ser inglés.

CloudLinux builds Linux infrastructure and security products. You will join our Automation & Management Services cell, working closely with Dmitrii Petrov to solve problems across teams and services: cloud-cost data, infrastructure inventory, network policies and capacity workflows. Check out our website for more information https://cloudlinux.com/ Inside the Infrastructure Department, the Platform cell is a small team. We run the observability platform, the company's GitLab and the CI runners behind it, a few smaller engineering services, and the automation the department relies on for provisioning and configuration. We are looking for a Platform Engineer for the PaaS team to take ownership of an agreed set of platform services: keep them reliable and within agreed service levels, make changes and recovery repeatable, and reduce recurring operational work through automation and self-service. You get real freedom in how you implement things, and you own the result: you pick the approach, defend it in review, and answer for how the service behaves afterwards. Most of the job is what site reliability engineering is about: services that run well day after day, and requests from product teams handled properly. Some of it is building. The observability platform and the runner cluster were both built from scratch within the last year, and there will be more of that. Expect the work to split between platform engineering, incident response, and helping engineers in other teams use what we run. What you'll do Run the observability platform. Keep it healthy, onboard teams, watch cost and capacity, and maintain the alerting that runs on top of it. Run GitLab and the CI runner fleet. Upgrades, capacity, access, backups and restore drills. Keep the rest of our services healthy, with the monitoring and runbooks a production service needs. Deploy new services when they are requested. Research the options, pick a design, and stand the service up from scratch according to good practice: as code, monitored, backed up, documented. Work with developers' requests. Access, onboarding, pipeline problems, new exporters and dashboards. Answer them, and turn the recurring ones into self-service. Run incidents. Diagnose and mitigate impact, restore service safely, then complete the root-cause analysis and post-mortem. Deliver the prevention or detection improvements the incident calls for. Ship everything as code, reviewed in merge requests. Plan and check before every change. Write for engineers outside the team. Runbooks, onboarding guides, maintenance notices and status updates that people can act on. Work with AI agents. Delegate collection and drafting to them, review their output as you would a colleague's merge request, and record what you learn where the team can find it. Requirements Must have: Senior-level experience in infrastructure, platform or site reliability engineering, including at least one production service you were responsible for keeping up. We will ask you to walk us through it in detail: what broke, how you found out, and what you changed so it would not happen again. Linux systems administration and debugging on bare metal and virtual machines. Much of our infrastructure is not Kubernetes. Kubernetes in production delivered through GitOps, including cluster upgrades you performed yourself. Infrastructure as code as your delivery form: Ansible and Terraform or OpenTofu, changes reviewed in merge requests. GitLab administration and GitLab CI in production, self-hosted or SaaS. Deep experience with another CI system is acceptable if you can show the same depth. Working knowledge of the Prometheus and Grafana ecosystem: you have run it for a team, written alert rules and dashboards, and can read PromQL. Depth here is welcome, and learnable. Written technical explanation for engineers outside your team: runbooks, notices, answers to requests. Strong communication and interpersonal skills. This role deals with people at least as much as with servers: most work starts as a conversation with a product team, and you need to understand what they actually need, agree scope, priority and timing with them, push back politely when a request should not be done as asked, and keep everyone informed while the work is in progress. We are looking for someone other teams enjoy working with. Advanced use of AI engineering assistants such as Claude and Codex: providing context, breaking down tasks, designing agent loops, and delegating plans for unattended, end-to-end execution within defined scope and permissions, with clear stop conditions. You can explain, debug and test the resulting automation, and verify generated commands, scripts and conclusions before they touch production. English - upper-intermediate or higher - to ensure clear communication of progress within the teams. Nice to have: Alerting design: SLOs, burn-rate alerts, thresholds sized from data. MicroVM isolation for CI: Kata Containers, Firecracker or gVisor. S3-compatible object storage operations: Ceph RGW or similar. AWS with real cost work. Self-hosted Sentry, or another Kafka, ClickHouse and Redis-backed application you have kept alive under load. Python or Go for exporters and small internal services. You do not need to have run every system on this list. Solid fundamentals and the judgment to pick up an unfamiliar service, make it observable and hand back a runbook matter more than matching every line. What this role is not focused on: Not a ticket-queue operator. Recurring requests get turned into self-service, not processed one by one forever. Not a pure cloud or Kubernetes role. Bare metal and virtual machines are a large part of our infrastructure. Not the DBA, the network engineer or the security engineer. Those teams run their own systems; we provide the platform they monitor them with. Benefits What's in it for you? A focus on professional development. Interesting and challenging projects. Fully remote work with flexible working hours, which allows you to schedule your day and work from any location worldwide. Paid 24 days of vacation per year, 10 days of national holidays, and unlimited sick leaves. Compensation for private medical insurance. Co-working and gym/sports reimbursement. Budget for education. The opportunity to receive a reward for the most innovative idea that the company can patent. By applying for this position, you consent to the processing of your personal data as described in our Privacy Policy (https://cloudlinux.com/candidate-privacy-notice), which provides detailed information on how we maintain and handle your data.

Busca, compara y prepara tu candidatura

Empieza con un puesto o una competencia que quieras utilizar. Ajusta los filtros de ubicación y profesión y abre las ofertas para comparar sus responsabilidades. Si no encuentras resultados, prueba un término más corto o elimina un filtro cada vez.

Distingue los requisitos imprescindibles de las preferencias. Comprueba la jornada, la retribución y la ubicación cuando se indiquen. Un puesto remoto puede exigir residencia en un país, autorización para trabajar o coincidencia horaria. Confirma la oferta y las condiciones completas con la empresa.

Elige ejemplos reales de tu experiencia que respondan a los requisitos del puesto. Explica tu aportación y utiliza cifras solo cuando puedas justificarlas. Sigue las instrucciones de la empresa y revisa los datos de contacto, el contenido y el PDF antes de enviar la candidatura.

Antes de enviar tu candidatura

Preguntas sobre la búsqueda de empleo

¿Por qué algunas ofertas están en inglés?

Las empresas publican sus propios títulos y descripciones. Conservamos ese texto para no alterar requisitos o condiciones. La navegación y esta guía están en español. Si una búsqueda en español no encuentra ofertas, prueba también el título o la competencia en el idioma del anuncio, por ejemplo «software engineer».

¿Un puesto remoto permite trabajar desde cualquier país?

No necesariamente. La empresa puede limitar los países de residencia, exigir autorización para trabajar o fijar un horario. Comprueba estos puntos en la oferta original. Si no aparecen, consúltalos con la empresa antes de asumir que puedes trabajar desde tu ubicación.

¿Qué hago si no aparecen resultados?

Prueba un título más general o una sola competencia y elimina los filtros de uno en uno. Los nombres de los puestos varían entre empresas. Si una oferta concreta ha desaparecido, busca su referencia en la página de empleo de la empresa; ampliar los filtros no recupera una vacante cerrada.

¿La candidatura se envía desde ResumizeAI?

El botón de solicitud abre un destino externo. Sigue las instrucciones de la empresa o del proveedor de selección y confirma allí el envío. Preparar un currículum en ResumizeAI no equivale a presentar una candidatura. Si el enlace solo abre la web de la empresa, busca la vacante antes de continuar.

¿Cómo adapto el currículum y la carta de presentación?

Relaciona los requisitos con proyectos, tareas y resultados que puedas explicar. Destaca lo relevante sin inventar experiencia ni copiar competencias que no tienes. En la carta, explica tu interés y aporta un ejemplo concreto. Respeta el idioma y el formato pedidos y revisa ambos documentos antes de enviarlos.