💼 Hiring Quest – Senior QA Software Engineer (FoodTech Systems) @ Sahm Food

👋 We are Sahm Food, a fast-growing food & beverage technology company transforming how restaurants operate and deliver experiences across Egypt.

Our platform powers a full ecosystem including food delivery mobile apps (iOS & Android), a super admin dashboard, and restaurant management dashboards — along with integrated POS and CRM systems tailored for modern restaurant operations.

We’re building technology that connects kitchens, customers, and business intelligence into one seamless flow — and we’re looking for someone who can ensure every piece works flawlessly.

We’re now hiring a Senior QA Software Engineer (3–5 YOE) to take ownership of product quality across our mobile apps, dashboards, APIs, and internal systems.

🕓 Start Date: Immediate
📍 Location: On-site – Makram Ebeid, Nasr City
💰 Salary: 40,000 – 60,000 EGP
📌 Type: Full-time

🛠️ How the Hiring Quest Works

1️⃣ Register for the quest
2️⃣ Receive the full challenge instructions
3️⃣ Submit your solution before the deadline
4️⃣ Top candidates are invited to a technical QA review session
5️⃣ One candidate will be hired — others may be considered for future roles

👉 The technical session focuses on your thinking and understanding of your solution, so use AI as a support tool only — not a replacement for your own work.

🔍 Who We’re Looking For

1. ✅ 3–5 years of experience in manual QA

2. ✅ Strong experience testing web + mobile applications

3. ✅ Solid understanding of API testing (Postman / Rest Assured)

4. ✅ Experience working on CRM / ERP / POS systems

5. ✅ Familiar with Agile workflows and ceremonies

6. ✅ Strong bug reporting, communication, and analytical thinking

🎯 Your Mission: Test a Real FoodTech System

To simulate real-world QA challenges, you’ll test a food delivery + restaurant operations system similar to what we build at Sahm Food.

You can choose ONE of the following approaches:

Option A (Recommended)

Test a real food delivery app such as:

1. Talabat

2. Mrsool

3. Elmenus

Option B

Design a QA strategy for a hypothetical system with:

1. Customer mobile app (ordering food)

2. Restaurant dashboard (managing orders)

3. Admin dashboard

4. POS + CRM modules

🚨 The goal is to evaluate your QA thinking across systems, not just UI testing.

🧪 What You Should Submit

✅ Test Plan

• Define scope across mobile app, dashboards, and APIs

• Testing types: Functional, Regression, Integration

• Entry & exit criteria

• Risk areas (e.g., payments, order flow, syncing between systems)

• Prioritization strategy

✅ Test Cases

1. At least 12–18 test cases

2. Include:

   1-Preconditions

   2-Steps

   3-Expected results

   4-Status

Cover:

1. End-to-end order flow

2. Edge cases (e.g., failed payments, order delays)

3. Negative scenarios

✅ API Testing

1. Test 2–3 API endpoints (real or simulated)

2. Validate:

   1-Request/response

   2-Status codes

   3-Data integrity

✅ Bug Reports

1. Report 2–4 bugs or UX issues

2. Include:

   1-Steps to reproduce

   2-Expected vs actual

   3-Severity & priority

   4-Screenshots or logs

✅ (Bonus)

💡 Suggest one automation opportunity (what & why)

💡 Recommend a QA process improvement for a food delivery system

📝 Submission Requirements

⚠️ Real thinking over AI-generated answers

We care about how you think, not how polished your document is.

Generic, templated, or unrealistic submissions will be disqualified.

📦 Deliverables

📄 Test Plan

📋 Test Cases

🐞 Bug Reports

💡 Bonus (optional)

📹 Video Walkthrough (3–5 min)

1. Walk through your testing approach

2. Explain key bugs and priorities

3. Show how you think as a QA engineer

📊 Evaluation Criteria

1. Test Plan (structure & depth) – 30%

2. Test Cases (coverage & clarity) – 25%

3. Bug Reporting (quality & communication) – 20%

4. QA Thinking & Prioritization – 15%

5. Bonus (automation & insights) – 10%

📩 What Happens After Submission

Shortlisted candidates will be invited to a live QA review session, where we will:

1. Walk through your test plan and test cases

2. Discuss your bug reports and prioritization

3. Evaluate your understanding of real business workflows (orders, POS, CRM)

👉 Final decisions will be made within 5–10 business days after the review.