Product Engineer, Working Student

Role overview Contribute to software that helps keep websites, applications, and game servers available during distributed denial-of-service attacks. Work can span customer issues, Linux traffic filtering, game and application protection, attack detection, platform services, and web interfaces. The source describes the same broad engineering work as the other product engineer role, but does not specify student-specific duties, hours, or eligibility details.

Responsibilities - Help handle feature requests and investigate customer problems, including complex issues that are difficult to reproduce. - Contribute to high-performance Linux filters, protection proxies, or verification services for games and online applications. - Work on traffic detection and mitigation systems using network signals and telemetry. - Support platform services for customer accounts, billing, and support, or customer dashboards and documentation. - Collaborate through weekly sprints, written updates, and calls for debugging and technical discussion.

Requirements - A foundation in Linux and networking, along with production coding experience in at least one of Go, Java, or TypeScript. - Good written communication skills and the ability to contribute to resolving customer issues. - Strength in one or two relevant technical areas, such as eBPF/XDP, Go networking services, traffic analysis, Java and Spring Boot, or TypeScript and React. - Familiarity with tools and practices relevant to the chosen area, such as PostgreSQL and OAuth2, or binary protocols, rate limiting, and TLS. - Ability to read code across areas beyond your primary specialty.

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 The team uses weekly sprints and Linear to coordinate development. It aims to automate repeatable tasks, offers few recurring meetings, and generally lets engineers manage their own schedules while using calls for debugging and discussion.