Full-Stack Engineer

Some engagements are small enough that one engineer owns whole slices of a product: the table, the endpoint, the screen, the empty state, the email that goes out afterwards. If that reads as satisfying instead of exhausting, keep going.

The stack is TypeScript end to end: React or Next.js in front, Node services behind, Postgres underneath. You'd join a team of four to eight and stay with the product long enough to see it used in anger.

Fintech, logistics and travel clients means a new domain every few months and a lot of questions asked out loud, which is the fastest way to learn anything.

AI is part of how we build, not a side project. Agents take the repetitive half of the work, which is exactly why the interesting half arrives faster and why the bar for your judgment is higher.

• Own features end to end. Start from what the user is trying to do, finish with it working in production.
• Cut the schema and the API. Design the slice your feature needs, and keep it consistent with what's already there.
• Cover the whole surface. Validation, errors, permissions, empty states, and the notification nobody remembered to ask for.
• Leave a trail. Tests that save the next person and notes that save the client's team.
• Show your work. Demo it weekly, take the feedback, and turn it round without drama.

• Three Years Across the Stack: real production work on both sides, not one side plus curiosity about the other.
• React and Next.js on the Front: app router, server components, and forms that behave under bad input.
• Node and Postgres on the Back: an API you designed, a schema you migrated, and a query you had to make faster.
• One Product End to End: at least one where you wrote both halves and lived with the seam between them.
• Tests on Both Sides: Vitest or Jest underneath, Playwright over the top, aimed at the flows that matter.
• Deploys Without Ceremony: Docker, a CI pipeline, and a preview environment you're willing to send a client.
• Review Hygiene: small pull requests, descriptions that explain the why, and reviews that leave the code better.
• TypeScript Everywhere: React and a Node backend, or equivalent experience you can map across in a fortnight.
• SQL Beyond SELECT *: joins, indexes, and a sense for why the page takes four seconds.
• Comfortable Being The Expert: sometimes you're the only person who knows how a feature works, so you document like it.
• Asks Rather Than Guesses: you know which questions are worth a client's time, and you ask those.
• Fluent English, Written and Spoken: most of our work happens in a written thread or on a call, and both have to be clear. Arabic is a genuine advantage across the region.
• AI in the Loop: you already build with coding agents and can say where they earn their keep.

• Adaptable: a new domain every quarter sounds like variety, not chaos.
• Owner: if it's broken and yours, you fix it without waiting for a ticket.
• Low ego: you'd rather ship the right thing than win the design debate.

• Agency or studio experience, so you know what a clean handover looks like.
• React Native or Expo for the occasional mobile stint.
• An eye for interface detail, so a designer's absence doesn't show.

• Remote across MENA. Work from wherever you are in the region, with hours built around your team's overlap rather than someone's attendance spreadsheet.
• Work that ships. Products go live in weeks, not quarters. When someone asks what you have been building, you can open it on your phone and show them.
• Small teams, no ticket queue. Four to eight people carry a product from the first client call to handover. Nobody hands you a spec and disappears.
• Kit and tools you choose. A budget for your setup, and for the editor, licenses and services that make you fast. No three-week procurement saga.
• A learning budget with time attached. Money for the course or the conference, plus room in the week to use it. The second half is the part most places skip.
• Client contact from day one. You sit in the room where the decisions get made. Plenty of engineers wait a decade for that seat.
• Time off people take, and no timesheets. We measure engagements, not humans in fifteen-minute increments. Book the holiday, go, come back.