It does not just add seats up, it argues with you: QA for a team of three, a tech lead at five, and a plain note when our suggestion differs from your pick. Then it sends the whole brief in one click.
The builder
0Or just describe it in a sentence
This is a keyword matcher running in your browser, not an AI model. The text does not leave this page until you send the brief.
1Roles and levels
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.
Where your team sits
Engagement length
When you want to start
Do you have engineering leadership today
Engagement model
Recommended team
Or write a sentence in the first field and let the assistant propose a shape.
The rules
Three or more engineers with no QA: we add a QA seat and say why.
Five seats and no engineering leadership on your side: we add a tech lead.
Four engineers and nobody on infrastructure: half a DevOps seat.
A managed team with no product management: we add a product manager, because we carry the outcome.
We recommend the model against the team that will actually exist, additions included, and say so when we disagree with your pick.
FAQ
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.
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.
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.
Next step
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.
Typical response within one business day · everything you share is treated as confidential
