Build fb641aaf 13 Nov 2026
Book a demo

Careers

Build what has to be right

We hire people who care whether a number is right and can show why. You work on one regulation at a time with the text open, and someone from the other discipline checks what you change.

See open roles How we hire

Open roles

6 roles, newest first

Each role says who you would report to, where the work is and what it pays.

Methodology London

Cryptographic assurance analyst

Pay
£100,000 to £135,000 a year
Reports to
Elif Demirci
Listed

Work on entropy validation and the move to post-quantum cryptography. You will read the NIST texts closely and tell customers exactly what a test does and does not show.

You will

  • Implement the estimators and the health tests of SP 800-90B, and check them against published values.
  • Keep the inventory model for post-quantum migration honest about what it can and cannot see.
  • Write up what you find, for customers and for the essays.

You bring

  • A background in cryptographic evaluation, statistics or hardware security.
  • The habit of noticing which section of a standard a claim rests on.
  • A wish to say what has not been checked.

Apply for this role: Cryptographic assurance analyst

Customers London

Customer engineer, parallel runs

Pay
£80,000 to £110,000 a year
Reports to
Rafaela Quintero
Listed

Sit with the team of a customer through a parallel run, and explain every difference to the line, in the language of their regime.

You will

  • Run sample books and parallel runs, and keep the log of cases.
  • Write the validation pack with the methodologists.
  • Bring what customers find back to the people who build.

You bring

  • Experience in model validation or regulatory reporting at a bank or an insurer.
  • Patience with data that arrives in odd shapes.
  • A plain way of writing, because the pack is read by people who were not in the room.

Apply for this role: Customer engineer, parallel runs

Verification Barcelona

Verification engineer

Pay
€100,000 to €135,000 a year
Reports to
Dr Anneliese Okafor
Listed

Turn statements about the engines into proofs, certificates and mutation tests, and decide with us which level each statement can honestly claim.

You will

  • Write SMT-LIB encodings of properties of the kernel, and check them with two solvers.
  • Extend the mutation lists so that every changed line fails a test.
  • Say tested when a statement is only tested.

You bring

  • Experience with an SMT solver, a proof assistant or a model checker.
  • Care about the difference between a proof and a test.
  • Enough numerical background to read an encoding of floating point.

Apply for this role: Verification engineer

Methodology Barcelona

Insurance methodologist

Pay
€85,000 to €115,000 a year
Reports to
Priya Raghunathan
Listed

Read the text of Solvency II and the ICS and turn each rule into something that can be tested. You decide what a clause means, write down why, and defend it to people who validate models for a living.

You will

  • Map clauses of Delegated Regulation (EU) 2015/35 and of the IAIS Insurance Capital Standard to the functions that carry them.
  • Write the cases that a change in the text must break.
  • Answer questions from the validators of customers, in writing.

You bring

  • Practice in the actuarial or risk function of an insurer, or at a supervisor.
  • Fluency in the standard formula and in how its modules combine.
  • Willingness to be shown wrong by a test.

Apply for this role: Insurance methodologist

Kernel Barcelona

Numerical software engineer

Pay
€95,000 to €130,000 a year
Reports to
Tomasz Wierzbicki
Listed

Write the arithmetic that every engine stands on. Your work has to return the same bits in five JavaScript engines, so you will spend your days on what a floating point number does and does not promise.

You will

  • Extend the kernel with the operations that the next regimes need, using only add, subtract, multiply and divide.
  • Write the property tests and the cross-engine checks that show a change has not moved a bit.
  • Review changes from the methodologists for what rounding will do to them.

You bring

  • Years of numerical work in any language, and a view on the order of a sum that you can defend.
  • A habit of writing the test before the fix.
  • Comfort in reading a specification and saying what it leaves open.

Apply for this role: Numerical software engineer

Platform Barcelona

Site reliability engineer, edge

Pay
€70,000 to €95,000 a year
Reports to
Jonas Falk
Listed

Run the deployment, the release pipeline and the checks that keep a receipt from last year verifying. Most of the work is making sure that nothing surprising happens.

You will

  • Own the Workers, D1 and R2 deployment, and the pipeline that builds it the same way twice.
  • Run the cross-engine parity check on every release.
  • Take a share of the on-call rota, which is paid and rotates.

You bring

  • Production experience of an edge or serverless platform.
  • Reproducible builds, and the habit of finding out why two builds differ.
  • A clear way of writing an incident report.

Apply for this role: Site reliability engineer, edge

How we hire

Four steps, and a decision

The process is the same for every role. After the last step you hear from us within five working days, and an offer comes with the pay range of the role in writing.

  1. Write to us

    Send a CV or a link to work you are proud of, and two paragraphs on one thing you checked that other people had trusted. There is no cover letter. We reply within five working days.

  2. Talk about the work

    Forty-five minutes with the person you would report to, about work that you have done. There are no puzzles.

  3. Take a problem from our code

    A task of two hours at most, taken from our own code. We pay for the time. Use any tools you like, and tell us what you used.

  4. Meet the other discipline

    An engineer meets a methodologist, and a methodologist meets an engineer, because that is how we work. You decide whether it is the team for you.

How we work

Four habits, kept

These are the habits that new people notice first. Ask the person you meet whether they are true.

  • Review crosses disciplines

    No change is reviewed only by the discipline that made it. A methodologist reads the code that carries a rule, and an engineer reads the clause.

  • Not knowing is allowed

    Every essay we publish ends with what we have not checked. Saying so is part of the work, and no one is marked down for it.

  • Where you work

    Two days a week in an office is the usual pattern, and the rest is wherever you work best. Some roles are remote within the hours of an office.

  • Adjustments

    Tell us what you need at any stage and we will arrange it. You do not have to explain why.

We welcome applications from people of every background, and we decide on the work that you show us.

Open application

Nothing that fits?
Write anyway.

Say what you would work on and why. We read every message and reply within five working days.

Write to contact@graphatlas.com How we hire

The next step

Bring us
one book

A scoping call, a sample book and a parallel run on your data. Most teams have the first reconciled number inside two weeks, and a receipt for it on the day.

Book a demo Work out a price