Google Network Engineer (Entry Level) Interview Preparation Guide

Network Engineer

Google

entry

6 rounds

Updated 6/13/2026

Google's network engineer interview process for entry-level candidates typically consists of a recruiter screening phase, followed by 1-2 technical phone screens focusing on networking fundamentals and troubleshooting, and 4-5 onsite rounds covering technical networking depth, practical troubleshooting scenarios, network design basics, and behavioral/culture fit assessment. The process evaluates foundational networking knowledge, problem-solving ability, communication skills, and alignment with Google's collaborative culture.

Interview Rounds

Recruiter Screening

30 min3 focus topicsculture fit

Technical Phone Screen - Networking Fundamentals

45 min5 focus topicstechnical

What to Expect

First technical interview conducted over phone or video with a Google network engineer. This round focuses on foundational networking concepts, TCP/IP stack, addressing, routing basics, and your understanding of core protocols. You may be asked to explain networking concepts, work through simple network scenarios, or discuss how you've applied these concepts in past work or learning. This assesses your baseline technical knowledge and communication ability.

Tips & Advice

Review OSI model layers, TCP/IP stack, IPv4/IPv6 addressing, subnetting, routing concepts (static vs dynamic), and common protocols (TCP, UDP, DNS, DHCP, ARP). Be ready to explain network concepts clearly and ask clarifying questions if a scenario is unclear. Use a whiteboard or notepad to sketch network diagrams while explaining. For entry-level, focus on explaining fundamental concepts correctly rather than advanced optimization. Reference the job description: be ready to discuss how you understand network infrastructure design, protocols, and basic troubleshooting.

Focus Topics

Network Design Concepts

Understand basic network architecture concepts like LAN, WAN, VLANs, network segmentation, redundancy, and how these relate to reliability and scalability.

Practice Interview

Study Questions

Basic Network Troubleshooting Tools

Know common Linux/Unix networking tools like ping, traceroute, netstat, ss, ifconfig/ip, dig, nslookup, arp, and tcpdump. Understand what each tool shows and when to use it.

Practice Interview

Study Questions

Routing Fundamentals

Understand static routing, dynamic routing basics (distance-vector vs link-state), routing tables, default gateways, and how routers forward packets. Know concepts like convergence and metric.

Practice Interview

Study Questions

IPv4 Addressing and Subnetting

Master IPv4 address classes, subnet masks, CIDR notation, calculating network/broadcast addresses, and determining host ranges. Understand private vs public IP ranges and special-use addresses.[1]

Practice Interview

Study Questions

OSI Model and TCP/IP Stack

Understand the 7 layers of the OSI model and the TCP/IP model, including the protocols at each layer and how data flows through layers. Know common protocols like TCP, UDP, IP, ICMP, DNS, DHCP, ARP, and HTTP/HTTPS.

Practice Interview

Study Questions

Technical Phone Screen - Network Troubleshooting and Problem-Solving

45 min5 focus topicstechnical

What to Expect

Second technical phone interview focusing on practical troubleshooting scenarios and problem-solving methodology. You'll be presented with network connectivity or performance issues and asked to diagnose the problem methodically. This assesses your troubleshooting approach, logical thinking, ability to ask clarifying questions, and understanding of common network failure modes. The goal is to see how you apply foundational knowledge to real-world scenarios, not necessarily to arrive at the 'correct' answer quickly.

Tips & Advice

When presented with a troubleshooting scenario, start by gathering information: ask what symptoms are being observed, what was working before, what changed. Use a systematic approach—work from Layer 1 upward or follow the network path. Ask clarifying questions about the environment (VLANs, firewalls, NAT, cloud vs on-prem). Explain your reasoning aloud so the interviewer understands your methodology. Don't jump to conclusions; rule out possibilities methodically. Reference the search results[1] which show common troubleshooting patterns: IP connectivity issues, service port accessibility, DNS resolution failures, routing to specific subnets, inter-VLAN communication, and application-level issues.

