Build attack-surface
tooling with us.
GuardianGaze Limited is hiring senior engineers and threat researchers to build Guardian Gaze. London-based, remote-friendly within the UK. Small team, high autonomy, and every shipped feature visible.
Hiring across four functions
Open roles get listed here once scoped. If you fit a function below, send a note before the listing exists.
Senior detection engineers & threat researchers
Build and maintain scanners across application, network, domain, brand and cloud surfaces. Develop new detection logic, manage the breach-dataset pipeline, and improve correlation over raw scan output.
Senior backend engineers
Own the scan orchestration pipeline, the REST API, multi-tenant isolation, scoped cloud integrations, event delivery and webhook signing. The stack is built for portfolio-scale tenants.
Senior frontend / full-stack
Build the dashboards, reports library, alerts and takedown workflow, the MITRE ATT&CK lens and the compliance interface. Design-led work where every screen ships with the data wiring done.
Security analysts (GRC and TPRM)
Review disputed findings, run the brand-takedown workflow, onboard customers, and make the rating model better through observation rather than guesswork.
A few things to know
- London-based, remote-friendly within the UK
- Small team, high autonomy, every shipped feature visible
- Open roles are listed here once scoped
- No listing yet for your function? Send a note via the contact form
- We respond within 24 hours
Four functions, each shipping end to end
Research builds detection and validates findings. Platform engineering builds discovery and scoring infrastructure. Product decides what gets built and, more often, what gets refused. Customer engineering works directly with design partners on findings quality and workflow fit.
Each function ships end to end rather than handing work over a boundary. The person who writes a detection is the person who hears when it produces a false positive, which is where accuracy actually comes from, not from a QA stage bolted on afterwards.
That structure only works while the team is small enough for it, and we would rather grow slowly and keep it than grow quickly and rebuild it as a process.
Judgement, and a tolerance for saying no
The hardest problems here are not technical. Deciding whether an exposure is critical or moderate, whether a version match is real or a backported patch, whether a similar domain is preparation or coincidence: those are judgement calls that determine whether practitioners trust the output.
So we look for people who have done the work rather than described it, and who are comfortable removing a finding, a feature or a claim when the evidence does not support it. A great deal of what makes this product credible is what it declines to assert.
Backgrounds that fit: offensive security, detection engineering, incident response, and large-scale platform work. Backgrounds that do not: anyone whose instinct is to ship the claim and let marketing sort out the caveats.
London-based, remote-friendly within the UK
GuardianGaze Limited is a London company registered in England and Wales and a subsidiary of RedSecLabs. Roles are London-based and remote-friendly within the UK.
The team is small, which means high autonomy and correspondingly high exposure: your work reaches customers quickly, and so do its mistakes. That suits some people considerably better than others, and it is worth being honest about before an interview rather than after a start date.
If nothing listed matches and you think you should be here, say so directly. At this size the roles follow the people at least as often as the other way around.
Common questions
Where are roles based?
London, and remote-friendly within the UK. GuardianGaze Limited is registered in England and Wales.
What backgrounds fit?
Offensive security, detection engineering, incident response and large-scale platform engineering. The common thread is having done the work rather than described it.
What is the team structure?
Four functions (research, platform engineering, product and customer engineering) each shipping end to end rather than handing work across a boundary.
What is it actually like?
Small team, high autonomy, and correspondingly high exposure: your work reaches customers quickly and so do its mistakes. That suits some people much better than others.
Nothing listed matches me. Should I get in touch?
Yes. At this size roles follow the people at least as often as the other way around.
No listing for your function yet?
Send a note through the contact form and tell us which function fits.
We respond within 24 hours.