Skip to content
A ready team

Backend and platform team, 3 seats from Jordan

Two backend engineers and DevOps. For APIs, services and deploy pipelines.

At a glance

Seats
3 seats
Availability
Available now
First shortlist
10 to 15 working days
Suggested model
Dedicated team
  • Estimate

    7,250 – 8,350 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

7,250 – 8,350 JOD

per month, estimated · 480h · 3 FTE · 15.00 – 17.50 JOD/h

  • 2 Backend engineerSenior · 160h · 13.25 – 15.50 JOD/h
    4,300 – 4,950 JOD
  • 1 DevOps engineerSenior · 160h · 18.25 – 21.25 JOD/h
    2,950 – 3,400 JOD
Request this package

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

Price by seniority

As composedSenior across every seat7,250 – 8,350 JOD
Mid-LevelDelivers a whole feature without close supervision5,875 – 6,775 JOD
SeniorOwns a subsystem and reviews others7,250 – 8,350 JOD
StaffOwns a problem that crosses several teams without managing them8,225 – 9,475 JOD
LeadOwns architecture and the quality bar9,025 – 10,400 JOD
PrincipalDecides what does not get built10,225 – 11,775 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

You have a working frontend or app, and the whole bottleneck is behind it.

Server towers joined through glowing pipes to a hexagonal core

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

    Reading the system before touching it

    Access, docs, a map of the services, and what your own team is afraid of in the current system. Understanding first; it is the cheapest fix there is.

  2. Week one

    A first endpoint through a full pipeline

    One small change through tests, review and automated deploy. If there is no automated pipeline, building it is task one, not feature one.

  3. Weeks 2 to 4

    The real work in risk order

    APIs and services land in the order that lowers production risk, with load tests on whatever will actually take load.

  4. Month two

    Monitoring and operating limits

    Dashboards, alerts and written service objectives. A system whose sickness you cannot see is one whose death you will.

  5. Month three

    Documentation that makes us replaceable

    Architecture decisions written down, runbooks in place, and your team able to operate what we built without us. That is a success criterion, not an option.

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