Security Engineer (Research Infrastructure) [Remote]

Status (updated 21 August 2026): this hiring round is temporarily paused. We expect to resume in the next ~2 months. You can still apply, and we will contact you when the process restarts.

About Resolution

Resolution does research on how to align artificial superintelligence (ASI). ASI may be developed in the next few years, but it is unclear whether alignment is on track to be ready in the same timeframe. We aim at higher a priori confidence in aligned outcomes by pursuing a portfolio of theory and empirics bets, any one of which — if it succeeds — would meaningfully advance the field. We invest heavily in research automation to accelerate progress, and we believe that stronger alignment theory unlocks higher automation: more principled approaches give us better filters for which directions of automated research are promising.

Resolution was founded in 2026 by researchers from UK AISI's Alignment Team, who ran the £30m Alignment Project , and Timaeus , who pioneered applying singular learning theory to alignment.

For more information, see our announcement .

About the Team

Resolution's work will involve sensitive frontier-relevant research and partnerships with AI labs. This role exists both to protect that work and to enable it: good security is what makes deeper lab partnerships possible. We draw a distinction between two closely related areas of security:

• Research & infrastructure security. Securing how research actually runs: CI/CD pipelines, automated research agents, multi-cloud compute, and code/data/model-weight handling.

• Corporate IT & security. The endpoint, identity, and collaboration scaffolding a distributed research org runs on, in combination with the compliance frameworks that unlock lab partnerships.

This role focuses on the former, covering security on the technical side of the organization. You would report to senior leadership and work closely with our security and engineering teams (as well as with our operations team).

In practice, we expect to grow the security team one hire at a time, so your initial set of responsibilities is likely to span both areas. We expect the distinction to clarify over time.

About the Role

You are the security architect for our research pipeline. You'll define how we securely conduct research across multiple cloud environments, partnering closely with engineering to make CI/CD, automated research agents, and large-scale compute secure by default. You would build a hardened environment where researchers and agents iterate at speed without risking data leakage, supply-chain compromise, and other security failures.

Responsibilities

1. Secure DevSecOps & CI/CD Orchestration

• Pipeline Hardening: Build security guardrails directly into our CI/CD pipelines. Ensure that every deployment, whether manual or agent-driven, is automatically scanned, verified, and compliant.

• Automated Verification: Establish workflows where our agents can test their own code and infrastructure changes against security policies before deploying to production environments.

• Infrastructure as Code (IaC): Lead the implementation of "Compliance as Code." Automate the auditing and enforcement of security configurations across our AWS, GCP & neocloud footprints.

2. Supply Chain Security for Automated Research

• Provenance and Integrity: In an environment where we rely heavily on automated coding agents, build systems to ensure the provenance of code and dependencies. Implement robust signing, SBOM (Software Bill of Materials) generation, and automated vulnerability management.

• Agent Sandbox Security: Define and enforce security models for our research agents. Ensure that agents have the "least privilege" access required to execute experiments while remaining isolated from sensitive IP and credentials.

3. Multi-Cloud Research Infrastructure

• Compute Security: Manage the security architecture for our high-compute research environments. We operate in a multi-cloud ecosystem; you will be responsible for consistent, zero-trust network segmentation and identity management across disparate cloud providers.

• Research Data Protection: Develop and maintain the data handling protocols necessary for working with pre-publication research and potentially sensitive model weights.

4. Enabling Frontier Access

• Compliance as a Competitive Advantage: Partner with AI labs to navigate security audits. You will bridge the gap between our "move fast" research culture and the high-bar security requirements of frontier model providers, turning compliance into an accelerator for our research agenda.

You May Be a Good Fit If You

• Are a seasoned security engineer who writes code, with deep experience in Terraform, Kubernetes, and CI/CD tools (GitHub Actions, GitLab CI).

• Have managed security across multiple cloud providers (AWS / GCP / neoclouds) and understand the nuance of securing ephemeral, high-compute research clusters.

