Who is Asad Kissana?

Two names, one person

Asad Kissana is the short form. Muhammad Asadullah Kissana is the full name on formal records, and Asadullah Kissana is what he uses professionally. Which one you find depends on where you are looking — the shorter version is what most people type. The spellings page covers the variants in full.

This page is about the side of his work the job title does not cover: he runs a company.

Founder of aimEncoders

aimEncoders is a web and software development studio he founded and still runs. Its own site is https://aimencoders.com.

It builds:

• Responsive business websites and marketing sites
• Custom full-stack web applications
• eCommerce stores
• Admin dashboards and internal tools
• Cross-platform mobile applications

Typically on Next.js, React, and Node.js, with PostgreSQL or MongoDB behind them.

Why a QA engineer running a studio is unusual

Most small studios treat testing as the thing that happens if the budget survives to the end of the project. The result is predictable: the client finds the bugs, in production, and the fixes cost several times what they would have cost during the build.

At aimEncoders the person running delivery tests software for a living. Test planning, API validation, and cross-device verification are part of the build rather than a phase that gets cut. That is the studio's actual differentiator, and it is not a marketing line — it comes from the founder's day job being release sign-off on booking platforms where a defect moves money.

It also sets the ceiling on what the studio takes on. Projects are scoped around what a small team can deliver properly. Turning work down is preferable to shipping something he would have rejected as a tester.

Running both at once

The obvious question is whether the two roles compete. They pull in the same direction more than they conflict:

The studio keeps him building. Testing a Next.js application is a different kind of knowledge from building one. Doing both means he reads a codebase rather than only its interface, and that changes the quality of the defects he can find.

The day job keeps the studio honest. Sitting in release sign-off on production software is a constant reminder of what happens to shortcuts taken during a build.

Neither is a hobby. The studio is a real commercial operation with a small team of developers, and the full-time role is a lead QA position, not a passenger seat.

How the time actually splits

The honest version, because "founder plus full-time role" invites scepticism:

The QA role is the weekday commitment and takes priority. Release schedules do not move, and a product waiting on sign-off does not care what else is happening. Studio work sits around it — scoping and client conversations outside working hours, delivery coordinated with the developers who do the building.

That constraint is exactly why the studio stays small and states its scope narrowly. A studio promising enterprise-scale delivery on that arrangement would be overselling, and the person making the promise tests software for a living.

The through-line

Both roles come down to the same instinct: treat the happy path as the least interesting case. In QA that means asking what happens when a payment succeeds but the confirmation fails. In a build it means designing for that case before it becomes a defect.

Working with him

Through aimEncoders for a build, or directly for QA contracts and consulting. The services page covers what he offers personally; the aimEncoders page covers the studio. Either route starts at the contact page, or email kissanaasad217@gmail.com.