Business Analyst and Product Owner
Il y a 19 heures
Brussels, Brussels-Capital, Belgique
Nestoya
Temps plein
Gratuit avec email ou Google
Enregistrez cette offre et organisez votre recherche
Créez un compte gratuit pour enregistrer des offres d'emploi, créer des alertes et revenir à cette liste depuis votre tableau de bord.
Gratuit avec email ou Google
En continuant, vous acceptez nos Conditions d’utilisation & Politique de confidentialité.
ABOUT NESTOYA
We're a dynamic CPQ and ERP developer. Manufacturers of made-to-measure products come to us when quoting has become a bottleneck. We replace spreadsheets and back-and-forth emails with a 3D configurator and an integrated platform (Configurator, ERP, PIM and CRM) that sells, prices and produces from a single source of truth.
A customer configures a product in 3D, and that same product model drives the quote, the order, the bill of materials and the shop floor. Getting the rules right matters, and that is exactly what this role is about.
WHY THIS ROLE EXISTS
Today the same people sell, analyse and own the product. It works, but it caps how many projects we can run well. We're separating the two tracks: sales focuses on selling, and you take full ownership of delivery — analysis, specification, prototype, backlog, client coordination and acceptance.
This is a role with genuine authority, not a note-taking function. You decide what a rule means, you defend the scope, and you're the reference point for both the client and the development team.
WHAT YOU'LL DO
You are the bridge between a manufacturer's business reality and a development team that needs unambiguous instructions.
• Analyse the client's business: Run discovery workshops, map the sales-to-production process, and dig until you understand the product rules, the pricing logic and the exceptions nobody documented.
• Write the specifications: Functional specs the client can validate and a developer can build from: process flows, data models, configuration rules, business logic, integrations and edge cases.
• Build the prototype: Turn the specification into something the client can click through, using an LLM such as Claude or ChatGPT, so misunderstandings surface before any production code is written.
• Break it down for the dev team: Once the specs are validated, write the epics and user stories with clear acceptance criteria, and make sure the development team has everything it needs to build without guessing.
• Coordinate with the client: Status updates, planning, chasing the missing inputs, organising the test rounds and getting functionalities actually tested and signed off.
• Test and protect the scope: Test the delivered functionality before the client sees it, triage what comes back (bug or change request), and hold the line on scope, politely and with evidence. HOW A PROJECT RUNS: WATERFALL WHERE IT HELPS, AGILE WHERE IT PAYS Specification and validation follow a structured, phased approach, because clients need to know what they're signing. Delivery runs in iterations. You need to be fluent in both, and to know which one a given moment calls for.
• Discovery: Workshops with the client's sales, engineering and production teams. Process mapped, pain points quantified.
• Specification & prototype: Functional specs, rule sets and data model written; prototype built and walked through with the client.
• Validation & scope baseline: Client signs off. The baseline becomes the reference for every later "can we just…" conversation.
• Build: Epics and user stories to the dev team, refinement, questions answered fast, priorities kept clear.
• Testing & UAT: You test first, then drive the client's acceptance testing. Bugs get fixed, change requests get quoted.
• Go-live & handover: Training material, documentation and decision register, so the project leaves behind a single source of truth. WHAT YOU BRING (MUST-HAVES)
• A master degree in Business Engineering or any related subject
• 5+ years in business analysis and/or product ownership on custom software projects.
• Specification writing you're proud of: precise, complete, and readable by both a client and a developer.
• Both methodologies. Real experience with waterfall phasing and with agile delivery (epics, user stories, acceptance criteria, refinement, sprint rhythm).
• Testing experience. You write test cases, you execute them, and you can run a client through UAT without losing control of it.
• Scope discipline. You can tell a bug from a change request, explain the difference to a client, and keep the relationship intact while doing it.
• Structured logic. You can take messy product knowledge and turn it into a coherent, non-contradictory rule set built on a single source of truth.
• Client-facing confidence. Comfortable leading a workshop, presenting to a management team and chasing people for the input you need.
• Languages: fluent English, French and/or Dutch. English with the development team, French and Dutch with our clients. Other language is a strong plus.
• Tools: Jira and Confluence, SharePoint and the Microsoft suite (Excel, Word), and a process-mapping tool of your choice. NICE TO HAVE
• Comfort with technical and engineering topics. An engineering background is a plus, but what matters is that you can read a technical drawing or a product rule and reason about it. You don't need to be an engineer; you do need to be unafraid of the technical detail.
• Experience in manufacturing or made-to-measure products.
• Exposure to CPQ, product configurators, ERP, PIM or e-commerce integrations.
• Experience working with a remote development team. THE TEST WE CARE MOST ABOUT Give us a product with fifteen options, four of which contradict each other under certain conditions, and a client who describes them differently on Tuesday than on Monday. If your instinct is to sit down and build the rule table until it holds together, you'll enjoy this job.
WHAT WE OFFER
• A permanent contract in a growing company where your work is visible.
• Direct reporting to the CEO, no layers between you and the decision.
• Full ownership of your projects, from first workshop to go-live.
• Real industrial software: what you specify ends up running in a factory.
• Competitive salary.
• Hybrid working. INTERESTED? Send your CV and a short note about a project you specified from scratch: what the rules were, and what you did when the client changed their mind. Apply via LinkedIn or email sales@nestoya.com Configurator
· ERP
· PIM
· CRM
WHAT YOU'LL DO
You are the bridge between a manufacturer's business reality and a development team that needs unambiguous instructions.
• Analyse the client's business: Run discovery workshops, map the sales-to-production process, and dig until you understand the product rules, the pricing logic and the exceptions nobody documented.
• Write the specifications: Functional specs the client can validate and a developer can build from: process flows, data models, configuration rules, business logic, integrations and edge cases.
• Build the prototype: Turn the specification into something the client can click through, using an LLM such as Claude or ChatGPT, so misunderstandings surface before any production code is written.
• Break it down for the dev team: Once the specs are validated, write the epics and user stories with clear acceptance criteria, and make sure the development team has everything it needs to build without guessing.
• Coordinate with the client: Status updates, planning, chasing the missing inputs, organising the test rounds and getting functionalities actually tested and signed off.
• Test and protect the scope: Test the delivered functionality before the client sees it, triage what comes back (bug or change request), and hold the line on scope, politely and with evidence. HOW A PROJECT RUNS: WATERFALL WHERE IT HELPS, AGILE WHERE IT PAYS Specification and validation follow a structured, phased approach, because clients need to know what they're signing. Delivery runs in iterations. You need to be fluent in both, and to know which one a given moment calls for.
• Discovery: Workshops with the client's sales, engineering and production teams. Process mapped, pain points quantified.
• Specification & prototype: Functional specs, rule sets and data model written; prototype built and walked through with the client.
• Validation & scope baseline: Client signs off. The baseline becomes the reference for every later "can we just…" conversation.
• Build: Epics and user stories to the dev team, refinement, questions answered fast, priorities kept clear.
• Testing & UAT: You test first, then drive the client's acceptance testing. Bugs get fixed, change requests get quoted.
• Go-live & handover: Training material, documentation and decision register, so the project leaves behind a single source of truth. WHAT YOU BRING (MUST-HAVES)
• A master degree in Business Engineering or any related subject
• 5+ years in business analysis and/or product ownership on custom software projects.
• Specification writing you're proud of: precise, complete, and readable by both a client and a developer.
• Both methodologies. Real experience with waterfall phasing and with agile delivery (epics, user stories, acceptance criteria, refinement, sprint rhythm).
• Testing experience. You write test cases, you execute them, and you can run a client through UAT without losing control of it.
• Scope discipline. You can tell a bug from a change request, explain the difference to a client, and keep the relationship intact while doing it.
• Structured logic. You can take messy product knowledge and turn it into a coherent, non-contradictory rule set built on a single source of truth.
• Client-facing confidence. Comfortable leading a workshop, presenting to a management team and chasing people for the input you need.
• Languages: fluent English, French and/or Dutch. English with the development team, French and Dutch with our clients. Other language is a strong plus.
• Tools: Jira and Confluence, SharePoint and the Microsoft suite (Excel, Word), and a process-mapping tool of your choice. NICE TO HAVE
• Comfort with technical and engineering topics. An engineering background is a plus, but what matters is that you can read a technical drawing or a product rule and reason about it. You don't need to be an engineer; you do need to be unafraid of the technical detail.
• Experience in manufacturing or made-to-measure products.
• Exposure to CPQ, product configurators, ERP, PIM or e-commerce integrations.
• Experience working with a remote development team. THE TEST WE CARE MOST ABOUT Give us a product with fifteen options, four of which contradict each other under certain conditions, and a client who describes them differently on Tuesday than on Monday. If your instinct is to sit down and build the rule table until it holds together, you'll enjoy this job.
WHAT WE OFFER
• A permanent contract in a growing company where your work is visible.
• Direct reporting to the CEO, no layers between you and the decision.
• Full ownership of your projects, from first workshop to go-live.
• Real industrial software: what you specify ends up running in a factory.
• Competitive salary.
• Hybrid working. INTERESTED? Send your CV and a short note about a project you specified from scratch: what the rules were, and what you did when the client changed their mind. Apply via LinkedIn or email sales@nestoya.com Configurator
· ERP
· PIM
· CRM