• Take a pragmatic approach to modern software supply chains and understand the unique risks of AI-driven development and how to mitigate them without killing velocity.

• Understand the threat model of a high-value target for state-level actors and IP theft, and can build systems robust against sophisticated adversaries.

• Can explain complex security trade-offs to lead researchers and scientists, saying "yes, safely" rather than just "no."

• Are willing to use AI tools aggressively in your own workflow, with appropriate care to not get fooled!

• Are motivated by alignment of artificial superintelligence (ASI) and want to contribute to it full-time.

Why This Role is Unique

At this organization, "Corporate Security" is a separate function. This role is focused on the Research Infrastructure. You will be working at the frontier of how automated alignment research is actually done. You will be building the security primitives for a new way of doing science: one where humans and machines collaborate to solve the most important problem of the 21st century.

Application Process

1. Application review. Every application gets at least one human review.

2. CodeSignal (90 minutes). The Industry Coding Assessment, not LeetCode: we want the content of our assessments to have at least some overlap with the things we expect you to do in real life, even if asking you to write code is a bit dated.

3. Screening call (15 minutes). An informal chat, where we briefly cover background, fit, and motivation.

4. Technical and experience interviews (about 2-3 hours in total, across two or three sessions). We're still settling the exact shape of these for this role, and we'll tell you the format before each session. Expect some combination of: a technical interview on reading and diagnosing unfamiliar code or infrastructure, without AI assistance; a technical interview in two parts, an AI-unassisted design and specification problem followed by an AI-assisted implementation of it; and an experience interview walking through one or more past projects in detail, with time to discuss the role and answer your questions.

5. 1-on-1s. A chat with our chief scientist, Geoffrey, as well as any relevant people from the team you would like to talk to and ask questions.

6. References. We'll reach out to a few references as we make our final decision.

On scheduling. Where we can, we'll bundle the sessions in (4) so they occur back to back, though with different interviewers, so you get a chance to talk to more of our team. We'll also run (5) and (6) in parallel. Our aim is to get you an update within 2-3 days of each stage, which means a process of about three weeks. For some candidates, especially if you have competing deadlines, we'll aim to push faster.

On the technical interviews. We dropped work tests because there's so little signal left in them. What we're looking for is how well you figure out what to tell the AIs, how well you interact with the AIs throughout implementation, and how well you navigate the resulting outputs. The exact details of the tests are still being settled for this role, but what we're testing for will remain the same.

On interviewers. Most of our interviewers are on our engineering team, and we'll try to set things up so that you get to talk to different people at each interview. Each interview will have time for you to ask questions.

Logistics

Salary: Your salary depends on the scope, autonomy, and impact we expect you to have while working at Resolution. Annual USD salaries for remote and Berkeley work are:

• L4 (SWE II): Remote $208,000; Berkeley $346,000

• L5 (Senior SWE): Remote $270,000; Berkeley $451,000

• L6 (Staff SWE): Remote $402,000; Berkeley $670,000

• L7 (Senior Staff SWE): Remote $558,000; Berkeley $930,000

We level using an internal adaptation of Google's standard levelling; the band above is indicative of where a strong candidate might come in.

Location: Berkeley, California. Remote may be considered in exceptional cases.

Benefits:

• 5 weeks of paid vacation per year, in addition to public holidays.

• Comprehensive healthcare insurance (medical, dental, vision).

• Unlimited sick leave to prioritize your well-being.

• An unconditional 401(k) contribution equal to 4% of your salary.

Visa sponsorship: We can sponsor visas for relocation to Berkeley.

Minimum education: A bachelor's degree in a field relevant to the role, or an equivalent combination of education, training, and/or professional experience that demonstrates comparable knowledge.

Status (updated 21 August 2026): This hiring round is temporarily paused due to capacity constraints. We expect to resume in the next ~2 months. You can still apply; we will contact you when the process restarts and will get back to everyone.

Start date: ASAP.

AI Usage

We may use automated systems and AI tools to support recruiting and hiring activities. Final hiring decisions are made by human decisionmakers.