Focus Topics

VLAN and Layer-2 Issues

Understand VLAN basics, inter-VLAN routing configuration, trunk vs access ports, VLAN tagging, and how to troubleshoot communication failures between VLANs. Know when to check port assignments and router interfaces.[1]

Practice Interview

Study Questions

Service and Application Connectivity Issues

Differentiate between network-level problems and application-level issues. Know how to verify service listening (ss -lntp), check port binding, validate load balancer configuration, and understand when to involve application teams.[1]

Practice Interview

Study Questions

DNS Troubleshooting

Understand DNS resolution flow, know how to test DNS with dig and getent commands, differentiate between DNS failures and other connectivity issues, identify resolver configuration issues via /etc/nsswitch.conf, and diagnose when DNS works but applications fail.[1]

Practice Interview

Study Questions

Routing and Path Issues

Diagnose missing routes, overlapping CIDRs, policy-based routing issues, and understand how to use 'ip route' command to view and troubleshoot routing. Identify when selective routing failures occur.[1]

Practice Interview

Study Questions

Connectivity Troubleshooting Methodology

Systematic approach to diagnosing connectivity issues: verify local configuration (IP, gateway), check layer-2 connectivity (ARP, MAC), test layer-3 routing, verify service listening on correct port, and rule out firewall/NAT issues. Know when to use ping, traceroute, arp, netstat, and ss.[1]

Practice Interview

Study Questions

Onsite Interview 1 - Network Infrastructure Design and Protocols

60 min5 focus topicstechnical

What to Expect

In-person or video interview with a senior network engineer or infrastructure architect. This round assesses deeper understanding of network infrastructure design, protocol choices, and architectural thinking at a basic level. You'll discuss designing simple network topologies, selecting appropriate protocols and technologies for scenarios, understanding performance and reliability trade-offs, and explaining your design reasoning. This evaluates whether you understand how individual network components work together and can think about infrastructure holistically, not just individual device configuration.

Tips & Advice

Prepare by understanding network design trade-offs: redundancy vs cost, performance vs complexity, security vs usability. Be ready to discuss when to use different technologies: static vs dynamic routing, VLAN vs subnet segmentation, L3 switching vs separate routers. Draw network diagrams and explain your reasoning. For entry-level, focus on explaining fundamental design decisions (e.g., why use OSPF over static routing) rather than complex optimization. Discuss the job responsibilities: how would you design network infrastructure for reliability, security, and scalability? Reference Google's emphasis on infrastructure reliability. Ask clarifying questions about requirements before proposing designs.

Focus Topics

IP Addressing Strategy and IPAM

Design addressing schemes using subnetting and hierarchical addressing. Understand IPAM (IP Address Management) concepts, address space planning, and how addressing scales with network growth.

Practice Interview

Study Questions

Switching and VLAN Architecture

Understand switched network design, VLAN architecture for segmentation, trunk port design, spanning tree basics for preventing loops, and Layer 3 switching. Know how switches provide scalability and segmentation.

Practice Interview

Study Questions

Network Security Fundamentals in Design

Understand how firewalls fit into network design, DMZ concepts, network segmentation for security, ACL basics, and how security considerations influence architecture. Know the job requirement to implement network security measures.

Practice Interview

Study Questions

Routing Protocol Selection

Understand characteristics of different routing protocols: static routing, RIP, OSPF, BGP. Know when to use each based on network size, complexity, and convergence requirements. Discuss metrics, cost, and scalability.

Practice Interview

Study Questions

Network Topology Design Principles

Understand basic network topologies (star, mesh, hybrid), their advantages and disadvantages. Know when to use redundancy, failover mechanisms, and how topology affects reliability and scalability.

Practice Interview

Study Questions

Onsite Interview 2 - Advanced Troubleshooting and Performance Monitoring

60 min5 focus topicstechnical

What to Expect

