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 change.

Training and Services Enablement

• Develop the training and enablement assets that accompany newly delivered functionality, including written guides, walkthroughs, and reference material for customer and internal audiences.

• Build the baseline materials, templates, and content standards that the Services team adapts and delivers for customer-specific training.

• Deliver internal enablement sessions for Services, Support, and Sales as significant functionality ships.

• Use support escalation and defect trends to identify where documentation or training gaps are generating avoidable customer friction, and close those gaps.

Implementation Templates and Standards

• Support the implementation templatization program led by the Director, Product and Delivery Enablement, which builds the out-of-the-box configuration, data, and documentation starting point that Services and customers deploy from.

• Own the documentation and content components of the standard package, and deliver assigned tasks within the program plan.

Launch Readiness and Adoption

• Maintain a launch readiness standard for customer-visible functionality, confirming that documentation, training assets, internal enablement, and release communication are complete before a release reaches customers.

• Track adoption of newly released functionality and report on it, so that the value of what we ship is visible.

What Success Looks Like in the First Year

• Stories and acceptance criteria reach development ready to build, with clarification cycles the exception rather than the norm.

• Release notes publish on a predictable cadence for every release, and published documentation matches shipped functionality.

• No significant functionality reaches customers without documentation, training assets, and internal enablement in place.

• Services and Support are equipped to deliver customer training from materials they did not have to build themselves.

• Adoption of newly released functionality is measured and reported on a regular cadence.

Required Qualifications

• Three or more years of experience in business analysis, product management, product commercialization, or a comparable role on a software product team.

• Two or more years as a member of an Agile team, ideally as a Business Analyst, Product Owner, or Scrum Master.

• Demonstrated experience authoring user stories and acceptance criteria that a development team built from.

• Experience working directly with business stakeholders and SMEs, and translating their needs into development-ready requirements.

• Demonstrated experience producing customer-facing content, such as product documentation, release notes, user guides, or training material.

• Strong written communication, with the range to write for developers, executives, and customers and adjust register accordingly.

• Working knowledge of the software development lifecycle and of Agile and Kanban practices.

• Proficiency with development planning tools such as Jira, Azure DevOps, and Confluence.

• Comfortable using AI tools to draft, review, and maintain content.

• Comfortable working with product usage or support data to produce straightforward adoption and quality reporting.

• Professional, customer-facing communication style, with the poise to lead a working session or enablement session.

Preferred Qualifications

• Experience authoring User Stories using Gherkin acceptance criteria.

• Experience with enterprise SaaS products, cloud architectures, enterprise system implementations, and system integrations.

• Background in food technology, food science, or food compliance, or familiarity with PLM or related food-industry software.

• Experience owning product launch or commercialization readiness for a software product, including internal enablement of services or sales teams.

• Experience building or maintaining a customer-facing documentation site or knowledge base.

• Experience writing or configuring agent skills (Claude, ChatGPT, or similar) for content maintenance or reporting.

• Experience translating UI/UX storyboards into development stories.

• Familiarity with product analytics or support ticket data, and comfort building straightforward reports.

Additional Information

All your information will be kept confidential according to EEO guidelines.