Engineering Manager

About this role

About the role Gcore operates a global edge platform: a content delivery network, authoritative and recursive DNS, and the traffic management layer that decides where requests land. It carries production traffic for media, gaming and enterprise customers, and the difference between a good and a bad engineering decision is visible in latency and availability within minutes. We are looking for an Engineering Manager to lead the teams that build and run the CDN control plane, the edge request path, the analytics and logging pipeline, and our traffic management services. This is a leadership role with real technical weight. You will not be writing production code day to day, but you will be expected to hold your own in an architecture discussion, question a proposed fix when the evidence is thin, and own the consequences when something breaks at 3am. What You Will Do Lead four engineering teams covering the control plane, the core edge and proxy layer, the analytics and logging platform, and DNS and traffic management. Own delivery on a two-week cadence: planning, commitments, and honest reporting on what shipped and what did not. Set and defend technical priorities with Product, Support and Maintenance. A large part of the job is deciding what the teams will not do this quarter. Own the incident and post-incident process for your area: severity calls, root-cause analysis, and making sure prevention work actually gets built rather than filed and forgotten. Run the on-call rotation for your teams and keep the escalation path clear. Develop your engineers and tech leads through regular one-to-ones, feedback and growth planning, and hire well when you have headcount. Improve how the department works: planning, prioritisation, quality standards, documentation, and service ownership. Ensure AI tools and approaches are being adopted. The kind of problems you will be closer to A sense of the work rather than an exhaustive list: Cache and shielding behaviour: how a large origin is protected, and how configuration changes propagate to the edge safely. Config delivery at scale: pushing configuration to a global fleet quickly, and knowing where its limits are. Analytics cost and performance: keeping a high-volume ClickHouse estate fast and affordable. Traffic steering and failover. Observability that catches customer impact before the customer does. What We are Looking For Four or more years leading software engineering teams, including experience managing tech leads. Production experience with internet infrastructure: CDN, DNS, reverse proxies, or large-scale distributed systems. Enough depth to reason independently about HTTP caching, nginx behaviour, TLS and SNI, and anycast routing. A track record of owning incident response and post-incident follow-through, not just attending the calls. Comfort running several teams at once, and the confidence to say no to a stakeholder with a clear reason. Experience with distributed teams spanning European and Asian working hours. Nice to Have C, Rust, Go, Python, at a level where you can review a change. Prometheus, Grafana, ClickHouse and distributed tracing. Kubernetes alongside bare-metal fleet operations. Experience at a CDN, DNS or cloud provider, or at a network operator. Experience acting as product owner for platform work. What We can be Straight with You About This is a mature platform with real customers and real legacy. Some services are owned by a single engineer, and reducing that dependency is part of the job. Product ownership for platform work is currently shared between engineering and product management, which means backlog quality depends partly on you. We would rather you knew that before joining than discovered it in month two. In return you get a genuinely interesting technical domain, a small enough organisation that your decisions are visible, and direct access to the people setting product direction. Benefits At Gcore , we want you to do your best work and enjoy the journey.

Skills and categories