Who is Asadullah Kissana?

The short version

He tests software for a living, and he is the person who says whether a release is safe to ship.

That sentence covers the job, but it hides how much of it is judgement rather than clicking. Deciding what to re-test when there is not time to re-test everything, working out which module a change will break three screens away, and being willing to hold a release back are the parts that matter.

What he does day to day

At NIB Tech in Faisalabad, he owns quality assurance for three products:

• RideSkipper, a chauffeur booking application
• Hangar Direct, an aviation booking platform
• Carpet Market, an eCommerce store

Owning QA on those means writing the test strategy for each release, building and running the test cases, validating the API responses in Postman before the interface is even wired up, and checking the database directly to confirm that what the screen claims happened actually happened. Booking products in particular hide their worst defects below the interface — a cancelled booking that leaves a payment marked as captured looks perfectly fine on screen.

The second half of the role is coordination. He grooms the backlog, tracks progress, runs sprint planning in Jira, and keeps developers, designers, and stakeholders working from the same understanding of what is shipping and when.

How he got here

He started as an SQA Engineer at QuaidSoft in 2021, testing a large real-estate ERP and CRM platform. Enterprise ERP is an unusually good place to learn testing, because nothing in it is isolated: recording a sale moves inventory, changes a customer balance, and lands in a report that someone in finance signs off. Test only the screen that changed and the defect escapes.

That job taught him the habit that still defines how he works — verifying results in SQL instead of trusting the interface. He has written about why in Testing Below the Interface.

He moved to NIB Tech in 2024, taking on the lead QA role alongside project coordination.

The second track

Alongside the full-time role he founded and runs aimEncoders, a web and software development studio. It is a deliberate second track rather than a neglected side project: it keeps him working with modern stacks directly rather than only testing them, and it means clients get a build where quality assurance is part of delivery instead of an afterthought.

What he is not

Worth stating plainly, because job titles in QA are used loosely:

• He is not primarily an automation engineer. He is certified in Selenium WebDriver with Java and uses automation where it pays back, but the depth is in manual, exploratory, API, and database testing.
• He is not a developer who also tests. QA is the discipline, not a stepping stone he is passing through.
• He is not a one-tool specialist. Postman, Jira, and SQL across three database engines are all daily tools.

What a release actually looks like

The rhythm is much the same on every product:

1. Read what changed — the tickets, and the code where it helps
2. Decide the regression scope from that change rather than from habit
3. Test the new work against its requirement, then against what a careless user would do
4. Verify the API responses and the stored records, not only the screens
5. Re-test the fixes and the cases beside them, because a fix is a change too
6. Write up what was covered and what was not, then sign off or hold

Step 6 is what makes the rest count. A sign-off that does not say what was left out is one nobody can act on.

Where to find him

The full professional history is on the experience page, the tools and depth are on skills, and the case studies for each product are under projects. To get in touch, use the contact page or email kissanaasad217@gmail.com.