Carrers

Work that has to hold.

Most software gets a second chance. Someone restarts the service, rolls back the build, walks into the data centre. Ours does not get that. It runs where nobody can reach it, and it has to keep running anyway.

That single constraint shapes everything: how we build, how we test, how we decide, and who we hire.

Concept & Values

  1. _001

    Expanding space

    Expanding minds, not just technology.

    Every capability we build widens what someone else can attempt. That is the point of infrastructure. The measure is not what we ship, it is what becomes possible once we have shipped it.

  2. _002

    Driven to change

    Human and AI interaction, in service of quality of life.

    We treat human expertise and artificial intelligence as one combined capability rather than two competing ones. Neither creates lasting value alone. The combination is the engine.

  3. _003

    People-centred

    Empowered minds create together.

    There are no support functions here. Every role exists because it contributes to what the system can do. Decisions are made close to the knowledge required to make them well.

How We Work

Capability is people and AI together

We treat human expertise and AI systems as one combined capability rather than two competing ones. Neither creates lasting value alone. In practice that means senior engineers working with agentic tooling as a matter of course, not as an experiment. If that interests you rather than unsettling you, you will recognise how we work.

There are no support functions

Every role exists because the system needs it. Some roles build products. Some strengthen customer relationships. Some hold trust, compliance and governance in place. All of them decide what the company is able to do. If a role were not critical, it would not exist.

Decisions belong close to the knowledge

Work happens in teams formed around missions rather than around seats. Decisions are made by the people nearest the problem. For critical decisions we ask for domain expertise, system understanding and product perspective, and at least two of those have to agree before we execute. We document what we decide. We avoid process for its own sake.

We expect to be challenged

Progress depends on challenge. We encourage debate, critical thinking and the questioning of assumptions. Ideas are judged on merit, not on tenure or position. We challenge ideas without diminishing people, and we treat constructive disagreement as a sign the system is working.

Learning is a responsibility

We operate where the technology moves faster than the regulation. Staying current is part of the job rather than something you do in your own time. We share what we build, what fails and what we learn from it.

We are small, and the work is serious

You will have more ownership than at a large prime and fewer people to hide behind. Parts of our work fall under export control and national security requirements. We will be specific about what that means for you before it affects you.

On who we hire

We believe different perspectives make better decisions and better engineering. We assess people on what they can do and how they think, and we welcome applications from anyone who recognises their work in the description. If you need an adjustment at any point in the process, tell us and we will make it.