Portfolio ↗ · LinkedIn · GeekSSort · Explore my work ↓
I'm an SQA engineer and product builder based in Dhaka, Bangladesh. My work spans browser automation, API and performance testing, and web, mobile, and desktop applications.
I care about the details that decide whether software feels dependable: clear interfaces, useful error messages, correct calculations, permissions, and what happens when a connection drops. I enjoy building the product and investigating how it behaves under real use.
A selection of public projects across quality engineering and product development. The repositories include their setup, scope, and supporting material.
| Quality engineering | Product building |
|---|---|
|
Browser tests for registration, login, product search, carts, and checkout. Page objects, reusable fixtures, and screenshots, traces, and video for investigating failures.
|
An expense tracker with a distinct visual identity, BLoC state management, Firebase sync, and offline support. Built around quick entry and a clear view of spending.
|
|
A manual QA portfolio covering test planning, boundary analysis, case design, execution records, and structured bug reports.
|
A fitness and meal-planning app built around Bangladeshi routines: local foods, daily tracking, training, and a focused onboarding journey.
|
|
API performance tests with authenticated flows, staged load, endpoint-specific thresholds, validation checks, and HTML reports.
|
An AI sales-agent prototype and merchant inbox for Bangladeshi social commerce, with Bangla, Banglish, and English conversations.
|
|
A BDD automation framework for e-commerce search, pagination, and data extraction, using Cucumber scenarios and a Page Object Model.
|
The source behind my personal portfolio: a Next.js site with Sanity-managed content, responsive layouts, and motion.
|
Also worth a look: Postman API testing · Jest unit tests · Testing scenarios · My macOS toolkit
Automation with evidence |
Ledger |
Daur |
- Start with the journey. Understand what the person is trying to finish before choosing a tool or designing a test.
- Investigate failures. Reproduce the problem, trace the state and data, and keep evidence that explains the cause.
- Keep automation readable. Use clear scenarios, reusable fixtures, and reports that help someone debug the next failure.
- Review the actual experience. Check keyboard use, navigation, viewport behavior, empty states, and recovery paths in the app.
| Area | Tools and technologies |
|---|---|
| Quality engineering | Playwright · Cypress · Selenium · Postman · k6 · Jest · Cucumber |
| Web and backend | TypeScript · JavaScript · React · Next.js · Astro · Node.js · NestJS |
| Mobile and desktop | Flutter · Dart · SwiftUI · Electron |
| Data and delivery | PostgreSQL · SQLite · Firebase · Docker · GitHub Actions |
- Desktop POS and back-office workflows, with attention to offline behavior, printing, keyboard checkout, and onboarding.
- Product UX that helps people finish everyday tasks quickly.
- Sharpening my system-design and testing judgment through practical projects and failure analysis.
I'm happy to talk about software quality, test automation, product UX, and building useful apps.
siraajul.com · LinkedIn · GeekSSort
From Dhaka, Bangladesh · Building, testing, and learning in public.