BCE logo

BCE Interview Questions
& Process

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

Based on 21 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
47.6% Positive experience

Which role are you interviewing for?

14 roles · 21 reports

Candidate interview experiences

First-hand accounts from people who interviewed at BCE.

Showing 4 of 21
BCE logo
BCE

Quality Engineer

Engineering · nearly a year ago

Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home Onsite
Interview formats
Coding Technical Behavioral

The interview process took over a month and felt unorganized. Communication was very slow, with about two weeks between each stage. Initially, HR mentioned only two rounds, but after those were completed, they informed me about an additional round and a weekend assessment. It makes me wonder if they are genuinely looking to hire or just continuously interviewing candidates. This process definitely needs improvement.

Confirmed questions2 questions
  • Questions included coding tasks and queries related to Selenium and Cucumber.
  • The second interview was a managerial discussion covering software testing and performance testing procedures.
BCE logo
BCE

Architect

Engineering · a year ago

Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Technical Behavioral

First, I had to fill out some paperwork with my information. Then, they asked me technical questions related to architecture and the construction field, covering architectural details and codes. They also looked at my portfolio and asked questions about my past work and my five-year bachelor's degree in architecture from Cairo University. Finally, we discussed salary.

Confirmed questions1 question
  • Could you elaborate on technical aspects of architecture and the construction industry?
BCE logo
BCE

Senior Software Engineer

Engineering

Senior Average Negative experience No offer 1 round
Interview process
Recruiter call Technical screen
Interview formats
Technical Coding

The first round was a recorded session. They gave me 2 code snippets to figure out the output for each. Then, I was given a problem with a nested 2D array of objects, and the output they provided was actually wrong. It took me a bit to figure it out, and I even showed the interviewer the mistake, which they agreed with. Usually, interviewers don't want you to use built-in functions, but I'm not sure if that was the case here, so I just coded it raw. I got positive feedback the next day, but no official confirmation. Later that same day, I got negative feedback saying I took too long to solve the problem, and they expected faster resolution given my experience. It felt like a waste of an hour because the interviewer seemed unsure and couldn't even provide the correct output initially.

Confirmed questions3 questions
  • What are the outputs for these two code snippets?
  • For the nested 2D array of objects problem, the provided output was incorrect. I identified this and corrected it, coding the solution manually without built-ins. What are your thoughts on this?
  • Given my experience, why was my resolution time considered too long for this problem, especially considering the initial incorrect output provided?
BCE logo
BCE

Senior Front End Developer

Engineering

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Panel
Interview formats
Technical Coding System Design Behavioral

After clearing four rigorous rounds for the Senior Front End Developer position, I was verbally informed I was selected. However, the company then ghosted me. After several follow-ups, they finally got back to me much later saying the position wasn't open anymore. It's baffling why they'd conduct four interview rounds, wasting my time and giving me false hope, if they didn't actually intend to hire. This shows terrible hiring practices and a lack of respect for candidates. Definitely a red flag.

Confirmed questions5 questions
  • Can you discuss the differences between monoliths and microservices architectures, particularly in the context of MFE?
  • What are common MFE team topologies you've encountered or would recommend?
  • How do React hooks work and what are their benefits?

BCE Interview Questions

Quoted word for word from BCE interview reports.

What are your predictions for the future of mobile phones?

Read report

What is the purpose of SCCs, how are they created and managed, and what role do they play in controlling pod-level security settings?

Read report

What is Infrastructure as Code (IaC), and how can tools like Ansible, OpenShift, and Red Hat CloudForms be used to implement it?

Read report

Formats, difficulty and experience

Across all 21 BCE interview reports.

Interview formats

Behavioral 39.1%
Technical 32.6%
Coding 13%
Presentation 4.3%
Other 4.3%

Interview difficulty

Easy 9.5%
Average 81%
Difficult 9.5%

Candidate experience

Negative 33.3%
Neutral 19%
Positive 47.6%

Reports by job function

Engineering 12
Operations 5
Sales 2
Analytics 1
Finance 1