Interview with a network operations engineer or performance specialist. This round combines challenging troubleshooting scenarios with discussion of network monitoring, performance analysis, and operational metrics. You'll work through complex multi-layer issues that require synthesizing knowledge across protocols, tools, and infrastructure. The interview also assesses your understanding of network performance monitoring requirements and how to measure network health. This evaluates problem-solving depth, ability to handle ambiguity, and understanding of operational requirements.

Tips & Advice

Prepare for complex scenarios combining multiple failure modes (e.g., intermittent connectivity that turns out to be MTU issues, or DNS working for some clients but not others). Approach systematically but be willing to pivot when new information changes your hypothesis. Discuss monitoring: what metrics matter (latency, jitter, packet loss, throughput), what tools to use (NetFlow, sFlow, SNMP, packet analysis), and how to detect problems proactively. Reference the job responsibility for monitoring network performance and traffic. Be comfortable discussing tools like Wireshark for packet analysis, NetFlow for traffic analytics, and SNMP for device monitoring. For entry-level, show that you understand the 'why' behind monitoring rather than just 'what to measure.'

Focus Topics

Capacity Planning and Network Growth

Understand how to plan for network growth: monitoring utilization trends, predicting when upgrades are needed, understanding bottlenecks, and planning expansion. Link to the job responsibility of capacity planning.

Practice Interview

Study Questions

Packet Analysis and Protocol Inspection

Understand how to capture and analyze packets using Wireshark or tcpdump. Know how to interpret packet headers, identify protocol anomalies, and use packet analysis to diagnose issues like DNS failures, TCP retransmissions, or protocol-specific problems.

Practice Interview

Study Questions

Network Performance Analysis and Metrics

Understand key performance metrics: latency, jitter, packet loss, throughput, and how they relate to user experience. Know tools for measuring performance: ping, iperf, traceroute with latency analysis, and understanding when performance is inadequate.

Practice Interview

Study Questions

Network Monitoring and Observability

Understand monitoring approaches: SNMP for device metrics, NetFlow/sFlow for traffic analysis, packet capture and analysis with tcpdump/Wireshark, and syslog for event logging. Know what each tool provides and limitations.

Practice Interview

Study Questions

Complex Multi-Layer Troubleshooting Scenarios

Diagnose issues that span multiple network layers or combine multiple failure modes. Practice scenarios like MTU issues in tunnels, packet fragmentation problems, performance issues with specific traffic types, and intermittent connectivity. Know when to involve application teams.

Practice Interview

Study Questions

Onsite Interview 3 - Network Security, Configuration, and Behavioral

75 min6 focus topicstechnical|behavioral

What to Expect

This round combines technical assessment of network security and device configuration practices with behavioral evaluation. A network security specialist or senior engineer will assess your understanding of firewall concepts, access control, security best practices, and how you configure network equipment securely. Additionally, a Google team member will conduct a behavioral interview using Google's standard framework to assess collaboration, teamwork, communication, learning ability, and cultural fit. The behavioral portion uses the STAR method and asks about your past experiences demonstrating these qualities.

Tips & Advice

For the technical portion: Study firewall concepts (stateful vs stateless filtering, ACLs, NAT/PAT), understand basic cryptography (why encryption matters), know security hardening practices (least privilege, default deny, logging), and be ready to discuss how to configure network equipment securely. Reference the job requirement to implement network security measures. For behavioral: Prepare 5-6 stories using the STAR method about times you collaborated with teammates, learned something new, solved a problem creatively, handled feedback, or dealt with ambiguity. Google values learning ability and collaboration highly for entry-level candidates. Emphasize growth mindset and willingness to learn from team members.

Focus Topics

Google Behavioral: Problem-Solving and Initiative

Discuss times you identified problems proactively, took initiative to solve them, thought creatively about solutions, and followed through. Show both technical and interpersonal problem-solving examples.[2]

Practice Interview

Study Questions

Secure Network Device Configuration

Know best practices for configuring network equipment securely: strong authentication, logging and monitoring configuration changes, disabling unnecessary services, keeping firmware updated, and using secure management protocols.

