The role You'll own meaningful features end-to-end — from an early product conversation through to production — with the support of a team that cares about getting it right together. There's room to shape how things are built, leave the codebase a little better than you found it, and grow into the parts of the craft you're curious about: mentoring, exploring new tech, helping plan the work. We're not looking for someone who already does all of this perfectly; we're looking for someone who's ready to keep growing into it with us.
Tech you'll work with

Core: React, Type Script, modern JS

Monorepo: Nx

UI: Ant Design (Antd)

Data: React Query, REST APIs from internal services

i18n: Arabic + English, RTL/LTR

State: Context API + React Query for the bulk

Tooling: Vite/webpack, ESLint, Prettier, Jest + React Testing Library

Workflow: Git, trunk-based PR culture, code review before merge


What we look for Must-have

2+ years shipping React in production, with strong Type Script and Java Script fundamentals (closures, async, prototypes, the DOM).

Specialization in one or more areas of a frontend stack — components, state, data, performance, accessibility, tooling — and the initiative to learn the rest.

Medium-to-XL feature ownership — you can break down a complex feature, design it, implement it, ship it, and reduce technical debt in the area you touched.

Process push-back — when a team practice is slowing you down, you raise it with a reason and a proposal, not a complaint.

Code review fluency — you give reviews that are respectful, thorough, thoughtful, flexible, and not pedantic.

Documentation discipline — you contribute to features, procedures, and runbooks as part of shipping the work, not as an afterthought.

Communication — you write a clear PR description, walk through a tradeoff in standup, and ask the right clarifying question before writing code.

Curiosity about the why — you read product specs, not just tickets.
Nice-to-have
Monorepo experience (Nx, Turborepo, Rush).
Antd, React Query, or i18n libraries in production.
Experience evangelizing new tech to a team — bringing a POC, making the case, and either landing it or reading the room.
Mentorship experience — you've helped someone level up and you can talk about how.
Cycle/sprint planning contribution beyond your own queue.
Comfort communicating with external stakeholders directly.
Fintech, payments, or other regulated-industry experience.
Performance work (Core Web Vitals, bundle analysis, lazy loading).
Accessibility work (semantic HTML, ARIA, keyboard nav).
Comfortable in Arabic + English (we work in both).


How we hire Our process is humane, personal, and built around technical conversation — not gatekeeping. A few things we want you to know up front:

No AI in the loop — on either side. Every conversation is with a real person on the team. We don't screen with AI, we don't score you with AI, and we don't ask you to perform for one. We also ask that you don't use AI assistants (Copilot, Chat GPT, Claude, Cursor, etc.) during any part of the process — we want to see how you think and code, not how a model does. You'll have plenty of room to use those tools once you're on the team.

No take-home task. We won't ask you to spend your evenings and weekends building something for us before we've even gotten to know you.

No whiteboard puzzles or trivia. We're not interested in whether you can invert a binary tree under pressure. We're interested in how you think, how you build, and how you work with other people.
What you can expect instead: a handful of conversations with the people you'd actually work with, grounded in real engineering — the kind of code, problems, and tradeoffs you'd see on the team. We'll be transparent about where you are in the process, and we'll give you the same care and attention we'd want if the roles were reversed.