Is Asadullah Kissana available for hire?

What he takes on

Contract QA. Testing an existing product: test planning, manual and regression testing, API validation in Postman, database verification, permission-matrix testing, and release sign-off. Either for a specific release or ongoing across a cycle.

QA consulting and process setup. For teams with no QA function yet. Establishing how defects get reported and triaged, what a regression suite should contain, what gets tested before a release, and how sign-off works — then handing it over as something the team runs itself.

Independent testing before launch. A product built by someone else, tested by someone who was not involved in building it. Consistently the highest-value engagement, because a fresh reader of a requirement finds assumptions the original team stopped being able to see.

Development through aimEncoders. Web applications, business sites, eCommerce, dashboards, and mobile apps — with testing part of delivery. See the studio page.

Full-time roles. Considered. He is currently in a lead QA position in Faisalabad and is not in a hurry, but is open to the right role — send the description.

How he works

Remote, worldwide. Based in Faisalabad on UTC+5. Afternoon overlap with Europe, evening overlap with the US east coast.

Scope in writing first. Every engagement starts with a scope discussion and a written estimate. Nothing begins on a verbal understanding.

Documented outcomes. You get the test cases, the defect reports, and a summary stating what was covered and what was not. That last part is not a hedge — a report claiming everything was tested is a report nobody can trust.

What he does not take on

Worth being direct, because a mismatch wastes everyone's time:

• Pure automation-engineer roles. He is certified in Selenium with Java and uses automation where it pays back, but his depth is manual, API, and database testing. A role that is entirely framework-building is a poor fit.
• Performance and load testing as a specialism. He checks that response times are sane against realistic data volumes. Dedicated load engineering is a different discipline.
• Penetration testing. He tests authorisation, role boundaries, and input validation as part of functional QA. That is not a security audit and he does not present it as one.
• Work he cannot deliver properly. Through the studio, projects are scoped around what a small team can do well. He turns down work rather than shipping something he would have rejected as a tester.

Rates and terms

Rates depend on scope, duration, and whether the engagement is through him directly or through aimEncoders. Describe what you need and you get a figure, not a brochure.

Starting

Email kissanaasad217@gmail.com or use the contact page. Useful to include:

1. What the product is and what stage it is at
2. Whether any testing exists now
3. Rough timeline
4. Whether this is a contract, a full-time role, or a build

Full contact routes are on the contact details page; the service list is on services.