Practice Interview

Study Questions

Google Behavioral: Learning Ability and Growth Mindset

Show eagerness to learn, examples of quickly picking up new technologies or domains, adaptability to change, and ability to learn from feedback. Demonstrate intellectual curiosity about networking.[2]

Practice Interview

Study Questions

Network Access Control and Least Privilege

Understand the principle of least privilege, how to design access control policies, segmentation using firewalls/ACLs/VLANs, and verification that users/systems have only necessary access. Know why this matters for security.

Practice Interview

Study Questions

Firewall Fundamentals and ACLs

Understand stateful vs stateless firewalls, how firewalls inspect traffic, basic ACL syntax and logic, implicit deny rules, and how to write firewall rules for common scenarios. Know limitations and when firewalls alone aren't sufficient.

Practice Interview

Study Questions

Google Behavioral: Collaboration and Teamwork

Demonstrate ability to work effectively with team members, ask for help when needed, share knowledge, and contribute to team goals. Use STAR method to discuss times you collaborated cross-functionally or supported teammates.[2]

Practice Interview

Study Questions

Frequently Asked Network Engineer Interview Questions

OSI Model and TCP IP StackHardTechnical

71 practiced

Describe the end-to-end principle and how it relates to placing functionality in different OSI layers (e.g., encryption, retransmission, error checking). Provide examples where rigidly following end-to-end is beneficial and where placing functions in intermediate devices is justified.

Firewall Concepts and Rule ImplementationMediumTechnical

43 practiced

Describe common methods to detect and resolve firewall rule shadowing and rulebase bloat in a mature enterprise (10k+ rules). What metrics and tooling would you use to prioritize rules for cleanup and how would you measure the risk of removing an unused rule?

Sample Answer

**Situation & goal**In a mature enterprise with 10k+ firewall rules the goals are to remove shadowed/unused rules, reduce complexity, and maintain security posture without disrupting business traffic.

**Detection methods**- Rule hit-count analysis over sustained windows (30–90 days) using firewall logging (PAN, ASA, Check Point, FortiGate).- Shadowing detection: static analysis that finds rules never reached because earlier rules match same traffic (order-based evaluation).- Rule similarity clustering: group by source/dest/service/app to find redundant or overlapping rules.- Policy-wide simulations (test mode) using packet-capture replay or synthetic flows to see which rules would trigger.

**Tooling**- Native mgmt: Panorama, FMC, SmartConsole for baseline hit counts.- SIEM + log analytics: Splunk/ELK to aggregate flows and long-tail usage.- Policy audit tools: AlgoSec, Tufin, FireMon for shadowing and impact analysis.- Custom scripts: Python + API to correlate rule metadata, last-hit timestamp, and owner.

**Metrics to prioritize cleanup**- Last-hit timestamp and hit frequency (low priority = 0 hits 90 days).- Shadowing score (completely shadowed highest priority).- Business owner / rule age / change frequency.- Risk score = criticality of services matched (ports/applications) + whether flows traverse high-risk zones.- Complexity impact (removing rule reduces rule count/order shifts).

**Risk measurement before removal**- Simulate removal with policy simulation tools and replay historical logs to detect blocked flows.- Change-window staged removal: disable (set deny) or move to bottom and monitor for alerts for 7–30 days.- Stakeholder validation: notify owners, request pre-approved testing.- Rollback plan & automated monitoring: immediate alerts for dropped connections and SLA metrics.

**Example workflow**1. Run hit-count and shadowing reports → flag 15% rules with 0 hits + 5% fully shadowed.2. Score by business impact and exposure.3. Disable candidate rules in audit mode for 14 days; monitor logs/alerts.4. Remove after zero impact and owner sign-off; record change and update documentation.

This approach balances automation, measurable metrics, stakeholder validation, and safe staged removal to reduce bloat while minimizing business risk.

Learning Agility and Growth MindsetMediumTechnical

