DevOps Engineer (Proxy)

✅DevOps Engineer (Proxy) #vacancy #DevOps

Remote, Flexible working hours, Four-Day Work Week

Overview
We're SOAX, a proxy infrastructure company with a product customers genuinely love and depend on. Our system is a geo-distributed, high-load platform written in Go, handling HTTP/HTTPS/SOCKS5/TCP/UDP traffic across millions of nodes worldwide. Customers pay us real money. The product works.

The DevOps side? It needs serious rebuilding.

We passed the MVP stage, grew fast, and now our infrastructure needs to catch up with the product. We're looking for someone who gets excited by that challenge — not someone who wants to draw architecture diagrams and delegate everything, but someone who will SSH into a box at 2 AM, find the root cause, fix it, and then build the system so it never happens again.

✅What you're walking into
- A geo-distributed system that routes proxy traffic across bare-metal and cloud nodes globally
- Low-level networking challenges: routing, load balancing, protocol-level debugging, traffic optimization
- Infrastructure that works but needs to be professionalized: monitoring, alerting, CI/CD, IaC — all need leveling up
- A small, tight team where your impact is immediately visible
- 24/7 on-call rotation (you won't be alone — but yes, this is real and we won't sugarcoat it)

✅What you'll actually do
• Troubleshoot and fix things. Incidents happen. You dig in, find root causes, and resolve them. Not "coordinate the response" — actually do the work.
• Rebuild infrastructure properly. Take what we have and make it production-grade: monitoring, alerting, deployment pipelines, disaster recovery.
• Own the roadmap. Once you understand the system, define what needs to happen and in what order. Then execute it.
• Work at the network level. Debug packet flows, optimize routing, understand why latency spikes between nodes in different regions. This is not a "deploy containers and forget" role.
• Automate everything that should be automated. If you're doing something manually twice, build a system for it.

✅What we need from you
Must have:
• 3+ years hands-on in DevOps / SRE / Infrastructure Engineering (we care about depth, not title inflation)
• Strong networking fundamentals: you can explain how a packet travels from client to proxy to target and back, and debug when it doesn't
• Real experience with: routing, load balancing, DNS, TLS/SSL, proxy protocols
• Kubernetes on bare metal (not just managed cloud K8s)
• Infrastructure as Code: Terraform, Ansible, or similar
• Monitoring and observability: Prometheus, Grafana, alerting pipelines — you've built these from scratch
• Comfort with bare-metal servers
• You've been on-call before and didn't hate it (or at least understood why it matters)

Strong plus:
• Experience with proxy technologies, traffic routing at scale, or CDN/edge infrastructure
• Hands-on with (self-hosted, not managed): ClickHouse, Redis, Kafka, MySQL, MongoDB
• Experience building or significantly improving SRE practices

What we're NOT looking for
• Someone who wants to "lead" without getting their hands dirty
• Someone who's only worked with managed cloud services and never touched a bare metal

✅What we offer
• A real path from engineer to Lead / Head of Infrastructure — not a vague promise, but a concrete growth trajectory based on impact
• Direct collaboration with the CTO — your voice matters in technical decisions
• Ownership. This is your infrastructure to rebuild and run.
• A team culture where mistakes are learning opportunities, not blame games. Our core value: "It's not the mistake that characterizes the system, but the reaction to the mistake."
• Competitive compensation in GBP
• Remote-first, distributed team

✅How to apply
Skip the generic cover letter. Instead, tell us:
1. The hardest infrastructure incident you've debugged. What broke, how you found it, and what you did so it wouldn't happen again.
2. Why this role — what about messy, real-world infrastructure excites you more than a polished big-company SRE job?

📩 Показать контакты