Quality Assurance (QA) Engineer
Noxus
A complete application in a minute
Tailored resume and cover letter, ready to send.
Job summary
PT Noxus Ideata Prima builds enterprise application software for multinational corporations, state-owned enterprises, and Indonesian government institutions. We are seeking a detail-oriented QA Engineer to join a team that works in a spec-driven way, from the first draft of a specification through to release, ensuring that what we agreed, what we built, and what we verified all still line up.
In practice, you will help shape Functional Specification Documents (FSD) and write Gherkin scenarios
Qualifications
- Bachelor’s degree in CS/IT or related field.
- Minimum of 2 years in software quality assurance or testing.
- Experience in a specification-driven delivery process.
Responsibilities
- Join requirement and FSD discussions from the planning stage and push back on ambiguity before development.
- Write and review Gherkin scenarios and acceptance criteria.
- Define clear, measurable acceptance criteria for each feature including edge cases.
- Verify delivered backend, frontend, and integration code against FSD and acceptance criteria.
- Review unit tests for coverage, correctness, and alignment with acceptance criteria.
- Maintain and extend automated test suites inside CI/CD pipelines.
Skills
Education
Tools
Job description
Quality Assurance · Engineering Division · Full-Time
Hold the quality gate, from the first draft of a specification through to release.
Discipline Quality Assurance
Division Engineering Division
Type Full-Time
Experience Minimum 2 years
The role
We are looking for a detail-oriented QA Engineer to join a team that works in a spec-driven way. This is not a role that starts once the code is finished. You will be part of the delivery process from the first draft of a specification through to release, making sure that what we agreed, what we built, and what we verified all still line up.
In practice, that means helping shape Functional Specification Documents (FSD) and writing Gherkin scenarios with acceptance criteria that leave little room for interpretation. You will verify what developers deliver across backend, frontend, and integration layers, review their code against our engineering standards, check the security and performance testing they have run, and then lead the full QA cycle before anything ships.
We are looking for a detail-oriented QA Engineer to join a team that works in a spec-driven way. This is not a role that starts once the code is finished. You will be part of the delivery process from the first draft of a specification through to release, making sure that what we agreed, what we built, and what we verified all still line up.
In practice, that means helping shape Functional Specification Documents (FSD) and writing Gherkin scenarios with acceptance criteria that leave little room for interpretation. You will verify what developers deliver across backend, frontend, and integration layers, review their code against our engineering standards, check the security and performance testing they have run, and then lead the full QA cycle before anything ships.
About the company
PT Noxus Ideata Prima builds enterprise application software for multinational corporations, state-owned enterprises, and Indonesian government institutions.
Our engineering work spans a modern polyglot stack, including event-driven systems and long-running workflows. Our clients operate under real regulatory scrutiny, so quality is not something we check at the end. It is a discipline we apply at every stage of delivery.
01 You verify at every gate
Our delivery process is spec-driven and gated, and QA is the verifying party at each stage rather than the last pair of hands before release.
02 Quality that is written down
Requirements arrive as Functional Specification Documents and Gherkin scenarios, so what you are testing against is agreed in advance and not argued about afterwards.
03 Systems under real scrutiny
Audit, financial and government systems, where a defect has consequences and holding a gate is supported rather than resented.
What you will do
- Join requirement and FSD discussions from the planning stage, and push back on ambiguity before it reaches development.
- Write and review Gherkin scenarios (Given / When / Then) that turn business requirements into behaviour anyone can test.
- Define clear, measurable acceptance criteria for each feature, including edge cases, negative paths, and boundary conditions.
- Spot delivery risks early through test planning, analysis, and realistic estimation of effort and resources.
- Produce and maintain test plans, test cases, and traceability between requirements, scenarios, and coverage.
- Confirm that delivered backend, frontend, and integration code actually satisfies the FSD and its acceptance criteria, not just that it runs without errors.
- Review unit tests written by developers for coverage, correctness, and alignment with the agreed acceptance criteria.
- Validate API contracts, data flows, and system interactions using tools such as Postman or JMeter.
- Confirm behaviour across service boundaries, including event-driven and asynchronous workflows.
- Raise gaps between specification and implementation as soon as you find them, and see them through to resolution with the developer responsible.
- Compare delivered code against our internal standard practices, covering structure, naming, error handling, logging, and maintainability.
- Review findings from static and dynamic analysis tooling (SAST and DAST) such as Snyk, CodeQL, or Semgrep, and make sure they are addressed rather than quietly deferred.
- Check the performance testing developers have run, including whether the scenarios are realistic, the thresholds are sensible, and the results have been read correctly.
- Hold back sign-off when the evidence is incomplete, and write down clearly what is needed to close the gate.
- Design and run functional and end-to-end test suites for web and mobile applications.
- Run smoke tests on each build to confirm it is worth taking into a deeper test cycle.
- Carry out fuzz and negative testing to surface unhandled inputs, malformed payloads, and unexpected system states.
- Run regression and integration testing to confirm that new work has not broken anything that already worked.
- Handle non-functional testing (performance, load, stress, and security) and report results against agreed thresholds.
- Work across both manual and automated testing, and grow automation coverage where it will keep paying off.
- Track, document, and manage bugs, risks, and issues so that anyone can reproduce and understand them.
- Classify defects by severity and impact, and give stakeholders an honest read on release risk.
- Work with developers and cross-functional teams to trace issues back to root cause rather than patching the symptom.
- Coordinate with internal stakeholders and vendors so that testing stays aligned with business requirements and delivery runs smoothly.
- Bring ideas for improving our testing processes, tooling, and methods.
- Maintain and extend automated test suites inside CI/CD pipelines so quality gates run continuously instead of by hand.
- Explore AI-augmented and agentic testing workflows where they measurably cut effort or widen coverage.
What we look for
Education and experience
- Bachelor's degree in Computer Science, Information Technology, or a related field.
- Minimum of 2 years of experience in software quality assurance or testing.
- Experience working inside a structured or specification-driven delivery process.
- Working knowledge of code (for example JavaScript or Python), enough to read, write, and debug test scripts and to review application code during verification.
- Be able to use Git, you will be comparing code against specs, acceptance criteria, coding and engineering standards.
- A solid grasp of testing methodologies: functional, regression, integration, smoke, and end-to-end.
- Hands-on experience with automated testing frameworks such as Selenium, Appium, Cypress, TestNG, or similar.
- Experience writing and reviewing unit tests, and working with developers on unit-test coverage.
- Confidence with API testing tools such as Postman or JMeter.
- Experience with non-functional testing: performance, load, stress, and security.
- Familiarity with static and dynamic code analysis tools for finding vulnerabilities and code-quality issues.
- Familiarity with CI/CD pipelines and with wiring automated tests into them.
- Able to write and review Functional Specification Documents, and to turn requirements into Gherkin scenarios and acceptance criteria.
- Clear, precise writing. Your defect reports and verification results need to be reproducible and hard to misread.
- Comfortable holding a quality gate and explaining the reasoning behind a sign-off decision.
- Exposure to AI-augmented or agentic testing tools and workflows.
- Experience testing systems in regulated and enterprise environments such as audit, financial services, or government.
- Familiarity with event-driven or asynchronous architectures.
- Experience with fuzzy testing or property-based testing.
How you work
Skills we can check on a CV. These are the ones we ask about in the interview.
- 01 Strong attention to detail, with a habit of anticipating problems and finding the edge cases other people miss.
- 02 Proactive and adaptable, and comfortable in a fast-moving environment.
- 03 Willing to question specifications, implementations, and assumptions, including your own.
Three independent standards cover how we run the work, how we hold your data, and how we do business.
'/%3e%3cpath%20d='M101.744%2012.4726L102.894%2016.1947L99.0021%2013.2201L101.744%2012.4726ZM105.3%208.40937H100.488L99.0026%203.59473L97.5116%208.41047L92.7%208.40385L96.5965%2011.3834L95.1055%2016.1942L99.0021%2013.2196L101.408%2011.3834L105.3%208.40992V8.40937Z'%20fill='white'/%3e%3cdefs%3e%3clinearGradient%20id='paint0_linear_5593_1381'%20x1='90'%20y1='9.44471'%20x2='99'%20y2='9.44471'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20stop-color='%2300AD70'/%3e%3cstop%20offset='0.998594'%20stop-color='%2300B67A'/%3e%3cstop%20offset='1'%20stop-color='%23DCDCE6'/%3e%3c/linearGradient%3e%3c/defs%3e%3c/svg%3e){kind=small}
