Software QA Engineer / Junior QA Engineer

What You Bring

Must-have:

• Good understanding of software testing principles and methodologies.
• Ability to understand business requirements and translate them into meaningful test scenarios.
• Good analytical thinking and problem-solving skills.
• Understanding of functional testing, regression testing, and software defect life cycles.
• Basic understanding of API testing, including REST APIs, HTTP methods, status codes, and JSON.
• Ability to write clear test cases and actionable bug reports.
• Good communication skills in English, both written and spoken.
• Attention to detail, a willingness to learn, and a proactive attitude toward identifying quality risks.

Additional Expectations for QA Engineer (2–4 Years):

• Hands-on experience in functional, API, and integration testing.
• Ability to independently plan and execute testing for assigned features.
• Experience identifying edge cases, requirement gaps, and potential regression risks.
• Ability to investigate defects and communicate findings clearly to development teams.
• Experience with test automation is preferred.

Expectations for Junior QA Engineer (0–2 Years):

• Good understanding of software testing fundamentals.
• Relevant internship, academic projects, or practical testing experience is an advantage.
• Ability to follow test scenarios, investigate unexpected results, and document findings.
• Willingness to learn API testing, integration testing, and automation.
• Strong fresh graduates with good analytical skills are encouraged to apply.

Nice-to-have

• Experience with Playwright, Cypress, Selenium, or other automation testing tools.
• Basic knowledge of JavaScript or TypeScript.
• Experience with Postman or similar API testing tools.
• Familiarity with webhooks, JSON payloads, and third-party API integrations.
• Experience testing workflow-based, event-driven, or enterprise software systems.
• Basic SQL knowledge for data validation.
• Familiarity with Git, CI/CD, and Agile/Scrum development.
• Experience improving regression test coverage or transitioning manual tests to automation.

What We're Looking For

• Someone who understands why and how a feature should work, rather than simply following test steps.
• Someone who is curious and willing to investigate unexpected system behavior.
• Someone who can identify meaningful edge cases and question unclear requirements.
• Someone who takes ownership of assigned testing activities and follows issues through to resolution.
• Someone who values effective test coverage over simply increasing the number of test cases.
• Someone who is motivated to improve testing efficiency through automation and continuous learning.