Python Developer — Mid-Level & Senior (Remote, Global)
Remote · Full-time · Work from anywhere
FDC Servers (AS30058) is a global IP transit and dedicated-server provider operating 100+ Tbps of network capacity across 27 PoPs. We're adding two mid-level engineers and one senior to a distributed engineering team.
We've got production systems that actually matter — real traffic, real Kubernetes clusters, real consequences when things break. We're not hiring engineers to close tickets. We're hiring people who want to understand a system, own a problem, and make things better over time.
The work is backend-heavy, the infrastructure is real, and there's room to grow into whatever you're good at.
WHAT YOU'LL ACTUALLY WORK ON The bulk of the work is building and maintaining Python/Django backend services — APIs, third-party integrations (payments, provisioning, internal tools), and the PostgreSQL and Redis layers underneath them. When something breaks in production, you'll be part of figuring out why and making sure it doesn't happen again.
We care about observability and reliability, not because it looks good on a roadmap, but because our team is small and we need systems we can trust.
Senior engineers will also shape how we build — system design, architecture decisions, code review, and raising the bar on testing and CI/CD practices.
THE STACK
Backend: Python, Django, Django REST Framework, PostgreSQL, Redis
Infrastructure: Kubernetes, Proxmox, Docker/containerd, Ansible
Tooling: GitHub, GitHub Actions
You'll also need solid footing in networking (IPv4/IPv6, DNS), TLS, caching, and reverse proxies. We're not looking for specialists in any one area — we're looking for engineers who are comfortable moving across the stack when the problem calls for it.
WHO WE'RE LOOKING FOR
Mid-level means 2–4 years of professional Python experience. You've shipped production code, you've been on the wrong end of a late-night incident, and you're ready to take on more ownership than your last role gave you.
Senior means 4–6+ years, with real production systems behind you and considered opinions about how things should be built. Not opinions from blog posts — opinions from having made calls and lived with the results.
For both levels: you're comfortable when the work crosses the application/infrastructure line. You don't wait for someone to tell you something is your problem.
English B1+ required. We're fully distributed and async communication is a real skill here. The team spans the US and Europe, so some practical overlap with those working hours helps.
APPLYING
Send your CV and written answers to the questions below to [email protected]. A strong answer here matters more than a polished CV.
• Describe a backend system you've owned in production — what it did, what broke, and what you changed.
• Walk us through how you'd structure and deploy a Django service from scratch: testing, CI/CD, environments, secrets.
• Tell us about something infrastructure-related you had to learn fast. What did you do and how did it go?
Senior candidates, add this one:
• Describe a technical decision you influenced that had long-term consequences. What tradeoffs did you weigh, and would you make the same call again?
Apply tot his job
Apply To this Job
FDC Servers (AS30058) is a global IP transit and dedicated-server provider operating 100+ Tbps of network capacity across 27 PoPs. We're adding two mid-level engineers and one senior to a distributed engineering team.
We've got production systems that actually matter — real traffic, real Kubernetes clusters, real consequences when things break. We're not hiring engineers to close tickets. We're hiring people who want to understand a system, own a problem, and make things better over time.
The work is backend-heavy, the infrastructure is real, and there's room to grow into whatever you're good at.
WHAT YOU'LL ACTUALLY WORK ON The bulk of the work is building and maintaining Python/Django backend services — APIs, third-party integrations (payments, provisioning, internal tools), and the PostgreSQL and Redis layers underneath them. When something breaks in production, you'll be part of figuring out why and making sure it doesn't happen again.
We care about observability and reliability, not because it looks good on a roadmap, but because our team is small and we need systems we can trust.
Senior engineers will also shape how we build — system design, architecture decisions, code review, and raising the bar on testing and CI/CD practices.
THE STACK
Backend: Python, Django, Django REST Framework, PostgreSQL, Redis
Infrastructure: Kubernetes, Proxmox, Docker/containerd, Ansible
Tooling: GitHub, GitHub Actions
You'll also need solid footing in networking (IPv4/IPv6, DNS), TLS, caching, and reverse proxies. We're not looking for specialists in any one area — we're looking for engineers who are comfortable moving across the stack when the problem calls for it.
WHO WE'RE LOOKING FOR
Mid-level means 2–4 years of professional Python experience. You've shipped production code, you've been on the wrong end of a late-night incident, and you're ready to take on more ownership than your last role gave you.
Senior means 4–6+ years, with real production systems behind you and considered opinions about how things should be built. Not opinions from blog posts — opinions from having made calls and lived with the results.
For both levels: you're comfortable when the work crosses the application/infrastructure line. You don't wait for someone to tell you something is your problem.
English B1+ required. We're fully distributed and async communication is a real skill here. The team spans the US and Europe, so some practical overlap with those working hours helps.
APPLYING
Send your CV and written answers to the questions below to [email protected]. A strong answer here matters more than a polished CV.
• Describe a backend system you've owned in production — what it did, what broke, and what you changed.
• Walk us through how you'd structure and deploy a Django service from scratch: testing, CI/CD, environments, secrets.
• Tell us about something infrastructure-related you had to learn fast. What did you do and how did it go?
Senior candidates, add this one:
• Describe a technical decision you influenced that had long-term consequences. What tradeoffs did you weigh, and would you make the same call again?
Apply tot his job
Apply To this Job