52 practiced

Design a 90-minute knowledge-transfer workshop for teaching advanced BGP troubleshooting to mid-level engineers. Provide a lesson outline with time boxes, a hands-on lab exercise (topology and tasks) with expected outcomes, and two assessment questions you would ask to verify participants learned the key concepts.

Sample Answer

**Workshop Title & Goal**Advanced BGP Troubleshooting — enable mid-level engineers to diagnose and fix complex BGP issues in multi-AS, iBGP/ eBGP, and route-policy environments.

**Outline (90 minutes)**- 0–10m: Introduction & learning objectives- 10–25m: Key concepts refresher (BGP path selection, attributes, route reflection, confederations, next-hop, MED, communities)- 25–40m: Common failure modes and diagnostic tools (show commands, bgp debug, traceroute, MRT)- 40–45m: Demo: reading BGP RIB/Adj-RIBs and policy effects- 45–80m: Hands-on lab (35m) — perform tasks below- 80–90m: Review, Q&A, and assessments (10m)

**Hands-on Lab**Topology:- Router R1 (AS 65001), R2 (AS 65002), R3 (AS 65002, RR), R4 (AS 65003). R2 and R3 are iBGP with RR; R3 peers eBGP to R4. R1 eBGP to R2.

Tasks:1. Observe that prefix 10.10.0.0/24 on R4 is not present on R1. Use show ip bgp, show bgp adj-rib and trace to find where it’s dropped.2. Identify if next-hop or route reflection loop prevents advertisement. Fix by adjusting next-hop-self on RR or update-route-maps.3. Simulate MED override and use community to prefer path via AS65003 -> implement and verify.

Expected outcomes:- Engineers locate the failure point via Adj-RIBs and BGP attributes.- Implement corrective config (next-hop-self, route-map, community tagging).- Validate with show ip bgp, traceroute, and traffic verification.

**Assessment Questions**1) Why might an iBGP-learned prefix not be advertised to other iBGP peers and how do you fix it? - Expected answer: iBGP split-horizon: iBGP-learned routes aren’t forwarded; use route reflection or full-mesh, or configure RR. Ensure next-hop correctness.2) You see same prefix from two eBGP neighbors but path chosen is not the one you expect. List the BGP attribute order you’d check and one config action to force the preferred path. - Expected answer: Check weight (vendor), local-pref, AS_PATH, origin, MED, eBGP over iBGP, IGP cost. To force: adjust local-pref, prepend AS_PATH, or set MED/local policy.

Network Architecture and TopologyEasyTechnical

65 practiced

List the core network metrics and telemetry you would collect to proactively detect congestion, increased packet loss, jitter, and device failure in a medium enterprise network. For each metric indicate a reasonable sampling frequency or polling interval and an example alert threshold.

Sample Answer

**Overview**As a Network Engineer I’d collect a mix of device, interface, traffic and active-probe metrics to detect congestion, packet loss, jitter and device failure early. Below are core metrics with recommended polling/probe intervals and practical alert thresholds.

- **Interface utilization (in/out bytes, % link)** - Poll: SNMP 30s–60s - Alert: > 80% sustained for 5m

- **Interface errors / CRC / FCS / frame errors / discards** - Poll: SNMP 30s - Alert: error rate > 0.1% of packets or sudden delta > baseline × 5 in 1m

- **Packet drops (device queues, output drops)** - Poll: SNMP 30s - Alert: drops > 1000/min or drop rate > 0.5% of packets

- **Queue depth and buffer utilization** - Poll: device telemetry/streaming 10s–30s - Alert: buffer > 70% for 2m

- **Latency / RTT (ICMP/TCP active probes between sites)** - Probe: 10s–30s - Alert: RTT increase > 50% of baseline or > 100ms (WAN)

- **Jitter (one-way delay variation from probes or RTP monitoring)** - Probe: 10s–30s - Alert: jitter > 30ms for 1m (VoIP-sensitive) or > baseline × 3

