CloudArmour builds network security infrastructure for the cloud era. Our flagship product, Neurowall, is a Next-Generation Firewall built on eBPF/XDP — the same kernel technology used by Cloudflare, Meta, and Google internally. We write kernel code, ship production Go services, and build intuitive UIs on top of infrastructure most teams never touch.
We are a small team. Every hire shapes how this company works.
Early-stage. Technical depth. Real impact.
Build products that protect organizations from real cyber threats. Your work directly impacts the security of internet infrastructure.
Work with eBPF, XDP, Linux kernel networking, and modern cloud infrastructure. Solve problems that require deep systems engineering expertise.
Join a growing company where your contributions shape the product, the architecture, and the company culture.
We build with Go, eBPF/C, modern Linux, Kubernetes, and cloud-native technologies. We value clean code and operational excellence.
Small team, direct communication. Everyone is close to the product and the decisions that shape it.
We know what we are building and why. Effective security should be accessible, simple, performant, and reliable.
10 open roles across engineering, go-to-market, content, and marketing.
The eBPF/XDP kernel program is the core of Neurowall. It runs in the network driver, evaluates every packet before the kernel network stack sees it, and makes allow/drop decisions in under 50 microseconds. You will own this program end-to-end: rate limiting, connection tracking, DDoS detection, protocol parsing, and the shared-memory interfaces that expose per-CPU counters to userspace.
This is not a "learn eBPF on the job" role. You will be writing production kernel-space C and reviewing verifier output from day one. We care about what you have built, not your title.
Send the role name in the subject line, 2–3 paragraphs on relevant experience, and a link to code you have written. No recruiters.
Apply now →The Go services layer turns kernel-space decisions into a manageable system: REST and gRPC APIs, rule synchronization across eBPF/nftables/database, high availability via etcd Raft, backup and restore, threat intelligence ingestion, and the LLM integration that provides contextual threat analysis. You will own significant parts of this surface.
Send the role name in the subject line, 2–3 paragraphs on relevant experience, and a link to code you have written. No recruiters.
Apply now →Neurowall's threat intelligence layer ingests indicators from multiple external feeds, caches them in memory, and correlates them against live traffic in real time. The detection layer sits above this: heuristics for behavioral anomaly detection, baseline learning, and LLM-powered contextual analysis. You will own the correctness, coverage, and performance of this entire pipeline.
Send the role name in the subject line, 2–3 paragraphs on relevant experience, and a link to code you have written. No recruiters.
Apply now →Neurowall's web UI is a real-time systems dashboard: live packet counters, DDoS event timelines, firewall rule management, threat feeds, and VPN peer configuration. It is built in Preact and communicates with the backend via REST and Server-Sent Events. The bar is high — this is a tool that operators use during active incidents.
Send the role name in the subject line, 2–3 paragraphs on relevant experience, and a link to code you have written. No recruiters.
Apply now →Neurowall ships as a Go binary, a Docker image, and packaged .deb/.rpm. The infrastructure around it — CI/CD, packaging, Prometheus/Grafana monitoring, and Kubernetes deployment — needs someone who treats infrastructure as code and takes uptime seriously.
Send the role name in the subject line, 2–3 paragraphs on relevant experience, and a link to code you have written. No recruiters.
Apply now →Neurowall makes performance claims — 10–24 Gbps throughput, sub-50μs drop latency, DDoS mitigation at line rate. Someone has to prove those claims are real, find where they break down, and make sure every release ships with that evidence. You will own the lab environment, the test methodology, and the results.
This is not QA in the traditional sense. You think in topologies, build attack scenarios, and know when a benchmark number is misleading.
Send the role name in the subject line, 2–3 paragraphs on relevant experience, and a link to code you have written. No recruiters.
Apply now →CloudArmour's internal monitoring platform collects and stores high-volume telemetry from deployed Neurowall instances — packet counters, drop events, DDoS detections, rule hits, interface statistics. It is built in Rust and backed by ClickHouse. You will own this system end-to-end: the ingestion pipeline, the storage schema, the query layer, and the reliability of the whole thing under sustained write load.
Send the role name in the subject line, 2–3 paragraphs on relevant experience, and a link to code you have written. No recruiters.
Apply now →You take a prospective customer from "we have a demo call" to "it is running in their environment and they understand what it is doing." You own the technical side of the sales process, customer deployments, and the feedback loop back to engineering.
This role sits between engineering and customers. You need enough technical depth to configure Neurowall, read packet captures, and diagnose why a rule is not matching — and enough communication skill to explain what you found to someone who is not an engineer.
Send the role name in the subject line, 2–3 paragraphs on relevant experience, and a link to code you have written. No recruiters.
Apply now →Neurowall is a complex product. The gap between "it is running" and "the operator understands what it is doing and trusts it" is almost entirely a documentation problem. You will own that gap: the API reference, the deployment guides, the configuration documentation, and the operational runbooks that help engineers and operators get value from Neurowall without needing to ask anyone.
Send the role name in the subject line, 2–3 paragraphs on relevant experience, and a link to code you have written. No recruiters.
Apply now →CloudArmour's public presence — primarily LinkedIn, but also technical communities like Hacker News, Reddit (r/netsec, r/linux), and developer forums. You will own the content calendar, the tone of voice, and the pipeline from "something interesting happened in the codebase" to "post that makes engineers stop scrolling."
This role requires genuine technical curiosity. You do not need to write eBPF code, but you do need to understand what it does well enough to explain it to a security engineer who has never heard of Neurowall.
Send the role name in the subject line, 2–3 paragraphs on relevant experience, and a link to code you have written. No recruiters.
Apply now →Benchmarked to Indian and global market rates. We do not lowball people who want to do serious work.
Async-friendly. No micromanagement. You are judged on what you ship, not when you are online.
You talk to the founders directly. Questions get answered, decisions get explained, and your input reaches the people who act on it.
Work on infrastructure that matters. The problems here are genuinely hard and the stakes are real.
Every early hire shapes how the company works — the architecture, the culture, the product direction.
Send an email with the role name in the subject line, 2–3 paragraphs on relevant experience (specific projects, not job descriptions), and a link to code you have written. For eBPF roles, describe one specific verifier rejection or kernel-space bug you debugged.
[Role Name] — Your Name