The questions every CTO asks before hiring engineers in Jordan

Yes, and it is the start we recommend. One engineer on a three month engagement is the cheapest way to test us. If it works, scale. If it does not, your downside was capped and visible from the start.

For roles where we have a standing pipeline: a first shortlist within 5 working days of a clear brief, and your interviews the week after. The actual start depends on the engineer's notice period with their current employer, and Jordanian labour law requires a month on indefinite contracts. Realistic total: 3 to 6 weeks. We publish both numbers deliberately: anyone publishing "48 hours" alone means time to shortlist, not time to start, and is offering you whoever is unoccupied rather than the best people in the market.

Folowise employs them in Jordan on a formal employment contract, and pays salary, social security and applicable taxes. You pay Folowise one monthly invoice. There is no direct contractual relationship between you and the engineer, which is what protects you from worker-classification exposure.

We start the replacement search immediately at our cost, and we do not bill you for an empty seat. We commit to a replacement shortlist within 10 working days, and to covering knowledge transfer from the departing engineer during their notice period. What we cannot commit to is that a replacement arrives just as fast for a rare role. We will tell you the truth on day one, not in week four.

Within the first 30 days: tell us, and we replace at no additional fee and with no notice period charged to you. After that, a standard 30 day notice applies. We ask one thing in return: tell us in week two if it feels wrong, not in month three. Most mismatches are fixable when raised early.

Yes, and without explaining why. Our assessment decides who reaches you; it does not replace your decision. If you reject three candidates in a row, we stop sending and re-read the brief with you, because the problem is probably our understanding of the need rather than the candidates.

A fixed monthly price per seat for the hours you committed to, from the same published price book. Invoiced at the start of the month on 15 day terms. The price includes salary, employer costs, equipment and operational support. Annual leave, Jordanian public holidays and sick leave are inside the price: nothing is deducted and nothing is added. Capacity changes on one month's notice; sustained overtime is not included, and we usually refuse it because it burns the engineer out within two months.

Yes, fully. Every role and level has a published monthly price at full capacity, and a commitment curve that shows the hourly rate at every hour count. Move the hours on any role page and the number moves in front of you, and every page reads from the same price book, so you will never find two different numbers for the same seat. The final price is written after one call, but it starts from these numbers, not from a blank page.

The practical difference: an outsourcing firm sells you a fixed-scope project and leaves at handover. We sell you ongoing engineering capacity that stays inside your team, assessed by engineers who actually build software at Folowise. The second difference: we tell you when we are not a fit. Read the "do not pick this" box on every engagement model page.

Partially, and honestly. With Europe and the Gulf the overlap is near total with no adjustment. With US East we propose a Jordan day of 13:00 to 22:00 which gives five hours of overlap, we get the engineer's consent for it, and we price it into their salary. With the US West Coast we advise against a full shifted day and propose a three hour bridge window with structured async handover. Full numbers are on the timezone page.

You do, and the mechanism is worth a minute because it is not what you expect. Jordanian copyright law does not adopt US work-for-hire: commissioned work vests in its author by default, a blanket assignment of future works is of uncertain effect, and moral rights cannot be assigned away. So we transfer ownership through a written assignment per deliverable instead of one broad clause. The practical outcome for you is the same, but the route is different, and we would rather you heard it from your own counsel before signing than after a dispute. The open source policy is agreed in writing before work begins, and we do not put a copyleft-licensed library into your product without your approval.

That is exactly what the commitment curve is for: pick fewer hours on the role page and you will see the hourly rate rise, because recruiting, social security and leave costs do not shrink with the hours. Every role shows its published minimum on its own page, higher for engineering roles and lower for roles like QA and design. Below the minimum you probably need a short consulting engagement rather than a standing seat, and the Folowise Expert Network is a better fit; we will point you there.

Yes. Every engineer in the network is based in Jordan and Arabic-native, and works in English for documentation and code review as the region does. For a Gulf client that means meetings without a language barrier; for a Western client, a recorded English score that reaches you with the profile.

No. The engineer is employed by Folowise in Jordan and works remotely, so they do not count toward Nitaqat or Emiratisation because they are not on your entity's payroll. If you need seats that count, that is local hiring, and we say so on the first call rather than let you find out at renewal.

Yes, in three forms, each with its published multiplier in the price book: remote from Amman, the default and the fastest; hybrid with a quarterly visit from the tech lead or product manager; or full relocation to your office. Relocation needs a work visa and residency and 8 to 14 weeks before day one, and the visa is a decision we do not control.