Senior Infrastructure Engineer
Own the infrastructure BruhnBruhn runs on. Linux, networks and container platforms across several environments, operated to a standard that holds up under audit. This is a security vetted position.
The work
We run our own infrastructure. That is a deliberate choice rather than an accident of history. The sovereignty of what we build matters to the people who buy it, and you cannot claim it credibly if you have outsourced the foundation.
This role owns that foundation. Linux systems, networks, storage and container platforms across more than one environment, run to a standard that holds when a customer’s security team starts asking questions.
It is a hands-on engineering role with real autonomy.
What you will work on
- Linux systems end to end: provisioning, hardening, patching, monitoring, backup, and restores that have actually been tested
- Networks: segmentation, routing, firewall policy, and encrypted transport between sites
- Identity and access: directory services, single sign-on, certificate and key management
- Container platform operations: Kubernetes, private registry, object storage
- Connecting environments that are administered separately and still have to interoperate, without either side extending blanket trust to the other
- Availability, capacity and incident response for services the rest of the engineering team depends on
- The evidence trail: configuration as code, documentation, and the records that let us answer a security questionnaire with facts rather than assurances
What we are looking for
- Deep Linux experience, in the sense of having owned production systems rather than used them
- Networking to protocol level, including the ability to diagnose from the packet upwards rather than by restarting things
- Practical experience joining separately administered environments: identity federation, access control across a boundary, and policy that survives the join
- Container platform operations at production quality
- Infrastructure as code, with the discipline to keep the repository the source of truth rather than a historical record
- Security engineering as a habit: least privilege, hardening baselines, patch cadence, and an instinct for what an attacker would try first
Useful, and we will make room for you to grow into it
- Familiarity with NATO standards and working practice
- Experience operating under ISO 27001, NIS2 or a comparable regime
- Experience in an environment subject to national security requirements
- Swedish
How we work
Decisions are made close to the knowledge needed to make them well. Teams form around missions rather than seats. There are no support functions: every role exists because the system needs it.
We treat human expertise and AI systems as one combined capability. In practice that means senior engineers working with agentic tooling as a matter of course rather than as an experiment.
We are small, which means more ownership than at a large prime and fewer people to hide behind.
This role may be subject to Swedish security vetting. We will explain what that involves before any assessment begins.