- **Packet loss (active probes, synthetic transactions, flow-derived)** - Probe/flow: 10s probes; NetFlow 60s exports - Alert: loss > 1% (business-critical) or > 3% general for 1m

- **TCP retransmits and session drops (from NetFlow/IPFIX or TCP metrics)** - Export: 60s - Alert: retransmit rate > 1% or sudden spike × 3

- **Device health: CPU, memory, temperature, power** - Poll: SNMP/telemetry 30s–60s - Alert: CPU > 85% for 5m, memory > 90%, temp above vendor threshold

- **Interface/Admin/Link state and flaps** - Trap/stream: immediate (event-driven) - Alert: any link down; > 3 flaps in 5m

- **Control-plane status (BGP/OSPF adjacencies, route table growth)** - Poll/trap: immediate/30s - Alert: adjacency down; route count change > 20% sudden

- **Flow-level top talkers / application breakdown (NetFlow/sFlow)** - Export: 60s–300s - Alert: single flow > 30% of link or unexpected heavy application

- **Interface latency microbursts (sFlow/telemetry per-packet counters)** - Stream: 1–10s - Alert: microburst > 100ms or queue spike above threshold

Implementation notes:- Use a mix of polling (SNMP/telemetry), streaming telemetry (gNMI, gRPC), and active probes for coverage.- Tune thresholds to baseline per-link and use anomaly detection to reduce false positives.- Correlate events: e.g., high utilization + queue depth + packet drops → congestion; CRC/errors + link flaps → physical layer issue.

Switching and VLAN FundamentalsEasyTechnical

70 practiced

What is MAC address table aging on a switch? Explain why entries are aged out, the typical default timer implications for environments with mobile endpoints (laptops, VMs), and the trade-offs involved when increasing or decreasing the aging timer.

IP Addressing and SubnettingEasyTechnical

56 practiced

Given the IPv4 network example 192.168.10.0 with netmask 255.255.255.192, calculate the CIDR prefix length, the number of usable hosts per subnet, the block size, and show the network and broadcast addresses for the first two subnets. Explain the method you used.

Routing Fundamentals and ProtocolsEasyTechnical

80 practiced

Explain the concept of administrative distance (AD). Provide typical AD values for common route sources (connected, static, OSPF, EIGRP, RIP, BGP) and describe how AD influences route selection when the same prefix is learned from multiple protocols. Give a simple example showing how changing AD can make an OSPF-learned route preferred over a static route.

Sample Answer

**What AD is (brief)** Administrative distance (AD) is a router's trust metric for route sources. Lower AD = more trusted. When multiple protocols advertise the same prefix, the router installs the route with the lowest AD into the routing table; AD is considered before route metric.

**Typical AD values** - Connected: 0 - Static: 1 (unless configured with a different AD) - eBGP: 20 - EIGRP (internal): 90 - OSPF: 110 - IS-IS: 115 - RIP: 120 - EIGRP (external): 170 - iBGP: 200

**How AD influences selection** - Router compares ADs of candidate routes for a prefix. - If ADs tie, uses next tiebreaker (e.g., metric). - AD lets you prefer one protocol's routes over another regardless of their metric.

**Simple example** Scenario: Router learns 10.1.1.0/24 from OSPF (AD 110) and also has a static route to that network (AD 1). By default the static is chosen.

To make OSPF preferred, change the static route’s AD to a higher value (e.g., 250):

shell

! original static (preferred by default)
ip route 10.1.1.0 255.255.255.0 192.0.2.1

! change AD so OSPF (110) wins
no ip route 10.1.1.0 255.255.255.0 192.0.2.1
ip route 10.1.1.0 255.255.255.0 192.0.2.1 250

Result: Router installs the OSPF-learned route (AD 110) because 110 < 250.

**Best practice** Use AD adjustments sparingly—prefer route redistribution or policy-based solutions for complex scenarios and document any AD overrides.

