← Mercor Interview Insights

Mercor·Software Engineer·Onsite - System Design / Architecture·Senior

Senior
Apr 2026

Summary

Interviewed for an Infrastructure Engineer role at Mercor and got hit with a deep Kubernetes networking question that covered basically the entire traffic routing stack. It was a single technical round and felt more like a design discussion than a quiz.

Questions Asked (1)

Q1

Walk me through how traffic is routed inside a Kubernetes cluster, from service discovery all the way to a pod receiving an external request.

System DesignTechnical Trade-offsAPI & Integrations
Author's notes

This was a lot to cover in one question.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by outlining the high-level path: external request → ingress → service → kube-proxy → pod. Then dive into each component's role, emphasizing how service discovery and load balancing work at each layer. Conclude by mentioning trade-offs and alternatives like Ingress controllers, service meshes, and CNI plugins.

Pro tip: Mention that kube-proxy in iptables mode uses random selection for load balancing, which can lead to uneven distribution, and that IPVS mode offers better performance and algorithms. This shows depth beyond basic knowledge.

1. External Request Entry

Explain how an external request reaches the cluster, typically via a LoadBalancer service or an Ingress controller. Mention DNS resolution to the external IP.

2. Service Discovery and Routing

Describe how the request hits a Service (ClusterIP) and how kube-proxy (or eBPF) intercepts and routes traffic to backend pods based on iptables/IPVS rules.

3. Pod Selection and Load Balancing

Detail how kube-proxy selects a pod from the Endpoints list, using random or round-robin algorithms, and how session affinity can be configured.

4. Pod Networking and CNI

Explain how the packet reaches the pod's network namespace via the CNI plugin (e.g., Calico, Flannel), including any overlay or underlay networking.

5. Pod Reception and Response

Describe how the pod's application receives the request on its container port, processes it, and sends a response back through the same path.

Key Points to Mention

  • Kubernetes Service types (ClusterIP, NodePort, LoadBalancer) and their differences
  • kube-proxy modes (iptables, IPVS, eBPF) and their trade-offs
  • Ingress controllers (e.g., NGINX, Traefik) and how they route HTTP/HTTPS traffic
  • CNI plugins (Calico, Flannel, Cilium) and how they handle pod-to-pod networking
  • CoreDNS for service discovery and DNS resolution within the cluster
  • Session affinity and load balancing algorithms in kube-proxy

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.