Servicepath Job Board Job Board / Quality Assurance Manual Engineer (06 Month Contract) / Apply Quality Assurance Manual Engineer (06 Month Contract) Personal Information First Name * Last Name * Email * Phone * Country * Postal Code * Professional Details Resume * Resume must be larger than 0 bytes and less than 25 MB. Cover Letter Cover Letter must be larger than 0 bytes and less than 25 MB. Personal Information Are based in Pakistan and able to work UK-aligned hours? * Are you available for a 6-month contract (with possible extension)? * What is your earliest start date? * Considering this is a contract role paid in USD (non-taxable), please state your expected monthly rate in USD. * Please provide your updated active LinkedIn Profile link. * Describe your QA experience split between manual and automation testing. For each, give a specific example of a project where you applied that approach — what was the product, what did you test, and what was your role in deciding the test strategy? * Which test management tools have you used (e.g., Xray, Zephyr, TestRail)? Pick one and walk us through how you used it on a real project — how did you structure your test cases, track execution, and produce sign-off evidence? * Give a concrete example of how you've used an AI tool (e.g., ChatGPT, Copilot, or similar) to improve your QA work. What was the task, what did the AI help you do faster or better, and what was the outcome? If you haven't used AI in QA yet, describe how you would apply it to test case generation or gap analysis. * Describe a feature or module where you owned testing from requirement through to sign-off. What was the feature, how did you build the test plan, what decisions did you make about coverage and risk, and how did you document and communicate your sign-off? * We rewrite modules from Angular to React with redesigned UX flows, not a 1:1 translation. If I hand you a legacy Angular module and its new React replacement with different user flows, walk me through your first 48 hours. What do you look at first, who do you talk to, and what do you produce before you start executing tests? * How would you build the evidence trail proving the new React version covers what the old Angular version did? Be specific — what artefacts do you produce, how do you structure them, and where does someone find them six months later during an audit? * Name the AI tools you use for QA work. Pick one and give me a specific example: what was the testing task, what exactly did you prompt or ask the tool to do, and how did the output change what you would have done manually? We're looking for real workflow integration, not experimentation * What do you think the biggest QA risks are when the UI flows have changed but the underlying business logic must stay the same? Give an example from your experience — or describe a specific scenario — where this kind of mismatch caused a defect that was easy to miss. * A feature works differently in the new React version by design, but a client insists the old Angular behaviour was correct. Walk me through exactly how you handle this — who do you involve, what do you document, and how do you make sure it doesn't block the release? * Angular and React versions will coexist for months — some clients on legacy, others migrated. How would you structure regression testing to cover both without doubling your effort? Be specific about how you'd organise your test cases, what you'd share between the two, and where you'd draw the line on coverage. * Submit