We process large volumes of real-world internet infrastructure data to understand how systems are exposed, connected, operated, and abused. The work sits between software engineering, internet measurement, big data systems, and security research.

We are looking for a Security Research Engineering Intern who wants to build useful systems, chase interesting internet behaviour, and work on problems that do not come with a tutorial.

This is not a “sit in meetings and take notes” internship. You will build, investigate, validate, and ship work that supports real security research.

What you’ll work on

You’ll help build the tooling and data workflows behind our research and intelligence platform.

Depending on your skills, you might work on:

• Building Go tools for collecting, enriching, and analysing internet infrastructure data

• Working with high-volume event streams, Protobuf messages, schemas, and data pipelines

• Helping turn interesting signals into repeatable research workflows

• Building utilities for querying, clustering, tagging, and validating infrastructure

• Supporting public security research with engineering, analysis, and technical validation

• Improving internal systems for handling APIs, queues, databases, and high-throughput data

• Investigating unusual services, patterns, networks, and behaviours seen across the public internet

We will not list every dataset, technique, or workflow here. Part of the fun is joining the team and working on the real problems.

What we’re looking for

We care much more about energy, judgement, and technical curiosity than polished corporate experience.

You should have:

• Practical Golang experience

• Interest in big data, distributed systems, pipelines, or high-volume processing

• Strong Linux and command-line instincts

• Good understanding of networking basics: IPs, DNS, HTTP, TLS, ports, and services

• Experience working with Protobuf, APIs, databases, queues, event streams, or data pipelines

• Interest in security, internet infrastructure, OSINT, threat intelligence, or abuse research

• Public evidence that you build things: GitHub projects, tools, writeups, blogs, CTFs, research, open-source work, or similar

• Good judgement around responsible research and ethical boundaries

You’ll probably enjoy this if

• You see an unusual service, hostname, certificate, ASN, or network pattern and immediately want to understand it

• You have side projects that became more serious than expected

• You like writing small tools that make research faster, sharper, or more repeatable

• You think Go, Linux, queues, databases, and a few well-designed pipelines can solve a surprising number of problems

• You enjoy turning high-volume internet signals into useful intelligence

• You care about how the internet actually behaves, not just how it is documented

• You want to ship work that contributes to public security research

Bonus points

• Experience with ClickHouse, Elasticsearch, Postgres, SQL, Kafka, Redpanda, NATS, or similar systems

• Experience building collectors, enrichment pipelines, analytics tools, or research utilities

• Familiarity with Docker, cloud infrastructure, distributed systems, or observability tooling

• Experience building security, networking, OSINT, or data-processing tools

• Published technical writing, talks, research, open-source tooling, or weird-but-impressive side projects

What you’ll get

• Real engineering work from day one

• Exposure to internet-scale data and security research

• Mentorship from a technical founding team

• The chance to contribute to public research

• A remote-first team across UK, EU, and US time zones

• A fast-moving startup where good work gets noticed quickly

Who this is for

This is for someone early in their career who is technical, curious, and a little obsessive in the right way.

You might be a student, recent graduate, self-taught engineer, open-source contributor, CTF player, homelab person, data engineer, or early-career developer who has started drifting toward security and internet infrastructure.

We do not care if your CV is perfectly linear. We care that you can build, debug, investigate, communicate, and keep pulling on a thread until something interesting falls out.