← Interview experiences
Got the offer

SDE 3 at F5 Networks

Difficulty
Process took
2-3 Weeks
Rounds
4
Format
Remote
Applied via
Company Website

How it went

Persistence matters, re-applying can make a difference.

What they would tell you

Persistence matters, re-applying can make a difference.

How to prepare

For coding rounds practice Dsa and Golang-specific problems

Their background

F5 Networks Title : Software Engineer III Location: Bengaluru RSU's Total CTC : 37 LPA

YOE: 4.5 Current Comp: 22 LPA Location: Bengaluru

Round by round

  1. 1

    Coding Round60 min

    Problem: Rearrange Array in Zig-Zag Fashion Given an unsorted array, reorder it so that elements follow the pattern arr[0] < arr[1] > arr[2] < arr[3] … while maintaining relative order where possible, i explained brute-force approach first, then optimized to O(n) using a single pass swap strategy Interviewer asked follow-ups on Linux commands, OS fundamentals, and networking basics

  2. 2

    Systems Design Round60 min

    One of the most interesting problems I got during my Go interview was building a Concurrent File Processor I had to design a system where multiple goroutines safely process files from a shared folder, handling synchronization, task distribution, and error management Talked a lot about goroutines and channels, and how to manage resource pools, Then the interviewer went down the rabbit hole of Redis caching, Kafka event ordering, and database performance tuning. It was one of those rounds that felt more like a deep tech discussion than a test.

  3. 3

    Managerial Round60 min

    Round 3 was honestly one of the toughest. It started casually with questions around leadership and ownership, and then quickly escalated into technical dive I had to design a rate limiter in Go using channels, talk about interface design, and handle goroutine safety. From there, it spiraled into distributed systems, where we discussed how to maintain throughput and fault tolerance at scale. The conversation also covered database optimization, Redis consistency, Kafka partitioning, Elasticsearch shard design, and even network load balancing, basically everything that keeps a large-scale backend alive and fast.

  4. 4

    HR Round60 min

    A closing round centered around compensation expectations, culture, benefits, and career path.

What came up

MediumRemote4 5 years

A candidate-reported account, lightly edited. Interview processes change by team and date.

Sources