About GeneralMind

GeneralMind builds AI Systems of Action for complex enterprise workflows. We deploy AI employees that automate messy operational handovers across supply chains - processing orders, validating invoices, coordinating suppliers, and handling exceptions directly on top of enterprise systems like SAP, Oracle, JDE, and Dynamics.

Our platform combines AI agents, operational context graphs, and real transaction data to achieve Autopilot-grade automation in real operational environments.

We work closely with leading global companies across manufacturing, retail, and logistics to deploy AI into mission-critical workflows.

About the role

You'll put our platform through its paces. You'll systematically look for bugs, weak spots, and unexpected behaviour, and just as importantly, document what works well and runs reliably. Your goal is simple: find the problems before our users do. You'll work closely with product and engineering and help make sure everything we ship holds up in the real world.

What You'll Do

• Test the platform from a real user's perspective, running through both typical flows and the unusual ones ("what happens if I enter the wrong thing?").

• Track down bugs, crashes, display issues, and illogical behaviour, and document them clearly with steps to reproduce.

• Judge whether features work the way they should, and flag anything confusing, clunky, or inconsistent (usability).

• Check different devices, browsers, and screen sizes to make sure everything works everywhere.

• Rank bugs by severity (critical vs. cosmetic) and prioritise them so the team knows what to fix first.

• Retest fixed bugs and confirm that the fixes didn't break anything else (regression testing).

• Work closely with engineering and product, answer their questions, and help reproduce issues.

What we are looking for

• A sharp, thorough eye for detail and the patience to get to the bottom of things.

• A structured, clear way of documenting bugs so anyone can follow them.

• The ability to think like a user and to use software "the wrong way" on purpose to find its limits.

• Clear, easy-to-understand communication, both written and spoken.

• First experience with software testing, QA tools, or ticketing systems (e.g. Jira, Linear) is a plus, but not a must depending on focus.