QA Engineer: Data-Driven Applications
API, UI & Data Validation
Hands-on API and UI testing required | Data validation experience valued
About the Role
We're hiring a QA Engineer to own quality across our procurement intelligence platform, from the screens and APIs our users interact with to the data behind them. You will test the product as a user would (UI), as a system would (APIs), and as a skeptic would (the data), confirming that what is ingested, stored and displayed is accurate and consistent. This is a QA engineering role, not a data engineering role. You will test and verify data pipelines, not build them.
What You'd Be Testing
UI: Contract views, category playbooks, supplier profiles, dashboards and in-app chat. We check that what users see matches what is stored.
APIs: The services that serve and update contracts, suppliers, categories and spend data, including request/response contracts, error handling, and authorization.
Data: Spend file ingestion, transformation and mapping, and storage. We trace data to every downstream surface to confirm it stays correct at each hop.
What You'll Do
• Design, execute and maintain functional, regression and exploratory test suites for web UI and REST APIs.
• Test APIs with tools such as Postman or REST Assured. Validate status codes, schemas, payloads, pagination, negative cases and security basics.
• Automate UI and API tests with frameworks such as Playwright, Selenium, Cypress or equivalent, and integrate them into CI/CD.
• Validate spend file ingestion end-to-end, from source file to stored record to downstream UI and API output (contracts, category playbooks, supplier master).
• Verify spend totals, supplier/contract field accuracy, and duplicate or near-duplicate records, comparing source files against what the product displays rather than trusting dashboard output at face value.
• Design edge-case tests: missing or malformed fields, inconsistent formats, conflicting supplier records, expired vs. active contracts, and template/schema mismatches.
• Use browser/network tools and logs to isolate whether a defect originates in the UI, the API, or the data layer.
• Build automated checks for ongoing quality monitoring, not just one-off spot checks.
• Partner with engineering and category/procurement teams to root-cause defects, write clear bug reports, and flag when a data model or template is missing a field it should capture.
You Might Be a Fit If You Have
• Required: Hands-on UI testing and API testing experience in web applications.
• Required: Experience with test automation (UI and/or API) and a working understanding of test strategy: smoke, regression, integration and exploratory testing.
• Required: A risk-based mindset, able to decide what to test deeply and what to spot-check under time constraints.
• Experience validating structured business data, and reasoning about what can break between a source file and the final record a user sees.
• Clear written communication: reproducible bug reports, evidence (screenshots, queries, logs) and good judgment on severity.
Nice to Have
• SQL, to independently verify data in the database.
• ETL / data pipeline testing experience, including log-based debugging across multi-step pipelines.
• Experience with procurement, sourcing, spend, contract or supplier data.
• Familiarity with orchestration tools, CI/CD, and Jira-based defect workflows.