Network Troubleshooting and ToolsMediumTechnical

98 practiced

Users can browse small webpages but large file downloads over HTTPS time out or fail. Explain how you would diagnose a path MTU issue: which ping, tracepath, and tcpdump commands you would run, how you would interpret ICMP 'fragmentation needed' messages, and short-term and permanent mitigations (MSS clamping, MTU changes).

Sample Answer

**Approach summary**Diagnose by reproducing the issue with DF (don't fragment) probes, mapping path MTU with tracepath/traceroute, and capturing ICMP Type 3 Code 4 with tcpdump. Use findings to apply short-term MSS clamping and long-term MTU fixes.

**Commands to run**- Ping with DF to find max packet that survives:

bash

# Linux: set DF, increase size until failure
ping -M do -s 1472 target.example.com
# (1472 + 28 IP/ICMP header = 1500)

- tracepath (auto PMTU discovery):

bash

tracepath target.example.com

- traceroute with MTU info (option varies):

bash

traceroute -F -n target.example.com

- Capture ICMP fragmentation-needed messages on client/server/router:

bash

sudo tcpdump -i eth0 -n 'icmp[0]==3 and icmp[1]==4' -vv
# or for IPv6: 'icmp6 and ip6[40]==2'

**How to interpret ICMP 'fragmentation needed'**- ICMP Type 3 Code 4 indicates an intermediate hop wants to drop the packet because DF was set and the next hop MTU is smaller. The ICMP payload includes the MTU of the next hop (often in the 'next-hop MTU' field). If you see repeated Code 4 from a hop with MTU X, that is the bottleneck PMTU.

**Diagnosis workflow**- Run tracepath to identify the hop where MTU decreases.- Use ping -M do with sizes below and above the reported MTU to confirm.- Verify tcpdump shows ICMP Type 3 Code 4 from that hop; confirm returned MTU field matches tracepath/ping behavior.

**Mitigations**- Short-term: apply MSS clamping on the gateway/firewall to reduce TCP MSS (e.g., clamp to 1400) so TCP connections never send segments requiring fragmentation: - On iptables:

bash

iptables -t mangle -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu

- Permanent: - Fix the device/interface MTU mismatch (reduce a too-small link MTU or raise where safe), correct VPN/encapsulation overhead (adjust MTU on VPN endpoints or use fragmentation-aware settings), or ensure routers propagate correct PMTU info and don't block ICMP. - After change, re-run tracepath/ping to verify.

**Notes / pitfalls**- Firewalls blocking ICMP will break PMTU discovery — allow ICMP Type 3 Code 4.- For HTTPS large downloads, retries/slow-start may mask issue; reproduce with iperf or wget with large files.

Network Troubleshooting MethodologyMediumTechnical

73 practiced

Design a systematic approach to determine whether an observed packet loss is caused by a faulty network interface, a misconfigured switch port (e.g., rate limiting), or a downstream application server. Describe tests at the NIC, switch, and server levels including interface counters, ethtool statistics, port-speed/duplex, queue drops, and server application logging.

Sample Answer

**Approach overview**Start narrow-to-wide: test NIC (host), then switch port, then server application. At each level gather objective counters, run active tests, interpret results, and escalate.

**1) NIC-level tests (host)**- Check interface counters and errors:

bash

ip -s link show eth0
ethtool -S eth0
ethtool eth0

- Look for RX/TX errors, dropped frames, FCS, overruns, and hardware queue drops. Verify negotiated speed/duplex via:

bash

ethtool eth0 | grep -E "Speed|Duplex|Link detected"

- Active test: run iperf3 to a known-good peer on same switch to isolate link:

bash

iperf3 -c <peer> -t 60 -P 4

Interpretation: persistent CRC/FCS, length errors, or overruns → NIC or driver; mismatched duplex/speed → config issue.

**2) Switch port tests**- Check port counters (switch CLI or SNMP): input/output errors, CRC, symbol errors, interface drops, queue drops, tail drops.- Verify port speed/duplex, rate-limits, ingress/egress policing and QoS queue stats. Example (Cisco-like):

