Last month, I applied for a full stack developer role at Odoo through their official website. Surprisingly, I got a call and email the very next day inviting me to take an online test. Here's a breakdown of my interview process and some insights for anyone preparing for a similar role at Odoo.
Round 1: The Online Test
The test was a mix of technical and problem-solving questions. It included:
1.MCQs: These covered the basics of HTML, CSS, JavaScript, and React. The questions were pretty straightforward but required clarity on core concepts.
2.DSA Questions:
- 1 easy-level problem
- 1 medium-level problem
3.SQL: This was a slightly challenging question involving complex queries.
I managed to clear this round and got an email within 10 days inviting me for the next stage
Round 2: English and Logical Tests
This round was split into two parts:
English Test:
- The task involved writing client-facing emails to troubleshoot issues. I had to draft three different responses for hypothetical client problems. It tested clarity, tone, and professionalism in communication.
Logical and Math Test:
- Standard logical reasoning and math puzzles to evaluate problem-solving skills.
Thankfully, I cleared this round too.
Round 3: Technical Interview
This was the most intense part of the process. It was a live coding round with a very supportive interviewer who let me decide the tech stack for the task. Here’s how it went:
Task: Build a full stack web application with the following features:
- Product page
- Shopping cart
- Filters and search functionality (with debounce)
- Database connection
Tech Stack: I chose Node.js for the backend, Next.js for the frontend, and SQL for the database as I already had a good understanding of the tables I needed to create.
Expectations:
- CRUD APIs for all operations
- Clean code and working functionalities
The session, scheduled for 2 hours, ended up stretching to 3 hours and 20 minutes. Although the interviewer was helpful and provided guidance whenever I got stuck, I faced issues connecting the database. To keep things moving, I used dummy data for the project.
Additionally, I was asked two SQL questions:
- A SELECTquery with WHERE conditions.
- An INNER JOIN query with logical operators.
My Takeaway
Unfortunately, I wasn’t selected. One thing that left me a bit disappointed was how the coding round extended well beyond the scheduled time. If the decision was to not move forward with me, I felt my time could’ve been respected a bit more.
That said, the process was a great learning experience, and I gained insights into:
- How to approach a full stack app under pressure.
- The importance of staying calm when things don’t go as planned.
- Areas to improve for future interviews, like debugging database issues quickly.
Tips for Odoo Interview Preparation
1. Brush Up on Basics: The MCQs are all about fundamentals, so review core concepts of HTML, CSS, JavaScript, and React.
2. Practice DSA: Ensure you’re comfortable with easy-to-medium level problems, as these are often asked in online tests.
3. SQL Skills: Be ready for advanced SQL queries involving joins and logical operators.
4. Communication Matters: The English test assesses how well you can communicate with clients, so practice writing concise and professional emails.
Be Ready for Full Stack Tasks: The live coding round is demanding.
Focus on:
- CRUD operations
- Search functionality with features like debounce
- Backend and database connectivity
- Time Management: Try to pace yourself, especially during the coding round, as time can slip away quickly.
The above is the detailed content of Odoo Full Stack Developer Interview Experience. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

There are three common ways to initiate HTTP requests in Node.js: use built-in modules, axios, and node-fetch. 1. Use the built-in http/https module without dependencies, which is suitable for basic scenarios, but requires manual processing of data stitching and error monitoring, such as using https.get() to obtain data or send POST requests through .write(); 2.axios is a third-party library based on Promise. It has concise syntax and powerful functions, supports async/await, automatic JSON conversion, interceptor, etc. It is recommended to simplify asynchronous request operations; 3.node-fetch provides a style similar to browser fetch, based on Promise and simple syntax

JavaScript data types are divided into primitive types and reference types. Primitive types include string, number, boolean, null, undefined, and symbol. The values are immutable and copies are copied when assigning values, so they do not affect each other; reference types such as objects, arrays and functions store memory addresses, and variables pointing to the same object will affect each other. Typeof and instanceof can be used to determine types, but pay attention to the historical issues of typeofnull. Understanding these two types of differences can help write more stable and reliable code.

Hello, JavaScript developers! Welcome to this week's JavaScript news! This week we will focus on: Oracle's trademark dispute with Deno, new JavaScript time objects are supported by browsers, Google Chrome updates, and some powerful developer tools. Let's get started! Oracle's trademark dispute with Deno Oracle's attempt to register a "JavaScript" trademark has caused controversy. Ryan Dahl, the creator of Node.js and Deno, has filed a petition to cancel the trademark, and he believes that JavaScript is an open standard and should not be used by Oracle

CacheAPI is a tool provided by the browser to cache network requests, which is often used in conjunction with ServiceWorker to improve website performance and offline experience. 1. It allows developers to manually store resources such as scripts, style sheets, pictures, etc.; 2. It can match cache responses according to requests; 3. It supports deleting specific caches or clearing the entire cache; 4. It can implement cache priority or network priority strategies through ServiceWorker listening to fetch events; 5. It is often used for offline support, speed up repeated access speed, preloading key resources and background update content; 6. When using it, you need to pay attention to cache version control, storage restrictions and the difference from HTTP caching mechanism.

Promise is the core mechanism for handling asynchronous operations in JavaScript. Understanding chain calls, error handling and combiners is the key to mastering their applications. 1. The chain call returns a new Promise through .then() to realize asynchronous process concatenation. Each .then() receives the previous result and can return a value or a Promise; 2. Error handling should use .catch() to catch exceptions to avoid silent failures, and can return the default value in catch to continue the process; 3. Combinators such as Promise.all() (successfully successful only after all success), Promise.race() (the first completion is returned) and Promise.allSettled() (waiting for all completions)

JavaScript array built-in methods such as .map(), .filter() and .reduce() can simplify data processing; 1) .map() is used to convert elements one to one to generate new arrays; 2) .filter() is used to filter elements by condition; 3) .reduce() is used to aggregate data as a single value; misuse should be avoided when used, resulting in side effects or performance problems.

JavaScript's event loop manages asynchronous operations by coordinating call stacks, WebAPIs, and task queues. 1. The call stack executes synchronous code, and when encountering asynchronous tasks, it is handed over to WebAPI for processing; 2. After the WebAPI completes the task in the background, it puts the callback into the corresponding queue (macro task or micro task); 3. The event loop checks whether the call stack is empty. If it is empty, the callback is taken out from the queue and pushed into the call stack for execution; 4. Micro tasks (such as Promise.then) take precedence over macro tasks (such as setTimeout); 5. Understanding the event loop helps to avoid blocking the main thread and optimize the code execution order.

Event bubbles propagate from the target element outward to the ancestor node, while event capture propagates from the outer layer inward to the target element. 1. Event bubbles: After clicking the child element, the event triggers the listener of the parent element upwards in turn. For example, after clicking the button, it outputs Childclicked first, and then Parentclicked. 2. Event capture: Set the third parameter to true, so that the listener is executed in the capture stage, such as triggering the capture listener of the parent element before clicking the button. 3. Practical uses include unified management of child element events, interception preprocessing and performance optimization. 4. The DOM event stream is divided into three stages: capture, target and bubble, and the default listener is executed in the bubble stage.
