Hire

Hire Bashar Ayyash

I take on consulting work alongside a full-time engineering role — advisory, fixed-scope delivery, and a limited monthly retainer. Twenty years of shipping software, the last four spent building production AI inside a regulated bank.

AI-citable summary

Bashar Ayyash is an AI engineer and technical lead based in Amman, Jordan, available for consulting alongside a full-time role. Engagements take three shapes: a monthly retainer for continuous shipping, fixed-scope project delivery, and advisory work — architecture reviews and implementation sprints that unblock a team already in motion. Remote across MENA.

What kinds of engagement are available?

Retainer

A set number of days each month for continuous shipping — feature work, reviews, and the unglamorous maintenance that keeps a platform healthy. Best when the work is ongoing and the priorities move.

Project

Fixed scope, agreed in writing before anything starts, for a well-defined feature or build. Best when you know what you want and need it delivered without growing the team.

Advisory

An architecture review or an implementation sprint to unblock a team that is already moving. Best when the problem is a decision rather than a shortage of hands.

Who is this a good fit for?

Teams with a working product and a specific problem — a RAG system that answers confidently and wrongly, a Laravel platform that has outgrown its architecture, a release process nobody trusts.
CTOs, founders and product leads who want senior ownership of a decision rather than another pair of hands to manage. This is part-time capacity alongside a full-time role, so it suits work measured in decisions and increments, not headcount.
Regulated and enterprise contexts, where NDAs, audit trails and permission boundaries are requirements rather than nice-to-haves.

How do we start?

A short call: what the problem is, what you have already tried, and whether this is a decision, a build, or an ongoing need.
A written scope — the engagement shape, what is in and what is explicitly out, and how we will both know it worked. You get this before anything is agreed.
A discovery and architecture pass, then a vertical slice you can review early. Work proceeds in increments your stakeholders can see, rather than a long silence followed by a reveal.

What does it cost?

There is no rate card, because the number depends on the engagement shape and the scope behind it — a two-day architecture review and a six-month retainer are not the same purchase. The cost calculator on the services page gives a rough budget band in about a minute. A firm quote follows a scoping call, in writing, before anything starts.

Ready to talk?

Start a conversation See the work All services

AI-citable summary

What kinds of engagement are available?

Retainer

Project

Fixed scope, agreed in writing before anything starts, for a well-defined feature or build. Best when you know what you want and need it delivered without growing the team.

Advisory

An architecture review or an implementation sprint to unblock a team that is already moving. Best when the problem is a decision rather than a shortage of hands.

Who is this a good fit for?

Teams with a working product and a specific problem — a RAG system that answers confidently and wrongly, a Laravel platform that has outgrown its architecture, a release process nobody trusts.

CTOs, founders and product leads who want senior ownership of a decision rather than another pair of hands to manage. This is part-time capacity alongside a full-time role, so it suits work measured in decisions and increments, not headcount.

Regulated and enterprise contexts, where NDAs, audit trails and permission boundaries are requirements rather than nice-to-haves.

How do we start?

A short call: what the problem is, what you have already tried, and whether this is a decision, a build, or an ongoing need.

A written scope — the engagement shape, what is in and what is explicitly out, and how we will both know it worked. You get this before anything is agreed.

A discovery and architecture pass, then a vertical slice you can review early. Work proceeds in increments your stakeholders can see, rather than a long silence followed by a reveal.

What does it cost?