BrowserStack interview experience Real time questions & tips from candidates to crack your interview
SDE - 1
BrowserStack
2 rounds | 2 Coding
problems
Rejected
Interview preparation journey
Application story
I applied through the BrowserStack careers website and received a call from HR to schedule the interview.
I was preparing for an SDE 2 backend role but got a call for an SDE 1 role.
The first round was an introduction round, followed by a second round based on the basics of LLD.
Why selected/rejected for the role?
I was rejected because I was not able to explain the internal working of Kafka in a distributed system during a practical problem.
Preparation
Duration: 2 months
Topics: Networking, Database Fundamentals, OS, LLD
Tip 1: Prepare computer science concepts clearly with their practical applications.
Tip 2: Learn the technologies used in distributed systems.
Tip 3: Learn about Kafka and its use cases.
Application process
Where: Company Website
Eligibility: NA, (Salary package: 26 LPA)
Tip 1: Keep your tech stack at the top of your resume for better visibility.
Tip 2: Highlight your achievements clearly to make your profile stand out.
Interview rounds
01
Round
Easy
Video Call
Duration30 minutes
Interview date12 Mar 2026
Coding problem1
1. System Design
Problem approach
Tip 1: Go through basic of distributed system.
Tip 2: Go through the CAP theorem and its practical application.
Tip 3: Go through the inner working of the load balancers.
02
Round
Medium
Video Call
Duration25 minutes
Interview date20 Mar 2026
Coding problem1
This was a LLD round where I had to write working code for circuit breaker.
1. System Design
Design a Circuit Breaker mechanism that prevents cascading failures when calling an external dependency (e.g., API, DB, service).
It should:
Detect failures
Stop calls when failure threshold is reached
Recover automatically after some time
Core Functional Requirements
1. States of Circuit Breaker
The system must support three states:
CLOSED
All requests pass through
Failures are monitored
OPEN
All requests are blocked immediately
Fail-fast without calling downstream service
HALF-OPEN
Limited requests are allowed
Used to test recovery
2. Failure Handling
Track failures (exceptions, timeouts, error responses)
Maintain:
Failure count OR
Failure rate (over time window)
Transition to OPEN when:
Failure threshold is exceeded
3. Success Handling
Track successful calls
In HALF-OPEN:
If enough successes → move to CLOSED
If failure → move back to OPEN
4. Timeout Management
Each request should have a timeout
Timeout should be treated as a failure
Problem approach
Tip 1: Think in State Machine first (not classes).
Tip 2: Always address concurrency & edge cases.
Here's your problem of the day 
Solving this problem will increase your chance to get selected in this company
Skill covered: Programming
What is the best case time complexity of Bubble Sort?
Choose another skill to practice
Similar interview experiences
SDE - 1
5 rounds | 5 problems
Interviewed by BrowserStack
Selected 
5384 views
0 comments
0 upvotes
SDE - 1
2 rounds | 4 problems
Interviewed by BrowserStack
Rejected
2522 views
0 comments
0 upvotes
SDE - 1
2 rounds | 5 problems
Interviewed by BrowserStack
Rejected
3035 views
0 comments
0 upvotes
SDE - 1
4 rounds | 3 problems
Interviewed by BrowserStack
Selected 6 views
0 comments
0 upvotes
Companies with similar interview experiences
SDE - 1
5 rounds | 12 problems
Interviewed by Amazon
Selected 115614 views
24 comments
0 upvotes
SDE - 1
4 rounds | 5 problems
Interviewed by Microsoft
Selected 58630 views
5 comments
0 upvotes
SDE - 1
3 rounds | 7 problems
Interviewed by Amazon
Selected 35337 views
7 comments
0 upvotes