Business Analyst

Key responsibilities

• Work with customers and internal teams to understand manufacturing processes across production, procurement, inventory, quality, maintenance, sales and dispatch.
• Convert business processes into clear requirements, user stories, acceptance criteria and process flows.
• Map the as-is process in a plant and define the to-be process in the product, including what changes for the people doing the work.
• Identify dependencies and downstream impact across modules before a change is built.
• Work with Product and Engineering through design, build and release, and answer the questions that come up mid-build.
• Support UAT with customers, triage what comes back and separate a defect from a missing requirement.
• Prepare functional documentation, configuration guides and release notes.
• Support implementation and onboarding for new plants, including data migration templates and cutover checks.

Must-have skills

• 2–4 years as a Business Analyst on a product or enterprise application.
• Ability to understand a complex operational workflow end to end and explain it simply.
• Strong requirement writing — user stories, acceptance criteria, process flows and edge cases.
• Comfortable with SQL for checking data and validating what a report or screen is really showing.
• Experience working directly with customers, including users who are not software-literate.
• Strong analytical thinking and the confidence to challenge a requirement that does not make business sense.
• Clear written and verbal communication with both plant teams and engineers.

Good to have

• Experience with ERP, MES, SCM or manufacturing software.
• Exposure to a shop floor — a plant visit, an audit, or time spent with production or quality teams.
• Understanding of quality processes such as APQP, PPAP, FMEA or control plans.
• Familiarity with API concepts and reading a Swagger/Postman collection.
• Experience with tools such as Jira, Confluence, Figma or a process-mapping tool.

What we're looking for

Someone who is not satisfied with writing down what was asked for. You should be able to sit with a production supervisor, work out what actually happens on the floor versus what the SOP says, and bring back a requirement that reflects reality — including the rejection, rework and exception paths that nobody mentions in the first meeting.