Own difficult product-system problems from ambiguity through model, decision, specification and implementation.

The Opportunity:

MenuWise is rebuilding a proven foodservice platform whose behaviour depends on deeply connected rules and knowledge across ingredients, recipes, nutrition, suppliers, procurement, pricing, compliance, reporting and search.

This role exists to turn that complexity into clear, durable product-system knowledge. You will take problems that are incomplete, contradictory or spread across several sources; determine how the product should actually behave; model the rules and relationships; produce specifications Engineering can implement; and remain involved when implementation evidence shows that the model needs to change.

This is not a conventional requirements-processing role. Delivery work follows from resolved product knowledge rather than being the starting point.

What You Will Own:

- Investigate difficult product and operational problems using existing behaviour, data, models, specifications, source evidence and domain expertise.

- Define and reconcile concepts, identities, relationships, states, transitions, rules, dependencies and information flows.

- Choose and create the model that fits the problem - for example domain, relationship, process, state, lifecycle, decision or data views.

- Find contradictions, hidden rules, missing states, invalid combinations and downstream consequences before they become implementation defects.

- Produce substantial functional/product specifications and governed knowledge that Engineering can implement without inventing fundamental product behaviour.

- Work directly with Engineering on APIs, data models, integrations and system behaviour while keeping product/domain decisions distinct from technical implementation authority.

- Stay involved through implementation, testing and correction, updating the governing model or specification when evidence changes.

Examples of the Problems:

The work can include modelling how ingredient transformations, yield or wastage affect recipes and nutrition; how supplier products, packaging and pricing relate to product knowledge; or how rules and classifications propagate through reporting, search and other platform capabilities. The important skill is not prior foodservice knowledge - it is the discipline to make complex behaviour explicit, coherent and implementable.

What You Need to Succeed:

- Principal or lead-level evidence of complex systems analysis, business systems analysis, functional architecture, domain/information modelling or an adjacent discipline.

- Strong modelling capability. We care about why a model exists, what ambiguity it resolves and how it changes decisions - not a particular notation.

- Experience producing substantial specifications or governed artefacts that Engineering has genuinely relied on.

- A disciplined approach to rules, exceptions, contradictions, edge cases and propagation effects.

- Evidence-led judgement when sources or stakeholders disagree, including the ability to separate facts, assumptions, recommendations and decisions.

- Enough technical systems literacy to reason credibly about APIs, JSON, relational data, integrations and implementation consequences. Production coding is not required.

- Advanced AI-assisted analytical working with verification, including examples where you rejected or materially changed AI output.

- Exceptional written English and sustained attention to detail across a large connected information space.

Backgrounds That Can Transfer Well:

We are deliberately not hiring by exact prior title. Relevant backgrounds may include Principal/Lead Business Systems Analyst, Senior/Principal Systems Analyst, hands-on Functional Architect, Business Architect, domain or information specialist, PIM/MDM/Product Information specialist, or an exceptional product/platform professional with deep system-definition ownership.

Experience in ERP, healthcare, insurance, procurement, supply chain, manufacturing, compliance or other complex domains can transfer strongly. Foodservice experience is useful but not required.

Technology & How We Work:

You will work at the boundary between product/domain knowledge and Engineering. The environment includes TypeScript and Python services, PostgreSQL, APIs and integrations; exact stack experience is less important than being able to reason about system consequences with engineers.

MenuWise works through research, modelling, documented decisions and implementation-ready specifications. AI-assisted working is part of normal analytical practice, with source checking, judgement and professional verification expected.