Product Engineer (m/f/d)

Role overview Develop software across a platform that helps keep websites, applications, and game servers available during distributed denial-of-service attacks. Depending on your strengths, you could work on Linux packet filtering, traffic detection, proxy services, platform APIs, customer-facing web tools, or technical support and debugging. The role expects depth in one or two areas and the ability to navigate code across the wider system.

Responsibilities - Handle feature requests and investigate complex customer issues, including problems that occur once and are difficult to reproduce. - Build high-performance Linux traffic filters, or proxy and verification services for games and online applications. - Develop systems that detect suspicious traffic and trigger mitigations, using network signals and telemetry. - Contribute to account, billing, and support services, or to customer dashboards and documentation. - Collaborate through weekly sprints, written updates, and calls for debugging and technical discussion.

Requirements - A solid foundation in Linux and networking, with production experience in at least one of Go, Java, or TypeScript. - Strong written communication, including the ability to help resolve customer problems. - Deep experience in one or two relevant areas, such as eBPF/XDP and C, low-latency Go services, traffic analysis, Java and Spring Boot backends, or TypeScript and React interfaces. - For the chosen area, familiarity with its associated tools and practices—for example, PostgreSQL and OAuth2 for backend work, or binary protocols, rate limiting, and TLS for proxy services. - Comfort reading and working with code beyond your main area of expertise.

Nice to have Experience with LLM applications, cloud or edge platforms, identity and security, large-scale data systems, payment integrations, low-level C performance, operating networks or servers, or writing developer documentation and API specifications.

Benefits and work setup Work is organized in weekly sprints with a Scrum-like process and tracked in Linear. The team aims to automate repeatable tasks and holds few recurring meetings; engineers generally manage their own schedules and use calls to debug and discuss work.