O
OdooSoftware Engineer
Updated Jul 18, 2026

Odoo Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at Odoo, newest first and distilled into what to expect across the loop.

Get your personalized Odoo Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
3 months ago
Average Positive United States

My interview journey started with an online assessment that was designed like a small LeetCode batch. I had a one-hour online session with two coding problems, then shortly after I moved into a screening step. I also had a recruiter conversation as part of the flow, which helped set expectations and confirm fit.

The main technical conversation with the team lead came next and lasted about an hour. The final stage ended up being a longer technical interview—around two to four hours—where the questions were a mix of coding, DSA-style problem solving, and database-oriented tasks like SQL/query reasoning based on a schema. The difficulty generally ramped up as the session went on, and the interviewers were willing to answer questions I asked while I was working.
3 months ago
Average Positive Mexico

After a recruiter screen, I went into an assessment that was part logic and part timed coding. The recruiter conversation was casual and general, mixing straightforward questions about what I knew about the company and what I liked about working there, along with a simple case-style question about reasoning with assumptions. Then I did a practical coding test on Coderbyte for about an hour.

The technical stage was the most intense part. I had a longer call with a tech lead, shared my screen, and worked in an editor while solving multiple problems they added via a shared document. They also asked me to think out loud about my approach and to explain the complexity of my solutions. The set included a “count bits” type of problem, a queue-driven medium problem, and then something much harder that referenced Advent of Code.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.

What to expect

Distilled from the reports

Initial Assessment

Candidates typically start with a coding assessment focused on HTML parsing or similar logic problems, often resembling LeetCode-style challenges. This initial step is crucial as it sets the tone for the rest of the interview process.

HTML parsingLeetCodecoding assessment

Recruiter Screening

The recruiter conversation is generally brief and casual, focusing on fit and motivation rather than technical skills. This step helps candidates understand the company culture and expectations.

HR interviewfit assessmentcasual conversation

Technical Interview Structure

Technical interviews often consist of multiple rounds, including coding challenges and system design discussions, with a mix of problem-solving and theoretical questions. Candidates should be prepared for varying difficulty levels and a focus on reasoning and communication.

technical interviewproblem-solvingsystem design

Focus on Communication and Reasoning

Interviewers place significant emphasis on candidates' thought processes and communication during technical tasks, valuing clarity and reasoning over simply arriving at the correct answer. Candidates should practice articulating their thought process.

communicationthought processclarity

Timeline and Feedback

The interview process can vary in length, with some candidates experiencing delays in feedback and outcomes. It's important to manage expectations regarding the timeline and seek clarity when necessary.

timelinefeedbackexpectations

Overall Experience and Outcome

While many candidates report a structured and organized process, the overall experience can vary widely, with some feeling unsupported or unclear about their performance. Reflecting on the experience can provide insights for future applications.

experienceoutcomereflection