Brightcove logo

Brightcove Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 11 interview experiences · FREE TO READ

3.8 Rounds average
Average Typical difficulty
54.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Brightcove.

Showing 3 of 11
Brightcove logo
Brightcove

Software Engineer

Engineering · more than a year ago

Entry Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

The process was short, which was great. I usually hear about bait and switch tactics with pay ranges, but this was my first time experiencing it. After being reached out to and reviewing the job post, I scheduled a call. The recruiter was nice enough, but then they told me the budget for the role was almost 30K lower than the pay transparency range. They said that was the 'range' and it's separate from the budget. I didn't continue because it would have been a 25K pay cut for me. I'm still surprised how the 'range' and 'budget' can be different, especially since pay transparency laws are meant to tell you what a company would reasonably pay. I live in a high-cost area (California) and figured I'd qualify for at least the top third of the range, and I wasn't even asking for the top. Sounds like HR fed them some talking points. It's odd because when I asked my company (which hires remotely across the US) about this, they said our budget is our budget. So, something is off here, be careful.

Confirmed questions3 questions
  • Can you tell me about your background?
  • What projects have you worked on in the past?
  • Which programming languages are you proficient with?
Brightcove logo
Brightcove

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience No offer 5 rounds
Interview process
Take home Phone screen Technical screen Onsite Background check
Interview formats
Coding Technical Behavioral Technical Coding Technical

So, the first thing was this take-home coding test where they give you a basic react app template and you gotta show data from a form (username, age, gender) after submitting it, with some sorting. Then, I had a call with the tech lead for the team. He talked about what they do and asked some easy technical stuff like how to center a div and about my accessibility experience. He was super nice, gave me a good feeling about the job. After that, it was three back-to-back half-hour interviews with different people from the team. The first one was with someone from testing, we talked about some behavioral questions and did some simple JavaScript trivia. The second round involved live coding with a couple of devs – they wanted me to get data from an API and show it, and also build a basic responsive website with divs and CSS. The last interview was with the team manager, who hit me with some harder JavaScript questions about closures and sync/async stuff. I kinda tanked that one but thought the questions were great. Overall, it was a solid interview process, felt relevant and the interviewers were all friendly and welcoming. The only bummer is that after it all, I got ghosted. No one followed up about the job status, even though they said they would.

Confirmed questions5 questions
  • Regarding this code snippet: console.log("first") setTimeout(() => {console.log("second")}, 0) for(var i =0; i < 100; i++) { console.log("third")}, what output do you expect and explain the reasoning?
  • For basic JS trivia, what is the result of console.log(false == "0")?
  • For basic JS trivia, what is the result of console.log(false === "0")?
Brightcove logo
Brightcove

Software Engineer

Engineering

Senior Difficult Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Presentation Background check Offer
Interview formats
Technical Coding System Design Behavioral Presentation

The interview process was great, mainly featuring practical coding challenges and discussions about my past work. I had conversations with several future teammates who thoroughly explained the project I would be joining. Additionally, I had a more relaxed chat with senior company leaders, allowing me to ask broader strategic questions.

Confirmed questions1 question
  • Could you describe how you would architect system X leveraging cloud services?

Brightcove Software Engineer Interview Questions

Quoted word for word from Brightcove interview reports.

For basic JS trivia, what is the result of console.log(false == "0")?

Read reports

For basic JS trivia, what is the result of console.log(3>2>1)?

Read reports

Regarding this code snippet: console.log("first") setTimeout(() => {console.log("second")}, 0) for(var i =0; i < 100; i++) { console.log("third")}, what output do you expect and explain the reasoning?

Read reports

Can you explain web technologies like JavaScript, CSS, and HTML?

Read report

Could you describe how you would architect system X leveraging cloud services?

Read report

Formats, difficulty and experience

Across all 11 Brightcove interview reports.

Interview formats

Behavioral 30.3%
Technical 30.3%
Coding 24.2%
Presentation 6.1%
System Design 6.1%

Interview difficulty

Easy 0%
Average 72.7%
Difficult 27.3%

Candidate experience

Positive 54.5%
Negative 27.3%
Neutral 18.2%