Mojammel
Hossain
13 years in QA — I decide what to test and what to skip. 6 years in production React/Next.js — I build what I test. The development skills aren't a separate track; they're what make the automation sharper.
Playwright · TypeScript · Next.js · k6 · JMeter
Test strategy & scoping · CI/CD pipelines · Appium
Swipe →
Swipe →
All repos include a DECISIONS.md documenting every architectural choice — because the hardest part of QA isn't writing tests, it's knowing which ones matter.
Owned QA strategy — test scope decisions, automation architecture, and release quality — across a continuously rotating portfolio of USAID, UNICEF, and INGO-funded ICT-for-development projects shipping concurrently. Dual-tracked with frontend engineering on the same platforms. The development work wasn't a separate role; it was what made the test strategy sharper — I understood the code I was validating.
- —Managed test coverage decisions across concurrent projects spanning health, agriculture, humanitarian response, and governance — each with different domain rules, release cadences, and donor-reporting requirements. Deciding what to automate, what to smoke-test, and what to leave to structured exploratory testing was the core of the job.
- —Defined test criteria for platforms where incorrect data had real consequences: national vaccination tracking (mTika), maternal and child health registration (mCARE/MOVE-IT), nutrition growth monitoring, field-worker performance tracking for BRAC's health programme (12,000+ active field workers), and humanitarian camp service delivery.
- —Tested offline-capable Android field apps deployed in low-connectivity rural and camp environments. Validated offline data queueing, sync conflict resolution, and data integrity on field submissions — where a failed sync could mean a missed vaccination schedule or a lost patient record.
- —Validated data exchange pipelines between mPower systems and government/NGO platforms — DHIS2, Shared Health Record (SHR), BRAC ERP — ensuring immunisation records, patient data, and nutrition tracking survived integration boundaries correctly.
- —Verified domain-critical calculations: GMP z-scores for child nutrition, vaccination reminder trigger logic, weather-based crop advisory thresholds (GeoPotato/GeoBIS agricultural DSS), and multi-stage beneficiary tracking across programme interventions.
- —Designed smoke test suites targeting critical user flows and high-risk API paths, integrated into PR pipelines via GitHub Actions — enabling confident go/no-go decisions without slowing release velocity across multiple simultaneous project deliveries.
- —Led performance and load testing using JMeter (distributed) and k6 ahead of high-traffic field deployments. Supported Redis caching improvements that reduced response times under load.
- —Migrated automation suites to Playwright and CodeceptJS. Extended mobile coverage via Sauce Labs for cloud-based Appium execution across device configurations common in field deployments.
- —Mentored QA engineers, standardised practices across the automation stack, and embedded BDD scenarios using Cucumber to keep donor-required outcomes traceable to test coverage.
- —Built a reusable React component library serving multiple production platforms across international NGO and donor-funded programmes — designed for rapid plug-in across projects where deadlines are tight and rebuilding from scratch each cycle isn't an option.
- —Implemented state management using Redux and Context API across large-scale applications; applied memoisation (React.memo, useMemo, useCallback) to optimise rendering in data-heavy monitoring and reporting dashboards.
- —Collaborated with backend teams to define API contracts via Swagger/OpenAPI from day one; fixed frontend bugs directly in the codebase rather than filing tickets.
The school's legacy .NET system became unmanageable — years of ad-hoc requirements stacked on a codebase the original vendor no longer maintains cost-effectively. I was brought in to examine the system from a technical perspective, plan a clean replacement, and start delivering the modules they need now. Solo consultant, full ownership.
- —KPI Evaluation System — role-based performance reviews with multi-part weighted scoring. 604 evaluations across ~300 teachers, 36 observers, completed with zero data issues. HR configures sessions, observers submit on-screen, scores aggregate automatically.
- —Question Bank LLM Pipeline — Claude API extracts questions from legacy PDF past papers. Teachers review, correct, and approve. Live A4 paper builder with Cambridge-style cover generation and print-ready output. Eliminates hours of manual copy-paste and formatting.
- —Roster Manager — Python/Flask microservice that analyses teacher workloads per time slot and surfaces the least-loaded candidate for each duty window. Replaced a manual cross-referencing process that coordinators dreaded every cycle.
- —Data extraction & migration prep — reverse-engineered the legacy system's schema through the admin interface, exported critical records, and designed normalised data structures for the new platform. Migration pipeline is ready when the school greenlights the full rebuild.
- —This isn't a dev job I fell into. It's QA thinking applied at the systems level: validate the data before you trust it, build guardrails into the pipeline, ship incrementally, verify every evaluation before publishing.
- —Working solo means I own every layer — database design, API contracts, UI components, deployment, and the test suites that keep it all honest. When I say I understand the full stack, I mean I built one, alone, under real delivery pressure.
Built the foundations of mPower's test practice across a rapidly expanding portfolio of USAID, UNICEF, and INGO-funded MIS and MEAL platforms — health, agriculture, governance, education — each with distinct domain logic and stakeholder reporting requirements.
- —Executed functional, regression, and integration testing across concurrent ICT-for-development projects: national vaccination tracking, maternal and child health systems, nutrition monitoring platforms, agricultural decision support tools, disability information systems, and humanitarian response dashboards.
- —Applied structured exploratory testing on complex multi-module workflows — offline-capable Android field apps, web-based MIS dashboards, and data exchange pipelines feeding into DHIS2 and government health information systems — uncovering edge-case defects that scripted approaches routinely missed.
- —Defined and maintained structured test case libraries prioritised by risk, release scope, and donor-reporting impact — balancing coverage decisions across projects shipping on different cadences with different stakeholder urgency.
- —Introduced Selenium WebDriver automation for web platforms and set up in-house Appium infrastructure for mobile automation across Android and iOS field-worker apps — laying the groundwork for the automation strategy later scaled as QA Lead.
- —Authored and maintained automation suites using Cypress for newer web codebases alongside Selenium for legacy systems, establishing the multi-framework approach that carried forward.
Functional, regression, and integration testing on financial and ERP systems. Applied structured exploratory testing on complex ERP workflows, uncovering edge-case defects that scripted suites routinely missed.
Bachelor of Science in Computer Science & Engineering
Shahjalal University of Science & Technology, Sylhet, Bangladesh
Open to senior SDET, QA automation lead, and test architect remote roles.
Chattogram, Bangladesh · UTC+6 · EMEA-friendly hours