Quality Assurance Engineer

What we are building

Onified.ai is building an Enterprise Resource Intelligence (ERI) platform for manufacturers. It brings enterprise applications and factory data into one connected system instead of fifteen that do not talk to each other. We are building 50+ integrated applications on it: Cargo (transportation), Supply (procurement), Warehouse (WMS), Assets (maintenance), Energy, Gauge (vision quality), Trace (traceability), Books (accounting), People (HRMS), Service (ITSM/ESM), Field (field service), Prism (analytics), and more.

Why this role matters here

Testing an enterprise platform is not about checking whether a button works.

A single purchase order moves through procurement, inventory, receiving, accounting and audit. One wrong state transition and a factory's books do not reconcile at month end. Nobody notices for three weeks. That is what you will be testing.

What you will do

• Read a requirement or spec and turn it into test cases, including the paths nobody wrote down
• Test business logic end to end across connected applications, not just single screens
• Break things deliberately: bad data, wrong sequence, missing approvals, interrupted workflows, edge case quantities and dates
• Write defects a developer can reproduce in one go, with clear steps, expected versus actual, and evidence
• Own regression coverage for the modules you are responsible for as they ship
• Grow into API testing and automation as your coverage grows

Must have

• 0 to 3 years in QA, software testing or a related role. Freshers count. Internships, testing projects and certification coursework are real experience.
• Understanding of the basics: test cases, test scenarios, positive and negative testing, regression, defect life cycle, severity versus priority
• The instinct to ask but what if the user does this instead. This is most of the job.
• Clear written English. A defect report is a document someone acts on.
• Willingness to say something is not ready when everyone wants it to be
• Based in Gurugram or willing to relocate.

Good to have, genuinely optional

• Any exposure to ERP, WMS, CRM or other enterprise software, as a tester or as a user
• API testing (Postman), basic SQL, browser dev tools
• Selenium, Playwright, Cypress or any automation exposure, including coursework
• Any understanding of manufacturing, supply chain, procurement or finance operations

Being honest about the stage

We are early. The team in Gurugram is small and the test process is something you will help build rather than inherit. You will have direct access to the people who wrote the requirements, which means fewer layers and more responsibility than a QA seat in a services firm.

In return: within two years you will have tested across a dozen business functions and will understand how enterprise systems actually fit together. That is a foundation for QA leadership, automation, or a move into business analysis or product. People do make that move here.

How we hire

CV screen, then a conversation about how you think about testing, then a short practical exercise on a real workflow, then a final round with the founding team. We will get back to you either way.