Skip to content
A ready team

QA automation pod, 3 seats from Jordan

Two automation engineers and one manual tester. A release gate everyone trusts within three months.

At a glance

Seats
3 seats
Availability
We recruit for it
First shortlist
20 to 30 working days
Suggested model
Dedicated team
  • Estimate

    5,050 – 5,825 JOD a month

  • At full capacity

    Remote from Amman

The price

Configure the package, and the price moves with you

Configure the package

The price moves with every choice

How you engage

You choose each seat's monthly hours and the commitment curve prices it: more hours, better hourly rate. Capacity changes monthly on one month's notice.

Capacity per seat

Lower capacity is not a proportional discount: recruiting cost, social security and leave accrual do not shrink with the hours, so the hourly rate rises as the commitment falls. The full price curve is on each role's page.

Where the engineer sits

The engineer sits in our Amman office with their team and works in your tools and channels. This is the default and the fastest to start.

Engagement length

Where your team sits

Seniority

Optional add-ons

The price

5,050 – 5,825 JOD

per month, estimated · 480h · 3 FTE · 10.50 – 12.25 JOD/h

  • 2 Automation QA engineerSenior · 160h · 11.75 – 13.75 JOD/h
    3,800 – 4,375 JOD
  • 1 QA engineerMid-Level · 160h · 7.75 – 9.00 JOD/h
    1,250 – 1,450 JOD
Request this package

Prototype prices. The final price is written after one call.

Price by seniority

As composedMixed levels, and what we would recommend5,050 – 5,825 JOD
Mid-LevelDelivers a whole feature without close supervision4,350 – 5,025 JOD
SeniorOwns a subsystem and reviews others5,400 – 6,225 JOD
StaffOwns a problem that crosses several teams without managing them5,950 – 6,850 JOD
LeadOwns architecture and the quality bar6,400 – 7,375 JOD
PrincipalDecides what does not get built6,400 – 7,375 JOD

Every number here is an estimated range, not a final price. The final price is written after one call, against a real brief, a real timezone and a real term.

Who this is for

Best for you if, and do not take it if

Best for you if

A fast existing dev team where every release is a gamble and defects reach your customers before they reach you.

Robot arms testing a line of phone screens on a conveyor

The seats

The delivery playbook

The first ninety days, written in advance

Not marketing promises; this is how we actually run this kind of package. If we drift from it, this text is what you hold us to.

  1. Before day one

    Inventory of flows, not pages

    A list of what actually breaks your business when it fails: payment, login, sign-up. Testing starts where failure hurts.

  2. Week one

    A documented manual smoke pack

    A manual checklist covering the critical flows, used on every release from this week, before any automation.

  3. Weeks 2 to 4

    Automating the top flows in CI

    The highest-value flows become automated tests running on every change. A test that does not run automatically is forgotten within a month.

  4. Month two

    A regression pack and a flake budget

    Full regression coverage of the critical flows, and an explicit flake budget: a flaky test gets fixed or deleted, not retried forever.

  5. Month three

    A release gate everyone trusts

    Green means ship, no debate. And the honest metric: how many defects reached users this month compared to before we existed.

The subscription

What every month includes

  • A written weekly note

    What landed, what got stuck, what is next, readable in two minutes. No extra meeting unless you ask for one.

  • A monthly steering call

    Thirty minutes with you: priorities, levels, team size. Cancelled when there is nothing worth it; your time beats our rituals.

  • Leave visible in advance

    Team leave and Jordanian holidays in a calendar you see weeks ahead, not in an apology on delivery morning.

  • The replacement guarantee, ongoing

    Not only the first thirty days. An engineer who stops being right gets replaced in any month, and a vacant seat is never invoiced.

  • One invoice line per seat

    One monthly invoice, one line per seat, no surprises and no hidden fees. The number we agreed is the number that arrives.

  • A level review each quarter

    Is the level you pay for still the right one? Sometimes we advise down and lose invoice value, because the renewal matters more to us than the margin.

In every package

What is included, and what we do not promise

Included

  • The engineer is a Folowise employee on a formal Jordanian contract, not a loose contractor.
  • The final interview is yours, and you can say no without explaining.
  • Machine, licences, office and connectivity are on us.
  • Replacement inside the first thirty days with no invoice for the vacant seat.
  • IP assigns to you through a written assignment per deliverable.

Not promised

  • We do not guarantee the same engineer forever. People resign, and the replacement cost sits with us, not you.
  • We do not hold SOC 2 or ISO 27001, and we will not imply otherwise.
  • We do not sell "the top 1%". Nobody can evidence that number, us included.

FAQ

Before you order

01

Who runs the team day to day, you or us?

It depends on the model. On staff augmentation and a dedicated team you run it as part of your company. On a managed team we run it and you receive the outcome. The package suggests the best fit; the call is yours.

02

Can I change the package after we start?

Yes, monthly. Add a seat, remove one, or change its level on one month's notice. The package is a starting point, not a contractual cage.

03

What if I need to pause?

On one month's notice you can shrink or end the package. We do not sell a "pause" that holds seats free of charge, because the engineers are employees on real salaries, and anyone promising that is paying for it out of engineer quality.

04

Do I interview the engineers before we start?

Always. We send anonymised profiles, you pick who to meet, and the final interview is yours with the right to say no without explaining. Nobody starts on your team whom you did not approve.

Next step

Tell us what you are trying to ship

Not the headcount. Tell us the product, the date, and what team you have today, and we will propose the shape. If we think what you need is not more engineers, we will say so on the first call.

Send a briefBook a 20 minute call

Typical response within one business day · everything you share is treated as confidential