次の仕事の機会を見つけましょう

職種、スキル、勤務地で求人を検索できます。応募書類を準備する前に募集要件を確認しましょう。

魅力的な職種名を見つけることは、仕事探しの出発点です。業務内容、応募条件、働き方を自分の経験と照らし合わせましょう。このガイドでは、候補の絞り込み、応募書類の準備、提出先の確認を順番に進めるためのポイントを紹介します。

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

条件をクリア

検索結果: 14,302

← 検索結果に戻る

Staff Engineer, Imunify360 (remote work)

CloudLinux

リモート勤務

勤務地
Remote (Worldwide)
掲載日
2026年10月19日

応募する前に、企業のウェブサイトで現在も募集中かどうかと詳しい条件を確認してください。

仕事内容

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

CloudLinux is a global remote-first company. We are driven by our principles: do the right thing, employees first, we are remote first, and we deliver high-volume, low-cost Linux infrastructure and security products that help companies to increase the efficiency of their operations. Every person on our team supports each other and does what we can to ensure we all are successful. Check out our website for more information: cloudlinux.com We are currently hiring Staff Engineers for various projects within the Imunify360 product. Imunify360 is CloudLinux's multi-layer security suite for Linux web servers: antivirus and malware cleanup, WAF, IDS/IPS, Proactive Defense, patch management (KernelCare/Patchman), and IP/domain reputation. It runs on hundreds of thousands of shared, VPS and dedicated hosting servers, under cPanel, Plesk, DirectAdmin and standalone. The engineering org is 60+ engineers in squads covering backend, core, server agent, malware research, WAF/WebShield, and Patchman. Core services are Python; agents and performance-critical paths are Go and Rust. We run on Hetzner and our own bare metal. Check out our website for more information: https://imunify360.com/ Role Mission & Scope Most complex technical challenges in Imunify360 go beyond individual squads. A single detection change can impact the scanner, agent, UI, reputation backend, and release process. While squad leads own delivery within their teams, the Staff Engineer ensures technical alignment across the product. As a Staff Engineer, you'll be a hands-on technical leader working across the entire product, focusing on the most critical and high-impact challenges as priorities evolve. You'll drive technical decisions, improve architecture, establish engineering standards, and help teams build sustainable solutions. This is an individual contributor role, without direct people management responsibilities. You'll remain actively involved in development, spending approximately 30–50% of your time writing production code, rather than focusing solely on architectural design. While deep expertise in a particular area is valued, this role requires the flexibility to work across different components, collaborate with multiple squads, and tackle challenges wherever your expertise can make the greatest impact. What you will own Architecture and technical direction Own the end-to-end architecture of Imunify360 as a product: agent ↔ server ↔ cloud backends, data flows, and the contracts between them. Write and drive ADRs and RFCs for cross-squad changes. Run the Wed/Fri architecture sync together with the Technical Director. Keep a living tech-debt and risk register (security / compliance / uptime) with owners and dates, and get the top items funded on the roadmap. Hard cross-cutting problems (examples of what lands on your desk) Agent resource footprint on dense shared hosts: CPU, memory and I/O budgets for scanning, file monitoring (inotify/fanotify) and WAF, measured on real kernels, not benchmarks from elsewhere. Detection pipeline quality: false positive / false negative rates, signature and ML model rollout with staged gates and rollback. Upgrade and release safety across a large, heterogeneous fleet (CentOS/AlmaLinux/CloudLinux/Ubuntu, multiple control panels, old kernels). Backend scale and cost of reputation, ThreatIntel and telemetry services. Migrating hot paths from Python to Go/Rust where the data shows it pays off, and saying no where it doesn't. Engineering standards Set the bar for design reviews, code review, testing strategy, observability (Prometheus/Grafana/Sentry) and secure SDLC (OWASP ASVS, CIS Benchmarks as relevant). Lead or co-lead SEV1/SEV2 incidents when the cause is unclear or cross-squad; make sure the blameless post-mortem ships within 24 h and its actions get closed. Drive the AI-augmented SDLC in practice: show what good agentic coding looks like (prompt specificity, context provision, review quality, tool boundaries) on real changes, not slides. People multiplier (no direct reports) Mentor senior engineers and squad leads toward staff-level scope. Act as the technical bar-raiser in hiring loops for senior and lead roles. Be the engineering voice in product and sales discussions: estimates, feasibility, and no dated customer commitment without a written squad-lead estimate. Key Milestones 30 days: Shipped at least one non-trivial change to production. Can explain the full request path from agent to backend. Has a personal list of top 10 technical risks. 90 days: Owns one cross-squad initiative with an approved ADR, a measured baseline, and a staged rollout plan. Published risk register reviewed in arch sync. 6 months: That initiative is in production with before/after metrics. At least one engineering standard (e.g. release gating, agent perf budget, design review template) is adopted by 3+ squads. 12 months: Recognized by squad leads as the default escalation point for cross-cutting technical decisions. At least one senior engineer grown into broader scope with your mentorship. Requirements Must have 10+ years building and operating production software, with 3+ years in a Staff/Principal/Tech Lead scope spanning several teams. Strong production experience in Python and at least one of Go or Rust . Deep Linux internals : processes, filesystems, networking, kernel interfaces (inotify/fanotify, eBPF or similar), packaging (RPM/DEB), systemd. Track record of designing and running distributed systems at scale: async backends, queues, databases, caching, failure modes. You have owned systems that run on customer machines (agents, daemons, on-prem software) and know what upgrade safety, backward compatibility and resource budgets mean there. Security mindset: threat modeling, secure coding, handling of untrusted input (files, HTTP traffic, user content). Writes clear, short technical documents and drives decisions in async, remote teams across time zones. Uses AI coding tools (Cursor, Claude, MCP-based tooling) daily and can judge their output critically. Nice to have Experience in server security: AV/malware detection, WAF (ModSecurity/Coraza), IDS/IPS, rootkit detection, CVE/patch management. Experience with WordPress and Node.JS web application hosting at scale ML in production for classification/detection, including evaluation and safe model rollout. Observability at scale: Prometheus, Grafana, Sentry, ClickHouse or similar. CI/CD ownership: GitLab CI, Jenkins, build systems for multi-distro packaging. Open-source contributions in security or systems tooling. Benefits What's in it for you? Stay hands-on technically while owning complex, high-impact engineering work. Work on challenging Linux, automation, and cybersecurity problems across mature and newer products. Influence technical direction and make meaningful architectural decisions. Work independently with a high level of ownership and autonomy. Fully remote work with flexible working hours. 24 paid vacation days, 10 national holidays, and unlimited sick leave. Private medical insurance compensation. Co-working and gym/sports reimbursement. Education budget. Opportunity to receive a reward for innovative ideas 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で応募書類を作成しただけでは応募は送信されません。リンク先が企業のトップページの場合は、該当する募集を探してから手続きを進めましょう。

応募書類とカバーレターはどう調整すればよいですか?

募集要件と、自分が説明できるプロジェクト、業務、成果を結び付けます。経験していない技術や実績を加えず、関連する経験を分かりやすく示してください。カバーレターでは応募理由を具体例とともに伝えます。指定された言語とファイル形式に従い、送信前に両方の書類を確認しましょう。