A complete application in a minute
Tailored resume and cover letter, ready to send.
CloudLinux Inc. ищет ведущего инженера для руководства архитектурой Imunify360 — комплексной защиты Linux-серверов. Вы будете отвечать за архитектуру агентов, серверов и облачных бекендов, вести ADRs/RFCs и синхронизацию с Technical Director.
Требуется 10+ лет разработки, глубокие знания Linux и опыт работы с распределёнными системами. Удалённая работа, гибкий график, международная команда.
CloudLinux develops high-volume, low-cost Linux infrastructure and security products that help companies improve operational efficiency. Imunify360 is its multi-layer security suite for Linux web servers, providing antivirus and malware cleanup, WAF, IDS/IPS, proactive defense, patch management, and IP/domain reputation services. It runs on hundreds of thousands of shared, VPS, and dedicated hosting servers.
Own Imunify360's end-to-end product architecture, including agents, servers, cloud backends, data flows, and contracts Write and drive ADRs and RFCs for cross-squad changes, and run architecture syncs with the Technical Director Maintain a technical debt and risk register covering security, compliance, and uptime, and secure roadmap funding for top items Address cross-cutting challenges involving agent resource usage, detection quality, upgrades and releases, backend scale and cost, and migration of performance-critical paths from Python to Go or Rust where justified by data Set standards for design reviews, code reviews, testing, observability, and secure SDLC Lead or co-lead unclear or cross-squad SEV1/SEV2 incidents, ensure blameless post-mortems are completed within 24 hours, and close follow-up actions Drive practical adoption of AI-augmented SDLC practices through real changes Mentor senior engineers and squad leads toward staff-level scope Act as a technical bar-raiser in hiring loops for senior and lead roles Represent engineering in product and sales discussions, providing estimates and feasibility assessments and avoiding dated customer commitments without a written squad-lead estimate Ship at least one non-trivial production change within 30 days, explain the full agent-to-backend request path, and identify the top 10 technical risks Own a cross-squad initiative within 90 days with an approved ADR, measured baseline, staged rollout plan, and a risk register reviewed in architecture sync Put the initiative into production within six months with before-and-after metrics, and have an engineering standard adopted by at least three squads Become the default escalation point for cross-cutting technical decisions within 12 months and mentor at least one senior engineer into broader scope