Tech Lead

شرح موقعیت

Every engagement needs one person holding the whole technical picture: what we're building, why it's shaped this way, and what we'll curse ourselves for in six months. That's you, and it's a hands-on job. You still write code most days, usually the parts that set the pattern for everyone else. The delivery lead owns scope and commercials, so the client gets one technical voice and one commercial voice instead of a committee of five. Four to eight engineers on your team, a client team of varying technical depth, and a product that has to be handed over cleanly at the end. How those engineers grow while they're with you is yours too: pairing, same-day feedback, and your word when promotions come up. Hiring, pay and the ladder sit with the engineering manager, so you lead people without the admin. How your engagement uses agents is your call: which parts of the build are agent-first, what review looks like when a machine wrote the diff, and what you promise a client about how their software got made. Turn conversations into plans. Discovery goes in, an architecture and a delivery plan come out, with the risks written where the client can see them. Write the foundational code. The patterns others extend, built by you, then reviewed daily as the team builds on them. Make the build-or-buy calls. And explain them to a client who's paying for both options. Keep plan and reality together. Raise the slip the week it appears, not the week before the deadline. Run the technical conversation. Including the ones where the answer is no, or not like that. Grow the engineers on your engagement. Pair on the hard parts, give feedback the same day, and tell the engineering manager early when someone's ready for more, or struggling. Design the handover from day one. Documentation, access, runbooks and a walkthrough that leaves their team standing on their own. What we look for Six Years of Building: with at least one product you led technically from first commit to handover. Range Across the Stack: TypeScript at both ends, Node and Postgres, React and Next.js, and enough cloud to be dangerous. Architecture on Paper First: diagrams, decision records and trade-offs written down while changing them is still cheap. Integration Archaeology: legacy APIs, SOAP envelopes, CSV drops at 3am, and a credible plan for each of them. Cloud Fluency: AWS, GCP or Cloudflare, plus a view on what the client's own team can realistically operate. Reviews That Teach: you leave both the codebase and the people better than you found them. Estimates You Stand Behind: ranges with the assumptions attached, revised in public the week they move. TypeScript Depth: or enough depth elsewhere that picking ours up is a formality rather than a project. Decisions Under Deadline: you have made architecture calls with the clock running, and lived with them afterwards. Holds Ground, Changes Mind: you can disagree with a client's CTO, and concede gracefully when they're right. Early Warning System: problems arrive in writing, early, with options attached. Multiplier: the team gets better around you, and you don't keep the interesting work. 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 Practice Setter: you use agents heavily yourself and can define how a team and a client should use them. Personal traits Steady: when the client is anxious and the build is red, you're the calm one. Opinionated, loosely held: you argue hard and update quickly. Finisher: handover day matters to you as much as launch day. Agency or consultancy experience, where the client is in the room and the budget is finite. You have inherited someone's codebase and made it safe to change again. Two or three domains under your belt, so you spot a pattern repeating. Why you'd like it here 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.