BrowserStack

Role: Fullstack Developer

College: Not Specified

Interview Date: Not Specified (experience updated April 2025)

Interview Type: Full-Time (Referral)

Result: Rejected

Difficulty: Not Specified

Rounds: 3 rounds (after HR conversation)

Topics Asked: Machine Coding (Backend: Log File Reader with WebSockets, Frontend: Pixel-perfect UI from Figma), System Design (Counting word occurrences in large files, Scaling viral applications, Alerting, Monitoring, Error Handling), Projects, Tech Stack, Behavioral Questions (Conflict with colleague/senior).

Experience:

The candidate interviewed for a Fullstack Development role through a referral. An initial HR conversation discussed current experience, projects, reasons for change, and expectations. An upcoming hiring drive was scheduled.

Round 1: Machine Coding (3.5 hours)

• Group coding round, candidates split into individual rooms.
• Two separate tasks:
• Backend Task (1.5 hours): Build a log file reader application that broadcasts real-time updates to clients using sockets.
• Frontend Task: Implement a pixel-perfect UI from a Figma design to display logs from the backend, handling specific scroll behaviors.
• This round went well, with strong positive feedback.

Round 2: Hiring Manager Interview (45 minutes)

• Introductions, discussion of previous and current projects.
• "Explain your approach to count the occurrences of a word in a text file."
• "How would that approach change if the file size scaled from a few MBs to a few GBs?" Discussion of optimization techniques, including concurrency and multithreading.
• Culture-fit questions: "Describe a time when you had a conflict with a colleague or senior."

Round 3: Director of Engineering (DOE) Interview

• Introductions, discussion of past projects and tech stack.
• "If you built an application that suddenly went viral overnight, how would you ensure it continued to function smoothly? How would you handle alerting, monitoring, and critical error cases?"
• This round went well, with positive feedback.

Final Outcome: Despite positive feedback in machine coding and Director rounds, the overall decision was a rejection. The candidate found the experience enriching, working on real-world problems under time constraints, interacting with experienced leaders, and reflecting on areas for improvement.