We're hiring a DevOps engineer at Simple Analytics!
We're preparing for a LOT more traffic, and we're looking for someone who wants to help us build the infrastructure for that.
We're a small, remote team building privacy-first analytics. For us privacy is not a marketing thing. We take it as far as running our infrastructure on our own bare-metal servers instead of using cloud providers.
We don't care that much whether you know every tool in our stack. We're much more interested in finding someone who's genuinely smart, can solve problems independently, and communicates really well.
Especially that last part. We work mostly async, and when you're responsible for critical infrastructure, communication matters a lot.
- team:
- small, remote
- communication:
- mostly async
- process:
- shape-up # we don't work with scrum
- servers:
- our own bare metal
A few things we strongly believe in:
beliefs:
- privacy: "Privacy is an architectural decision, not a legal checkbox. It determines where data lives, which dependencies we accept, and how we build our systems."
- boring_infra: "Infra should be boring. Don't chase new technologies. We want predictable systems that rarely need attention."
- self_running: "Infrastructure should run itself. The goal is to make sure you DON'T get called at 3 AM, not to become great at fixing things at 3 AM."
- config_as_code: "Configuration belongs in code, not hidden away in dashboards and UIs."
- ownership: "We prefer owning our problems over outsourcing them. Running bare metal gives us control, but also means taking full responsibility."
- ai: "AI should help you move faster, but you should understand the systems you're building."
- automation: "Automate what makes sense. Sometimes a one-click solution is better than spending days automating something."
- data_safety: "Speed matters, but losing customer data is unacceptable. You'll have the freedom and responsibility to make those trade-offs."
The job
Your first big project will be migrating our Elasticsearch infrastructure to ClickHouse, together with Alex, our developer. You'll lead infrastructure architecture, he'll lead application architecture.
./migrate.sh --from elasticsearch --to clickhouse
[scan] elasticsearch cluster found
[plan] infra_architecture → you
[plan] app_architecture → alex
[wait] missing: devops engineer
0%
tree infra/ -L 1
infra/
├── ansible/
├── opentofu/
├── grafana/
├── .github/workflows/
├── docker-compose.yml
└── # and a bunch of other tools
You'll also write TypeScript, improve our deployment pipelines, and take ownership of our production infrastructure. We use Ansible, Grafana, OpenTofu, Docker Compose, GitHub Actions, and a bunch of other tools.
Site reliability engineering is a big part of this role. You know how to monitor, prevent and mitigate potential issues with our systems.
45% of capacity
nodes 3
What matters most to us is finding someone we can trust with the infrastructure behind our entire business. Someone who takes ownership, questions existing decisions, and genuinely enjoys making systems more reliable and simpler.
The practical stuff:
- SALARY
- is "€5,000/month"
- HOURS
- is "40" # 32-hour contracts are also possible
- LOCATION
- is "anywhere"
- TIMEZONE
- is "no restrictions"
- CONTRACT_EU
- is "employment"
- CONTRACT_OUTSIDE_EU
- is "freelance"
- START
- is "asap"
If you get excited about building reliable infrastructure for a company that genuinely cares about privacy, we'd love to hear from you.
And if you know someone who would be great at this, please share!