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.
