Opera Software Frontend Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 5 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Opera Software.
Opera Software
Frontend Developer
Mid Average Positive experience No offer 4 rounds
Interview process
Recruiter call Take home Technical screen Background check Offer
Interview formats
Behavioral Technical Coding Other
A partner recruiter reached out. It was the standard international process, with an algorithm test, logic, IQ, and personality, arguably too many steps. Then, a behavioral interview with the manager and a senior developer, a live interview and technical test, and finally, an interview with the team supervisor.
Confirmed questions2 questions
- Standard behavioral questions, the important thing was fitting the profile described for the role.
- Standard technical interview, I believe it was unnecessary to have a live stage if I had already done a test before.
Opera Software
Frontend Developer
Entry Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen
Interview formats
Behavioral Technical Coding
I was approached on linkedin and scheduled an meeting with the recruiter to talk more about the opportunity. After that, there were two extensive tests on logic and personality. Then, I had a technical interview with two developers from the company, to talk about my experiences and more about the job and some technical questions. After that last interview, they told me they would have a feedback in about two weeks. After those two weeks waiting, I reached out to them asking about the feedback and they told me that the opportunity was closed, because they actually hired an intern that was already on the company. Over two months in a selective process so that on the end they don't ever bother to tell me that the job wasn't available anymore, I had to reach out to them, and they hired someone that was already working with them. I don't recommend.
Confirmed questions6 questions
- How do you measure how well an algorithm performs?
- Can you explain what the virtual DOM is and why it's significant?
- What distinguishes a list from a linked list?
Opera Software
Frontend Developer
Intern Easy Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical
It was a good interview experience, everyone was nice and welcoming. There were two parts to it: first, a quick chat with a recruiter, then a technical interview with the lead.
Confirmed questions1 question
- Can you explain to a non-technical person what happens when you type google.com in your browser and press enter? Specifically, what steps occur from hitting enter until the page is displayed?
Opera Software Frontend Engineer Interview Questions
Quoted word for word from Opera Software interview reports.
“What distinguishes a list from a linked list?”
Read reports →“What are the ways to trigger renders and how can one prevent needless rerenders?”
Read reports →“Can you explain what the virtual DOM is and why it's significant?”
Read reports →“Can you explain to a non-technical person what happens when you type google.com in your browser and press enter? Specifically, what steps occur from hitting enter until the page is displayed?”
Read reports →“How do you measure how well an algorithm performs?”
Read report →“How do you trigger renders and avoid unnecessary rerenders, and what's the difference between GPT and ChatGPT?”
Read report →“Could you describe controlled and uncontrolled components?”
Read report →“Could you explain the distinctions between GPT and ChatGPT?”
Read report →“How would you describe an ideal work environment?”
Read report →Formats, difficulty and experience
Across all 5 Opera Software interview reports.