
Bright Data Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 10 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Bright Data.
Software Developer
just awful! don't go and do the task for them ! they only want to hear what they have written on paper... other options are not considered ! This approach is simply unacceptable
- Algorithms problem solving and more
Software Developer
The hr was nice on the phone and scheduled a zoom meeting for me with the team leader, he was late by 15 minutes. When he arrived, he gave me one question without asking about myself or discussing the position or company. The question was hard (graph theory + python) and I solved it correctly in about 25 minutes while explaining it. I used a BFS algorithm and wrote clean code. About ten minutes before the meeting ended, he mentioned he had another meeting and asked me to finish the question and send it. I agreed, asking for 10 minutes to finalize the code and ensure it passed the unit tests on a LeetCode-like platform. While I was finishing up, within 10 minutes, and about to submit my answer after passing all tests, I received an email from HR stating I wasn't a good fit and they were moving on with other candidates. They didn't even let me send my code, wasting my entire hour with this interview and team leader.
- A graph theory problem that required a Python solution, found on GitHub after being initially inaccessible on Coderbyte.
Software Developer
First, there was an hour-long homework assignment with two easy LeetCode problems. Then, I had another interview with a team lead, which also involved LeetCode questions.
- The first question involved sorting.
- The second question was about short code.
Bright Data Software Engineer Interview Questions
Quoted word for word from Bright Data interview reports.
“check if input is polindrome”
Read reports →“Check if parenthesis types in a string match.”
Read reports →“Compare two strings, a and b, to determine which one comes later lexicographically.”
Read reports →“A graph theory problem that required a Python solution, found on GitHub after being initially inaccessible on Coderbyte.”
Read reports →“How would you compare two strings character by character?”
Read report →“The second question was about short code.”
Read report →“Algorithms problem solving and more”
Read report →“The first question involved sorting.”
Read report →“For the next interview round, which was a Skype call, the interviewer asked me to implement two functions, one of which was to create an object that implements a Promise.”
Read report →Formats, difficulty and experience
Across all 10 Bright Data interview reports.