
Schibsted Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 13 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Schibsted.
Software Engineer
The whole thing had 4 steps. First, I talked with HR, just a quick chat. Then, I had a cultural interview with the Hiring Manager and Engineer Manager, it lasted about an hour. After that, they sent me a technical assignment, which was well-structured and explained. Finally, I had a technical interview with two senior software engineers where I had to explain my code and my approach. We also did some pair programming.
- What is your motivation for pursuing a career in software development?
- In your opinion, what are the essential skills for a junior software developer?
- Which programming languages do you have the most experience with?
Software Engineer
The recruiter contacted me first, then I had a 1h phone screen with an engineer where they asked basic algorithm questions. After that, I received a coding test to complete at home. Finally, I went through a 4+ hour onsite interview, which was a series of back-to-back interviews with no breaks. It was disappointing because the interviewers seemed to not have reviewed my CV and asked similar questions. They didn't extend an offer, which is fine, but the lack of feedback was frustrating. After multiple follow-ups, the recruiter finally mentioned that the hiring process was frozen and that they couldn't provide feedback, which was a waste of my time.
- The phone screen algorithm question asked was about insertion sort.
- The take-home exercise was to build a basic search engine.
- The f2f system design interview was about how to design a system like deliveroo and how to scale it using a whiteboard.
Software Engineer
I was contacted by an external recruiter for a Front End Developer position. After a brief chat with them, I was asked to complete a test. Initially, I was interested, but that changed when I saw the setup: a small room with a very old IBM laptop. The test involved filling out answers in Office files. One Excel file had over 600 rows to fill with "yes/no" for PHP type casting and default values. Then, there were Word files where I had to input formatted C++ code. Writing code in a word processor is not practical, especially on such an old laptop without even a mouse provided. After struggling for an hour, I decided to quit and informed the recruiter. They called a week later to say I wasn't considered, which didn't surprise me. There were no questions about software engineering principles, best practices, or design patterns, just memorization of obscure language details that are easily searchable.
- Can you fill out all 288 cells from the loose and strict comparison tables on php.net in an Excel sheet with the correct "yes/no" answers?
Schibsted Software Engineer Interview Questions
Quoted word for word from Schibsted interview reports.
“How to find the missing number in a consecutive array using sum[1...N]?”
Read reports →“Can you find if a word is an anagram of another word?”
Read reports →“How to minimize number of races to find the 3 fastest over 25 horses?”
Read reports →“From a given position, can you traverse all accessible positions?”
Read reports →“Can you code to print christmas tree?”
Read report →“Two robots on a line have to meet, and the same command is applied to both of them at the same time. What is the logic for commands like Right(), Left(), pause(), onPlatform()?”
Read report →“Can you implement LRU policy in cash?”
Read report →“Tell me about recursive algorithms on graphs.”
Read report →“Can you whiteboard Insertion sort?”
Read report →Formats, difficulty and experience
Across all 13 Schibsted interview reports.