Odoo logo

Odoo Software Engineer Interview Questions
& Process

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

Based on 206 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
57.8% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Odoo.

Showing 3 of 206
Odoo logo
Odoo

Software Engineer Intern

Engineering · nearly a year ago

Intern Average Positive experience No offer 2 rounds
Interview process
Take home Technical screen
Interview formats
Coding

The first stage was a coding assessment on the Coderbyte platform, lasting 1 hour and 45 minutes. It had three questions: one SQL, one graph, and one array. The SQL question involved joins and group by, and was easy. The array question used hashmaps and was easy. The graph question was about the shortest path from the first to the last node, which was hard for beginners but medium for those familiar with graphs. I got the results within a day but was not selected. After the coding round, there was a direct interview with the team lead, which was the final round. My suggestion is to try to solve all 3 questions fully, or at least the hard one with half the test cases and the other two fully. Solving the hard one is the best chance to get selected. Happy coding. Life moves on, better opportunities will come to you. Thank you.

Confirmed questions1 question
  • none
Odoo logo
Odoo

Software Developer

Engineering · a year ago

Entry Difficult Neutral experience No offer 3 rounds
Interview process
Take home Recruiter call Technical screen
Interview formats
Coding Technical

Applied online, and after about two weeks, I got an email for a coding challenge, which was like a medium LeetCode problem. They gave me an hour, but I did it in about 20 minutes. Then, a few days later, I had a quick screening call with HR. A couple of days after that, I got invited to the final round, a technical interview with LeetCode-style questions. You just solve them, no talking to the interviewer, they just watch. You can use Google if you ask them first. After each problem, you get the next one. If you can't solve a problem, the interview stops. I got one question from LeetCode and one from Advent of Code. I couldn't answer some follow-ups, so they stopped the interview.

Confirmed questions1 question
  • solve leetcode style questions in any language you prefer
Odoo logo
Odoo

Software Engineer

Engineering · a year ago

Mid Average Positive experience Decline offer 4 rounds
Interview process
Technical screen Recruiter call Technical screen Technical screen
Interview formats
Coding Behavioral Technical Technical

It started with a simple online coding test, followed by an HR interview and a cognitive test. Then, a technical interview. The whole thing was pretty quick and the HR person was really nice and helpful. The senior software engineer conducting the technical interview was great too, giving me tips to improve my first approach during the coding part. The technical interview covered a few things: first, coding, where I could use my preferred language. It wasn't super hard, more like easy to medium LeetCode problems, but it really tested my grasp of algorithms, data structures, and complexity. Second, dataset design, which was a cool, high-level task to check OOP skills, engineering sense, and how familiar I was with dataset design. SQL and UML weren't strictly needed; I used JSON and that worked fine. Lastly, project experience, which differs for everyone. They wanted to see that I really understood my past work and could share some interesting thoughts about it.

Confirmed questions5 questions
  • What motivated you to apply for this role?
  • Can you tell me about your future career aspirations?
  • Tell me about your approach to coding challenges, including how you would optimize your solution and analyze its time and space complexity.

Odoo Software Engineer Interview Questions

Quoted word for word from Odoo interview reports.

Given an array of strings representing a graph, find the shortest path from the first node to the last node and return it as a string separated by dashes. If no path exists, return -1. The graph is non-looping and connections are bidirectional. The array format includes the number of nodes, the nodes themselves, and then the connections.

Read reports

Can you validate or parse a simplified HTML string with opening and closing tags?

Read reports

Given a list of operations to be performed in order on an array, execute them.

Read reports

How would you create a sorted stack object in Python with O(1) complexity for its operations?

Read reports

Given an array of numbers, return "Arithmetic" if it follows an arithmetic pattern, "Geometric" if it follows a geometric pattern, or -1 if neither. An arithmetic sequence has a consistent difference between numbers, and a geometric sequence has a consistent ratio. Negative numbers are possible, but 0 and arrays with all same elements are not.

Read report

Implement a Polish Calculator using NPM that accepts a String and outputs a single number, possibly using a Stack Data Structure.

Read report

Can you solve the "Guess a number" game? Find a secret integer between 1 and 1000000 in under 50 guesses. Write a function that solves this game without user input and returns the solution using the verify() function, which is defined as follows: function verify(guess: integer) -> integer. Argument: guess (integer) is the number to verify. Returns: 0 if the guess is the solution, your program wins. -1 if the solution is smaller than the guess parameter. 1 if the solution is bigger than the guess parameter. Warning: You must not call verify() more than 50 times, or you will lose.

Read report

How would you push all the zeros to the end of an array?

Read report

Can you write a function to get the discount rate from order and price dictionaries?

Read report

Formats, difficulty and experience

Across all 206 Odoo interview reports.

Interview formats

Coding 37.1%
Technical 36.5%
Behavioral 19.8%
System Design 3.3%
Other 2.5%

Interview difficulty

Easy 8.7%
Average 71.8%
Difficult 19.4%

Candidate experience

Neutral 25.7%
Positive 57.8%
Negative 16.5%