R - Business Analyst and Product Commercialization Lead
FoodChain ID Group, Inc. · Remoto, BR
**BRAZIL RESIDENTS ONLY.** Company Overview At FoodChain ID, we are driven by our vision to make it easier to keep the food supply chain safe and transparent. As a global leader in food safety, compliance, and product innovation solutions, we support more than 30,000 companies across more than 100 countries with a comprehensive software platform that enables leading food manufacturers and retailers to manage compliance, risk, and efficiently access new markets and consumers as the New Food Economy continues to evolve. Job Title: Business Analyst and Product Commercialization Lead Reports To: Director, Product and Delivery Enablement Location: Remote Job Type: Full Time Job Overview The Business Analyst and Product Commercialization Lead works as part of the Product Management team supporting FoodChain ID's Enterprise Solutions portfolio, which includes Formulation for PLM, Compliance Analysis, and Recipes \& Specifications. The role covers the two stretches of work that sit on either side of development: getting work ready to build, and getting built work ready to deliver. On the front end, the role develops the epics, features, user stories, and acceptance criteria that carry an idea into a development\-ready state, working day to day with the Product Management team, which sets feature scope and prioritization. Doing this well means understanding the product domain deeply enough to write requirements engineering can build from without a second round of clarification. On the back end, the role makes sure that what development delivers is ready for customers: owning release communication, producing and maintaining product documentation, and building the training and services enablement assets that Services, Support, and Sales need to put new functionality to work. Consistent use of AI tooling is expected, including building and refining agent skills that reduce the manual effort of keeping documentation and release content current as features ship. Key Responsibilities Requirements Definition and Development Readiness * Develop epics, features, and user stories from product direction, customer input, and conversations with subject matter experts (SMEs), working under the direction of the Product Management team, which owns feature scope and prioritization. * Author clear, testable acceptance criteria, and confirm shared understanding with engineering and QA before work is committed to a sprint. * Conduct the upfront research and analysis that makes story\-writing and refinement sessions productive, so that decisions rest on evidence. * Work closely with SMEs, Services, and business partners to understand the product needs behind a request, and translate them into requirements a development team can build from. * Review or create process and system flow maps documenting the business domain, including the business rules and logic needed to incorporate a process into the system. * Identify and document story dependencies to support refinement and sequencing. * Maintain a regular cadence for story definition, writing, review, and refinement, keeping a backlog of sufficient depth and readiness to support team velocity. * Participate in backlog refinement, sprint planning, and demos as the analyst closest to the requirements. Delivery Coordination * Track development progress against committed plans so that commercialization work is timed to when functionality will land. * Raise scope changes, emerging gaps, and at\-risk dates to the Product Management team early, with the specifics needed to make a decision. * Review delivered functionality against acceptance criteria before it is considered ready for customers, and flag discrepancies. * Contribute delivery and release content to the recurring account reporting and business reviews prepared by product leadership. Release Communication * Own release communication end to end: build and operate a repeatable process that captures release content as it is developed. * Write release notes for every release, translating technical changes into language customers can act on, and publish them on a predictable cadence. * Brief Services, Support, and Sales ahead of customer\-visible changes so that internal teams are never behind the customer. * Coordinate the timing of release communication with documentation and enablement updates so that customers and internal teams encounter a consistent picture. Product Documentation * Own the customer documentation portal as its primary author and editor, and keep published content aligned with shipped functionality. * Drive documentation updates from the same source that drives release notes, so that both are produced from one pass through each release. * Improve the structure and quality of existing documentation over time, prioritizing the areas where support escalations and customer questions indicate confusion. * Establish and maintain standards for voice, structure, and depth so that content stays consistent as contributors chan