Software Engineering Lead

We’re hiring an Engineering Lead to join a small, highly technical team building real systems from ambiguous, real-world problems.

This role combines technical leadership and delivery ownership. It’s not a traditional Engineering Manager role — and not a full-time IC role either. You’ll shape solutions, guide architecture, and ensure high-quality delivery, while staying close enough to go deep when needed.

What you’ll do:

• Turn unclear partner needs into clear, implementable specs
• Set architectural foundations and make pragmatic technical decisions
• Break goals into executable phases and drive delivery
• Surface risks early and keep scope focused
• Review designs, unblock complex issues, and support the team’s growth
• Define what “done” really means — including reliability and operational readiness

What we’re looking for:

• Preferably 4+ years of software engineering experience

(We’re open to highly potential candidates with less experience.)

• Experience leading technical work or small teams
• Strong system-level thinking and sound technical judgment
• Experience designing services, APIs, or distributed systems
• High ownership, comfort with ambiguity, and clear communication

Nice to have: startup/small-team experience, hiring exposure, AI/data product experience.

Location: Doha, Qatar

If you’re interested in shaping real systems and owning outcomes — not just tasks — we’d love to hear from you.

Job Type: Full-time

Pay: QAR15,000.00 - QAR25,000.00 per month

Application Question(s):

• Describe one specific system you helped design.

What problem did it solve, what was your exact responsibility, and what is one technical decision you personally influenced?

• Describe a situation where requirements changed or were unclear.

What was the original misunderstanding, and what action did you take to clarify or control scope?

• Have you ever been responsible for breaking down work or planning delivery?

Briefly describe how you structured the work and how you handled risks or delays.

• What is one technical mistake you’ve made in a project, and what did you learn from it?
• Describe one decision where you had to choose between two technical approaches.

What were the trade-offs, and why did you choose the final approach?