寻找你的下一个职业机会

按职位、技能和地点搜索招聘信息。准备申请前,先仔细了解职位要求。

找到一个吸引人的职位名称只是求职的起点。请将工作职责、招聘要求和工作条件与你的实际经历进行比较。本指南帮助你筛选机会、准备有针对性的申请材料,并确认每份申请应该在哪里提交。

此界面为简体中文。雇主发布的职位名称和描述保留原文,可能为英文。

清除筛选

搜索结果: 8,549

← 返回搜索结果

Platform Engineer (remote work)

CloudLinux

远程工作

地点
Remote (Worldwide)
发布日期
2026年10月8日

申请前,请在雇主网站确认职位仍在招聘,并检查完整要求和条件。

职位描述

此界面为简体中文。雇主发布的职位名称和描述保留原文,可能为英文。

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.

查找职位、比较要求,再准备申请

从你希望从事的职位或运用的技能开始搜索。调整地点和职业筛选,打开职位比较工作职责。如果没有结果,可以使用更短的关键词,或逐一移除筛选条件。

区分必备要求和优先条件,检查已列出的工作安排、薪资和地点。远程职位也可能要求特定居住国家、工作许可或工作时间重合。请向雇主确认职位信息和完整条件。

选择能够回应职位要求的真实经历,说明你的贡献,只使用能够证实的数字。遵循雇主的申请说明,并在提交前检查联系方式、文档内容和 PDF。

提交申请前的检查清单

求职常见问题

为什么有些职位使用英文?

职位名称和描述由招聘企业撰写。为避免改变招聘要求或工作条件,我们保留原文。操作界面和本指南使用简体中文。如果中文搜索没有结果,可以尝试使用职位发布语言中的名称或技能,例如“software engineer”。搜索词不会自动翻译,界面语言也不代表企业要求的申请语言。

远程职位是否允许从任何国家工作?

不一定。企业可能对居住国家、工作许可或工作时段有要求。请查看原始招聘页面中的具体条件。如果未说明,应先向企业确认,再判断能否从你所在的地区工作。“远程”标签本身并不代表没有地点限制。

搜索没有结果时应该怎么办?

尝试更通用的职位名称或单个技能,并逐一移除筛选条件。不同企业可能用不同名称描述相似工作。如果某个职位已经消失,请在企业招聘页面搜索其职位编号。扩大搜索范围不会让已经关闭的职位重新开放。

申请会通过 ResumizeAI 直接提交吗?

申请按钮会打开外部网站。请按照企业或招聘服务的说明,在该网站完成并确认提交。在 ResumizeAI 中准备简历并不等于已经申请职位。如果链接只打开企业网站,请先找到对应职位,再继续申请流程。

如何针对职位调整简历和求职信?

将招聘要求与能够解释清楚的项目、任务和成果联系起来。突出相关经历,不要添加未经实际掌握的技能或虚构成绩。在求职信中用具体例子说明申请动机,并遵守企业要求的语言和文件格式。提交前检查两份文件,确保内容准确、联系方式正确、链接可用。