When a trader needs an answer, an order needs to move or Finance needs reliable information, the systems behind the work matter. We are bringing more Odoo development capability inside B Futurist. Help us turn business needs into useful software and build the knowledge to keep improving it ourselves.
At a glance
Who we are
B Futurist moves fragrance, cosmetics and hair care across Europe, the Middle East, Asia and the Americas. Alongside our trading and distribution business, we run Beautinow, our online niche fragrance retailer.
We are an energetic, international team with a flat structure. We avoid unnecessary hierarchy, speak openly, question established ways of working and give people room to take initiative. If you see a better way, bring it forward. Test your ideas, learn from feedback and share what you discover. Colleagues across Trading, Supply Chain, Warehouse, Finance and Business Operations work closely together. Freedom comes with responsibility for your choices, your work and the people who rely on it.
What you will actually do
Build and change what runs the business. Write customisations in Python inside the Odoo framework; models, views and business logic; for Trading, Supply Chain, Warehouse, Finance and HR.
Grow your ownership of the system. We work with a specialist Odoo partner and will continue to. You would bring the everyday development in-house and extend into the heavier work as you learn how our system is put together. A lot of that everyday work is small and frequent; a report that needs changing, a scheduled job that failed overnight, an import that has to be right the first time. Each one is minor on its own. Together they are what keeps people waiting, which is why we want them handled here.
Get to the bottom of problems. Open code you have never seen, work out what it is doing and explain what went wrong; whether the fix is yours to make or sits with our partner.
Lead the next version upgrade. We are moving to a newer Odoo version, and we do not want to simply migrate. You would help us review what we carry over, what we retire and what we rebuild, so the system evolves deliberately rather than by accident.
Work alongside our partner. On the larger developments they build, you write the specification, challenge the approach and test what comes back.
Your first months
Learn our customisations from the inside and start with the everyday development work. You would not do that alone; our Business Operations team knows the data, the processes and the ERP, and part of their job is getting you what you need to go further, faster. As you get to know the system, take on the heavier work in the areas you know best. Within a year we would expect you to be the person here who understands our Odoo best.
What you bring
The Odoo framework, hands-on. ORM, views, actions, security and controllers, with real experience on Odoo v17 or later, and a solid grasp of the data model and the PostgreSQL underneath it.
The ground around it. SQL you can read and write. XML you can read, write and modify with XPath. QWeb templating for the HTML documents Odoo generates. And a clear understanding of HTTP methods and how client and server exchange API requests and responses.
You write tests, and you know OCA. Unit tests for what you build, and familiarity with the Odoo Community Association development guidelines.
You can read and debug custom code somebody else wrote, without the original developer to ask.
You have been through an Odoo migration or a major version upgrade.
You understand stock, order and purchasing processes as business processes, not only as modules.
Mid-level or senior. This is not a first job, and not a role for someone who works through the interface and stops where the code starts.
You are comfortable as the first developer in the team, working alongside a specialist partner.
A plus: integrations and API experience, exposure to Lean or process improvement, and time spent inside a business rather than only at an agency. We do not ask for a computer science degree, and we do not ask for Dutch.
How we work
Work reaches you already defined. Business Operations sits with the departments, works out what is actually needed and sets the criteria, so your time goes into building and testing rather than into meetings about what to build. You will talk directly to the people whose work you are changing.
We are not a software company and we do not pretend to be. Our Odoo development is done today by a specialist partner who works to a clear standard: automated tests on what they build, and the OCA development guidelines. You would work with their developers and go through their review, so your code needs to meet that same standard. That is the level we are setting for this team from the start.
Expect direct feedback, and expect to say so when you think something is a bad idea.
What you get
Hiring Process
Our hiring process has three stages, each lasting up to one hour. We start with a conversation with HR and our Business Operations Team Leader about your experience and the Odoo projects you have delivered. Next is a technical session with a short exercise based on a real, resolved ticket from our backlog, followed by a discussion of your approach. We finish with a conversation with the founders about the role, working together and mutual expectations.
