Girmairi for Saudi Arabia:Read the Vision 2030 brief ↗
TeamsSolutionsResourcesCompanyBlogRate cardFAQ
Get in touch

Teams/QA Automation

QA automation engineers

Test suites that catch bugs before your customers do. Dedicated QA automation engineers working from our Dhaka office, wired into your CI and your hours — on one US contract, at flat monthly rates.

PlaywrightCypressSeleniumAPI testingCIRegression

ci · test-run

01auth.spec.ts ✓ 12 passed · 8.4s

02checkout.spec.ts ✓ 21 passed · 14.2s

03api.spec.ts ✓ 34 passed · 5.1s

04retries 0 · flaky 0

05report uploaded → ci artifacts

06suite green · safe to ship

E2E

passing

API

passing

Visual

stable

Why QA automation

The difference between shipping fast and shipping scared.

Without automated tests, every release is a gamble and every refactor is a risk. Good QA automation engineers give your team a green light it can actually trust — so you ship on a Friday without holding your breath. We vet for judgment about what to test, not just tool fluency.

01

Test strategy

Deciding what to test, at which layer, and what to skip. A suite without a strategy is just slow noise.

02

E2E coverage that stays fast

Critical user journeys covered end to end — and a suite that still finishes in minutes, not hours.

03

API & contract tests

Most bugs live below the UI. Testing at the API layer catches them earlier and runs far cheaper.

04

Flake discipline

A flaky test is worse than no test — the team stops trusting green. Stable selectors, real waits, zero tolerance for retries-as-a-fix.

05

CI integration

Tests that run on every push, block bad merges, and report clearly. Automation nobody runs is shelf-ware.

Tooling

The tools we staff.

Tell us what you run — we match from our pipeline. These are the testing tools we most commonly place.

ToolWhat we use it forWhere it shows up
PlaywrightModern E2E and component testingOur default for new web suites
CypressE2E for JavaScript-heavy frontendsTeams already invested in it
SeleniumCross-browser and legacy coverageEnterprise apps, older estates
Postman / newmanAPI test collections in CIBackend and integration coverage
supertestAPI tests inside the codebaseNode.js services
k6Load and performance testingCheckout flows, launch readiness
CI reportingDashboards, traces, failure triageGitHub Actions, GitLab, Jenkins
Credentials

Credentials & signals.

Certifications aren't how we vet — our pipeline is. But they show what the market here trains for. ISTQB is widespread in Bangladesh, backed by an engineering-school pipeline — BUET, University of Dhaka, NSU and others — and a strong competitive-programming culture. Real suites matter more than paper, so we weight both.

Credential / signalSourceWhat it signals
ISTQB Foundation LevelISTQBVery common here — shared testing vocabulary and basics
ISTQB Advanced — Test Automation EngineerISTQBDesigning automation architecture, not just writing scripts
Real Playwright / Cypress suitesTheir own workThe strongest signal — we read the actual code
API test collectionsTheir own workComfort testing below the UI, where most bugs live
Open-source test contributionsGitHubCode that survived review by strangers
Vetting

How we vet a QA automation engineer.

Five stages before you meet anyone — and you still interview last and make the final call. Nobody joins your team without your sign-off.

  1. 1Test-strategy conversation
  2. 2Live automation exercise
  3. 3Selector and flake-handling depth
  4. 4Review of a real suite they built
  5. 5English & communication screen
Engineers pairing at a desk in Girmairi's Dhaka office
Meeting corner in Girmairi's Dhaka office
The engineering floor at Girmairi's Dhaka office
Training hall in Girmairi's Dhaka office

Our office in Dhaka — where your team sits. Real photos, real people.

Frequently asked questions

With Girmairi, a dedicated QA automation engineer is a flat monthly seat: junior from $1,500, mid-level $2,200, senior $3,200, and lead $3,800 per month. The rate includes the office, equipment, HR, and management, and is billed monthly in advance in USD. The full rate card is at /pricing#quality.

A full-time Playwright or Cypress automation engineer costs $2,200 per month at mid-level and $3,200 at senior level, with leads at $3,800. These are flat monthly rates for a dedicated, full-time engineer working your hours and your CI — not hourly freelance billing.

Girmairi's QA automation engineers are full-time employees working from its managed office in Dhaka — no freelancers or scattered contractors. Each engineer works exclusively for one client, on that client's timezone, Slack, and standups.

Yes. Girmairi vets each engineer first — including a live automation exercise and a review of a real test suite they built — then the client interviews last and makes the final call. Nobody joins the team without the client's sign-off.

The contract is with Girmairi LLC, a US company, so it works like any US vendor relationship: one monthly invoice in USD, billed in advance. An NDA and full IP assignment are signed before any work begins, so the client owns 100% of the test code.

ISTQB certification is widespread among QA engineers in Bangladesh and common in Girmairi's pipeline, including the Foundation and Advanced Test Automation Engineer levels. Girmairi vets on real Playwright, Cypress, and API suites rather than certificates alone, so certifications are a signal, not the bar.

Girmairi replaces the engineer from its pipeline under a replacement guarantee. A bad fit is Girmairi's cost, not the client's.

Yes — teams of 3 or more seats, or 12-month commitments, get 5–10% off the flat monthly rate. Every client company also gets one hour per month with Girmairi's founder, a working CTO, included at no extra cost.

QA automation seats are on the standard rate card.

Same flat monthly rate, same includes — office, equipment, HR, management, replacement guarantee.