ironSource Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 9 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at ironSource.
ironSource
Software Engineer
Entry Difficult Neutral experience No offer 2 rounds
Interview process
Take home Recruiter call
Interview formats
Coding Technical Presentation
I did a home test that took me about 1.5 to 2 hours. It had 2 data structures and algorithms questions, and then 1 backend understanding question. I was a bit surprised by the backend question since it was an entry-level role and I don't have much experience. They expected me to know it, especially within like 20 minutes. They didn't give me any feedback even though I asked why I was rejected.
Confirmed questions2 questions
- Two questions on data structures and algorithms.
- Given a specific case with a server/runtime problem, identify the source, explain your actions, and describe the fix.
ironSource
Senior Software Engineer
Senior Easy Neutral experience No offer 2 rounds
Interview process
Recruiter call Onsite
Interview formats
Behavioral Technical Coding
Had a quick phone chat about my background and what they're looking for. Then, an onsite where I met the team lead and group lead. It involved a lot of personal questions and also JavaScript questions on prototype and join, plus lambda. They also asked about projects I've worked on.
Confirmed questions3 questions
- Can you write a function that returns another function?
- Could you explain what lambda is?
- What are the advantages and disadvantages of using Redis and NoSQL databases?
ironSource
Software Engineer
Mid Average Positive experience No offer 4 rounds
Interview process
Technical screen Technical screen Technical screen Recruiter call
Interview formats
Technical Coding System Design Behavioral
We had 4 interviews in total. The first 3 were technical, and the last one was with HR. The initial interview involved discussing my technical background and experience, and also a system design question. Then, there was a 2-hour session focused on developing a web server to display a UI page that was presented to me. The third interview was a technical chat with the director, which also included a system design question.
Confirmed questions2 questions
- Can you plan out a system that would allow searching for a word in a repository based on a prefix?
- Plan a system that support search in a word repository by prefix
ironSource Software Engineer Interview Questions
Quoted word for word from ironSource interview reports.
“Can you write a function that returns another function?”
Read reports →“What are the advantages and disadvantages of using Redis and NoSQL databases?”
Read reports →“Could you implement an autocomplete search feature that displays the top 5 most frequent words starting with the user's input?”
Read reports →“Can you plan out a system that would allow searching for a word in a repository based on a prefix?”
Read reports →“Could you explain what lambda is?”
Read report →“Can you discuss designing systems for high availability?”
Read report →“Can you describe the algorithm for the coding challenge?”
Read report →“Given a specific case with a server/runtime problem, identify the source, explain your actions, and describe the fix.”
Read report →“Could you describe the design of a project you led?”
Read report →Formats, difficulty and experience
Across all 9 ironSource interview reports.