Real, anonymous reports from people who interviewed for Software Engineer at Odoo, newest first and distilled into what to expect across the loop.
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 process kicked off with a focused HTML tags validator assessment. The challenge was straightforward in concept: I had to check whether an HTML snippet was valid, and it was structured so that one wrong tag or an invalid structure would make it fail.
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.
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.
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.
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.
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.
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.