text

show interfaces GigabitEthernet1/0/10 counters errors
show policy-map interface Gi1/0/10
show platform queue stats interface Gi1/0/10

- Active test: mirror problematic traffic to analyzer or run iperf between host and another port while changing switch port (move cable) to a known-good port.Interpretation: queue drops or policer hits → port config (rate-limit/QoS). CRC on both switch and host → physical layer issue (bad SFP/cable).

**3) Server/application-level tests**- Correlate application logs (timeouts, retries) with host kernel drops:

bash

dmesg | grep -i eth0
ss -s
sudo journalctl -u myapp

- Check socket errno, application-level queue full errors, accept backlog, or thread starvation. Run a loopback/local iperf to separate network from app.Interpretation: if kernel shows no loss but app logs show processing delays/queue overflows → application bottleneck (CPU, thread pool, garbage collection).

**Decision logic & next steps**- NIC errors only on host → replace NIC/SFP/cable; update driver/firmware.- Switch shows policing/queue drops but host hardware counters clean → adjust rate-limit/QoS, increase buffers, or move traffic class.- No network-level errors, app logs show drops/timeouts → profile app, increase socket buffers, fix thread or backend latency.- If ambiguous: capture pcap at host and mirrored switch port to correlate where packets are lost.

Experience note: automate baseline counter collection and timestamped correlation across host, switch, and app logs to speed RCA.

OSI Model and TCP IP StackHardTechnical

67 practiced

How does TCP fast open (TFO) interact with middleboxes that expect a standard three-way handshake? Explain the OSI-layer risks and what fallback behaviors should be implemented when middleboxes block or modify TFO traffic.

Practice Network Engineer questions across all topics

Want to create your own tailored preparation guide using our deep research?

Get Started for Free

Interview-Ready Courses

Visual-first, interactive, structured learning paths

Browse Network Engineer jobs

AI-enriched listings across hundreds of company career pages

Explore Jobs

Google Network Engineer (Entry Level) Interview Preparation Guide

Interview Process Overview

Interview Rounds

Recruiter Screening

What to Expect

Tips & Advice

Focus Topics

Questions to Ask About the Role

Practice Interview

Study Questions

Communication and Professionalism

Practice Interview

Study Questions

Background and Motivation

Practice Interview

Study Questions

Technical Phone Screen - Networking Fundamentals

What to Expect

Tips & Advice

Focus Topics

Network Design Concepts

Practice Interview

Study Questions

Basic Network Troubleshooting Tools

Practice Interview

Study Questions

Routing Fundamentals

Practice Interview

Study Questions

IPv4 Addressing and Subnetting

Practice Interview

Study Questions

OSI Model and TCP/IP Stack

Practice Interview

Study Questions

Technical Phone Screen - Network Troubleshooting and Problem-Solving

What to Expect

Tips & Advice

Focus Topics

VLAN and Layer-2 Issues

Practice Interview

Study Questions

Service and Application Connectivity Issues

Practice Interview

Study Questions

DNS Troubleshooting

Practice Interview

Study Questions

Routing and Path Issues

Practice Interview

Study Questions

Connectivity Troubleshooting Methodology

Practice Interview

Study Questions

Onsite Interview 1 - Network Infrastructure Design and Protocols

What to Expect

Tips & Advice

Focus Topics

IP Addressing Strategy and IPAM

Practice Interview

Study Questions

Switching and VLAN Architecture

Practice Interview

Study Questions

Network Security Fundamentals in Design

Practice Interview

Study Questions

Routing Protocol Selection

Practice Interview

Study Questions

Network Topology Design Principles

Practice Interview

Study Questions

Onsite Interview 2 - Advanced Troubleshooting and Performance Monitoring

What to Expect

Tips & Advice

Focus Topics

Capacity Planning and Network Growth

Practice Interview

Study Questions