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

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

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

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

条件をクリア

検索結果: 14,302

← 検索結果に戻る

Staff Security 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 a Staff Security Engineer within the Imunify360 product. Imunify360 is CloudLinux's security suite for Linux web servers. It protects hundreds of thousands of hosting servers and the websites running on them, so it sees most large-scale web attacks early — often in the first hours. Check out our website for more information: https://imunify360.com/ Role Mission & Scope At Imunify360, protecting customers from evolving cyber threats requires close collaboration between security research, engineering, and other teams. Responding to complex attack campaigns involves more than identifying threats — it requires understanding attack techniques, developing effective detection and mitigation strategies, and ensuring customers are protected. As a Staff Security Engineer, you'll take end-to-end technical ownership of complex security challenges, from initial threat discovery and analysis to detection, mitigation, and post-incident review. This is a hands-on technical leadership role focused on practical security engineering rather than SOC monitoring, compliance, or purely theoretical research. You'll analyze malware and exploit code, develop detection and mitigation tools, anticipate emerging attack techniques, and ensure security findings translate into production-ready detections, mitigations, and fixes. You'll work closely with engineering, security research, support, external partners, and the broader security community to coordinate responses and drive continuous improvements in our security capabilities. As an individual contributor, you won't have direct reports or people management responsibilities. All security research and testing are conducted within authorized boundaries, with clearly defined scope and responsible disclosure practices. Your mission is to strengthen Imunify360's ability to detect, prevent, and respond to emerging threats, delivering measurable security improvements that protect customers at scale. What you will own Malware and campaign mitigation Lead response to large-scale exploitation and malware campaigns: triage, root cause, and mitigation across every protection layer of the product. Reverse-engineer malware and exploits targeting Linux servers and web applications. Track campaigns over time, not just individual samples: cluster indicators, connect activity to known actors and toolkits, anticipate the next variant. Define and run measurable outcomes per campaign: time to detect, time to protect, cleanup effectiveness, reinfection rate. Security response coordination Own the security incident and response process, both for threats against our customers and for vulnerabilities in our own product: severity model, runbooks, communication, escalation. Coordinate with external parties — software vendors, partners, CERTs/CSIRTs, abuse desks, other security vendors. Drive responsible disclosure where we find vulnerabilities. Be the technical voice in security advisories and partner briefings, together with Product and Support. Triage external vulnerability reports. Offensive security on our own product Red-team our product and infrastructure. Assume a capable attacker who already has a foothold. Threat-model new features before they ship; own the security review gate for high-risk changes. Turn findings into fixes with the owning teams, not just reports. Detection engineering and tooling Raise the quality bar of detections: false-positive budgets, test corpora, staged rollout with measurement gates and fast rollback. Build and automate the analysis pipeline: dynamic analysis, honeypots, telemetry-driven hunting, ML-assisted triage where it measurably helps. Write production code for these tools; expect 30–50% of your time to be hands-on building. Turn telemetry into intelligence: emerging exploits, attacker infrastructure, trends — shared as internal briefs and selected public research. People multiplier (no direct reports) Mentor analysts and engineers; raise the security skill level across teams. Bar-raiser in security hiring loops. Key Milestones 30 days: Analyzed real threats end-to-end. Mapped the current response flow and where it breaks. Shipped at least one detection or mitigation to production. 90 days: Security response process and severity model published and agreed. Led at least one real campaign response with a written post-mortem. Baseline response metrics in place. 6 months: Time from first sighting to protection measurably reduced vs. baseline. First red-team review completed, top findings fixed. Working relationships with key external partners. 12 months: Recognized internally and externally as the owner of security response. Public research or disclosures published. Teams can run a standard campaign response without you. Requirements Must have 10+ years in security engineering, malware research, incident response, or offensive security, with several years leading cross-team work at Staff/Principal/Lead scope. Deep hands-on malware analysis and reverse engineering skills. Strong web application security and practical exploitation experience. Deep Linux knowledge from both the attacker's and the defender's side. Proven incident response leadership on large-scale events: you have run the response, written the advisory, and closed the post-mortem. Production coding in Python plus a systems language (Go, Rust or C). Experience with coordinated vulnerability disclosure and working with the security community. Clear, short writing for both engineers and non-technical stakeholders; works well async across time zones. Daily user of AI tools for analysis and coding, with critical judgment about their output. Nice to have Background in hosting or large web ecosystems. Detection authoring at scale (signatures, WAF/IDS rules). Kernel-level monitoring and rootkit detection. Threat intelligence practice and actor tracking. ML for malware classification. Public track record: CVEs, published research, talks, CTFs, open-source security tools. Relevant certifications are a plus, not a requirement. 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で応募書類を作成しただけでは応募は送信されません。リンク先が企業のトップページの場合は、該当する募集を探してから手続きを進めましょう。

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

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