🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Role Overview The internet runs on data. We're the plumbing. Every AI company you've heard of has the same problem: their models are hungry, and the web is where the food is. Geonode builds the infrastructure that makes large-scale web data access actually work: residential proxy networks, scraping APIs, and the emerging layer that gives AI agents real access to the open web. We're bootstrapped, profitable, and ~30 people. No investors telling us what to build, no burn-rate anxiety, no bureaucracy. Small enough that your fingerprints will be on everything, profitable enough that you're not gambling your career on a runway. The proxy and web data industry is quietly one of the most interesting corners of tech right now,every AI lab, every data company, every agent platform needs what we build. You'll solve networking problems most engineers never get to touch. We're looking for a DevOps Engineer to own the reliability and scalability of the infrastructure that routes enormous volumes of traffic every day. What You’ll do Run and scale our containerized services: Docker and Kubernetes are your home turf; Work across our data layer: ClickHouse, Redis, MongoDB, and Postgres; Build and maintain observability with Prometheus and Grafana: if something breaks at 3am, our alerting should know before our customers do; Own backups, monitoring, and alerting end-to-end ; Ship tooling and automation in Golang and TypeScript; Work closely with our infrastructure lead and stay near the decisions that shape the platform. What We’re Looking For Deep hands-on experience with Docker, Kubernetes, and running production systems at scale; Solid experience with ClickHouse, plus Redis, MongoDB, and Postgres; Experience setting up Prometheus/Grafana stacks from scratch; Ability to write real code in Golang and/or TypeScript;Genuine understanding of how networks work: protocols, routing, what's happening under the hood, not just "I've configured nginx once"; Based/working in a European time zone. Preferred Qualifications: Experience with proxies, VPNs, or traffic routing infrastructure; Experience working on systems where network performance was the product. What We Offer? At Geonode, we believe great work deserves great rewards. Here’s a glimpse of what you can expect: Career Growth: Opportunities for advancement, leadership development, and skill-building. Work-Life Balance: Flexible schedules and generous paid time off to keep you energized. Culture of Inclusion: Join a diverse team where your voice is heard and valued. How to Apply? Submit your application via this form: https://tall-pink-f7d.notion.site/20b8821cab9082bcb6d601b49d573928?pvs=105 If you are passionate about DevOps, infrastructure, and building scalable and secure systems, we'd love to hear from you. Together, let’s redefine what’s possible. Your next big opportunity starts here!
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.