Security Engineer - Node.js Proactive Defense

• A focus on professional development.
• Interesting and challenging projects.
• Fully remote work with flexible working hours, that allows you to schedule your day and work from any location worldwide.
• Paid 24 days of vacation per year, 10 days of national holidays, and unlimited sick leaves.
• Compensation for private medical insurance.
• Co-working and gym/sports reimbursement.
• Budget for education.
• The opportunity to receive a reward for the most innovative idea that the company can patent.

• Proven experience building and shipping a new product, security solution, major feature, or technical system from scratch.
• Strong evidence of end-to-end technical ownership, from initial investigation and architecture through implementation, release, and production iteration.
• Strong web application security knowledge and current knowledge of practical exploitation.
• A working sense of how detection rules behave at scale - what catches attackers without flagging the long tail of legitimate code.
• Ability to start as the PM, architect, lead engineer, and QA for this product. You ask for resources or help when you need them; you don't wait to be told what to do.
• Comfort directing AI coding agents to high-quality output.

• Prior work on runtime-protection products, application firewalls, or instrumentation tooling.
• Background in malware analysis or incident response.
• Familiarity with managed-hosting environments.
• Public security research, vulnerability disclosures, or detection rulesets you've authored.
• Familiarity with the Node.js runtime and the JavaScript ecosystem.

We protect web hosting providers and the sites running on their infrastructure through a defense-in-depth stack: web-server-layer WAF, runtime application self-protection for PHP, deep application integrations (WordPress plugins and similar), a malware scanner with cleanup capability, and network-layer firewalls and IP reputation. The pieces talk to each other, and the threat intelligence they generate at scale powers detection across the stack.

Node.js is the segment of the hosting market growing fastest, and the next layer we want to build for it is runtime protection inside the Node.js process itself. Most Node.js workloads on managed hosting today are AI-generated web apps deployed by non-technical owners who can't, won't, and shouldn't be expected to patch their own code or audit their own dependencies. We're going to defend those apps anyway - at runtime, without their cooperation, without breaking them.

You'll build that runtime protection layer end-to-end.

• The product. A brand-new product line, yours to define - what we intercept, what we don't, what the customer-visible surface looks like.
• The technical approach. Instrumentation strategy, deployment shape, programming language - all open. You'll consult with our architects but the direction is yours.
• Implementation, end to end. You'll have the full tooling stack we provide - LLM subscriptions, modern dev infrastructure, the works. Use what makes you fast.
• Methodology. How you build conviction in your detection logic - your call.
• Cross-layer signal. Our existing stack produces threat intelligence at unmatched scale: tens of millions of monitored sites, petabyte-scale malware sample storage, real-time domain and URL reputation, IP-level attack feeds. These are available for you to plug into. Use what helps.

The product is held to four numbers: runtime overhead, false positives, false negatives, and customer-escalation volume. They reflect what hosting providers and their customers care about. Hit them well and the product runs inside a meaningful slice of the modern Node.js web.

An experienced researcher or engineer who can build and iterate on a brand-new product, driving both the research and the development. The hard part of this work is knowing what's malicious, what's vulnerable, and what's just an unusual but legitimate pattern - and being right about it across the long tail of frameworks, libraries, and customer code we'll encounter in production.

• Not a scope-and-handoff role - you drive the work and own the outcome.
• Not a "platform team will productize this later" role - you ship to real customer fleets and watch the telemetry quickly.
• Not a spec-and-review role - you are hands-on every day.

• Most managed-hosting customers are not developers. They cannot patch their apps. They cannot audit their dependencies. They will keep deploying vulnerable code from AI assistants because that's how modern web apps get built now. The textbook advice - "secure your code, audit your dependencies" - does not apply to them.
• If we don't intercept exploits at runtime, nobody will. The numbers you hit on detection, performance, and false positives will materially affect how much of the modern web stays online when the next exploit class drops.