A live autonomous system
AS203136 announces 185.143.176.0/22 through three upstream operators, with an RPKI ROA. BGP here is not an exercise — it runs, and a mistake in it is visible.
careers
The infrastructure we work on is our own
Nobody draws BGP on a slide here — it runs on a live autonomous system. Below is what engineering here actually involves, how hiring runs, and how to apply even when no vacancy is open.
the reality
What working here means
Six concrete facts about the work. We leave the adjectives to companies with nothing else to say.
An own datacenter
Cisco, Juniper and Arista hardware, KVM virtualization and a hosting platform — infrastructure you can physically reach, not just a client's remote access.
IPTV and an access network
A fibre access network, PPPoE and an IPTV platform: multicast, stream ingest and distribution to real subscribers.
An EVE-NG lab
A migration fails in the lab first. Rebuilding a topology, simulating the failure and testing the rollback is part of the job, not a personal side project.
A writing standard
Every technical claim is marked proven or capability, and a number is published only after it is measured. The same rule applies to internal documentation.
Ownership and on-call
An engineer owns engagements and takes part in the on-call rotation. The escalation tiers are defined in advance — nobody is left alone with a night incident.
disciplines
Where engineers are needed
The team is organised into five disciplines. A speculative application to any of them is welcome — say which one is yours.
01
Network engineering
- BGP
- OSPF
- MPLS
- RPKI
- SD-WAN
02
Datacenter & virtualization
- KVM
- Proxmox
- VMware
- Ansible
- RAID 10
03
Observability
- Prometheus
- Grafana
- Zabbix
- gNMI
- Akvorado
04
Logging & security
- Graylog
- Wazuh
- MFA
- RBAC
- syslog
05
Software engineering
- API
- Docker
- CI/CD
- Ansible
The full description of each discipline and the escalation model is on the team page.
process
Hiring in five steps
You speak to engineers at every stage. The number of stages does not grow by "one more call".
01
Application
A CV plus a short description of one network or system you built or fixed. Lab configurations, scripts or a repository are welcome.
02
Technical conversation
A conversation with an engineer, not a recruiter: what you did, why that way and what broke. No trivia questions.
03
A practical lab task
An EVE-NG topology with a concrete fault. We look at the order of your diagnosis and how you write up what you found — not only the final config.
04
Meeting the team
You meet the engineers you would actually work with and we go through on-call, escalation and documentation expectations.
05
Offer and onboarding
A written offer with the full terms. Onboarding starts with access, the lab and a first engagement alongside a mentor.
open roles
Open positions
no confirmed vacancy right now
A vacancy goes up when the position is confirmed and budgeted — we do not run permanent "always looking for talented people" listings. Speculative applications, however, are genuinely read.
A speculative application
Write to us and include three things: which discipline interests you, one network or system you built or fixed, and what unexpectedly broke while you did it. Lab configurations, scripts or a repository link are welcome — a cover letter is not.
We publish no salary range here: it depends on discipline, experience and on-call load, and is discussed concretely in the first conversation.