This role sits somewhere between DevOps, systems engineering, backend development, infrastructure, security, integrations, and occasionally staring at a terminal wondering who the fuck thought this architecture was a good idea.
Is This You?
Does your brain allow you to deal with broken paths, misaligned configurations, failing services, undocumented dependencies, and ten configuration files open at the same time? Then you are the exact person we are looking for.
We need someone who can look at a broken system, resist the urge to complain for six hours, and start figuring out what the hell is actually happening.
Something About Us
We are a group of ambitious, highly driven, and determined people working on the problems most people consider too difficult, too risky, or simply not worth the headache.
We build industrial SaaS platforms, communication systems, APIs, data-processing infrastructure, security mechanisms, monitoring tools, and software connected to satellite and space-related applications.
There will be pressure. There will be uncertainty. There will be things that break for stupid reasons. There will also be things that break for extremely complicated reasons, which is way worse because you cannot even digest the problem properly. No worries, all of us are sometimes figuring out things as we go.
What We Expect From You
Solutions, not complaints. You are allowed to say something is broken, stupid, inefficient, overengineered, unreliable, or complete bullshit. But after saying it, we expect you to tell the reason that is sound and then improve it.
When you fuck something up - and eventually you will, because everyone does - we expect you to own it. No hiding. No blaming the infrastructure, the documentation, Mercury retrograde, or not enough caffeine in your body. Just tell us what happened, what the impact is, how you are fixing it, and how we will prevent it from happening again. That’s it.
Your Experience
You should have experience with, or at least a solid working understanding of:
Shell scripting;
Linux-based systems and subsystems;
Docker;
Containers and service deployment;
Git;
Configuration management;
Logs, monitoring, and debugging;
API integrations;
Data pipelines;
Feed processing;
System reliability;
Performance optimization.
Nothing mentioned is strictly mandatory or a requirement on day one. However, we use it, so you will learn it.
Security and API Knowledge
You should understand why signing a request matters, why a nonce exists, and why blindly trusting data received from an external system is a fantastic way to ruin your week.
Knowledge of post-quantum cryptography is a major advantage. Knowledge of secure transfer protocols, hybrid encryption, key management, or cryptographic integrations is also highly valuable.
Programming Languages
We work primarily with:
Go
C
PHP
Experience with any of these is a significant advantage.
You should be capable of understanding what the code is doing, identifying where things are going wrong, making corrections, and discussing the consequences of those changes.
You may need to write production code.
You may need to modify existing services.
You may need to debug something written by a person who believed comments were a sign of weakness.
Welcome to engineering.
Disclaimer
We care deeply about performance and reliability. We like systems that are fast, understandable, stable, observable, and simple enough that another human being can operate them.
If your solution to every problem is adding three new services, two databases, a message broker, seventeen abstractions, and a Kubernetes cluster, please do not apply. Complexity is not intelligence.
Sometimes the smartest engineering decision is deleting half the bullshit.
What You Will Work On
Your work may include:
Designing and developing internal and external APIs;
Building data pipelines and communication layers;
Creating communication systems for satellite-related applications;
Processing data connected to Copernicus and Sentinel services;
Designing encryption-transition and hybrid cryptographic solutions;
Creating monitoring software for space-related applications;
Improving observability across our platforms;
Debugging infrastructure and application failures;
Investigating networking, configuration, and deployment issues;
Improving system performance and reliability;
Removing unnecessary complexity;
Building integrations between APIs, cloud systems, external feeds, software platforms, and specialized infrastructure.
This means that one day you may be configuring infrastructure. The next day, you may need to debug an existing Go service. Then you may be reviewing an API-signing mechanism, processing satellite data, investigating a memory leak, or asking why one service requires six different configuration formats to start.
Is This Role for you?
This role is for you if:
You enjoy solving difficult technical problems;
You are comfortable moving between infrastructure and code;
You can read unfamiliar systems and gradually make sense of them;
You take ownership;
You admit when you do not know something;
You do not need constant supervision;
You prefer practical solutions over fashionable nonsense.
Do not apply if:
You want a narrowly defined DevOps role limited to CI/CD and cloud configuration;
You need every task broken into tiny instructions;
You cannot accept direct feedback;
You believe every disagreement is a personal attack;
You enjoy discussing problems more than solving them;
You want predictable work with minimal responsibility.
Also, do not apply because “space” sounds cool. It is cool. But most of the time it involves debugging, reading documentation, analysing data, designing reliable systems, and discovering that one tiny configuration value has been ruining your life since last week.
A Note About Pressure
We are not going to sell you a fantasy. There may be production incidents. There may be urgent problems. There may be occasions when systems need attention outside normal working hours.
However, we are not interested in destroying good engineers through preventable chaos. The goal is not to spend every Sunday night debugging at 3 a.m. But when things do go wrong, we need someone who stays calm, thinks clearly, communicates honestly, and helps solve the problem.
Swearing at the terminal is optional. Although realistically, it may happen.
Summary
This role is demanding. You will be challenged technically and personally. You will receive direct feedback. You will work on problems that may initially appear impossible. Sometimes your solution will fail, and you will have to try again.
But you will also have the opportunity to work on unusual systems, difficult engineering challenges, satellite-related technologies, secure communications, industrial platforms, and problems that most engineers will never encounter.
You are not expected to know everything.
You are expected to give a shit.
You are expected to learn.
You are expected to think.
You are expected to take responsibility.
And you are expected to help us build systems that actually fucking work.
If that sounds exciting, apply. If it sounds terrifying, that is also a reasonable reaction. Apply anyway - unless you already know this is not for you.