👋 We are Blu EV, a next-generation mobility company transforming how cities move.
Our mission is to make urban transportation cleaner, safer, and more affordable through electric two-wheelers and a smart, battery-as-a-service platform.

We combine flexible battery leasing, pay-as-you-go pricing, and maintenance-free operations — helping businesses and riders cut costs by up to 30% compared to traditional vehicles.

We’re now hiring a Quality Control Engineer (1–5 YOE) to help ensure the performance, reliability, and usability of our growing ecosystem.

🕓 Start Date: Immediate
🌍 Location: Hybrid – Cairo (3 days in-office, 2 days remote)
💰 Salary: based on experience
📌 Type: Full-time

🛠️ How the Hiring Quest Works

1. Register for the quest

2. You’ll receive full challenge instructions by email

3. Submit your solution before the deadline

4. Top candidates will be invited to a review session

5. One candidate will be hired — others may be considered for future freelance roles

🔍 Who We’re Looking For

1. 1–5 years of manual QA experience

2. Experience testing mobile apps and web platforms

3. Familiarity with API integrations, device-based workflows, and agile teams

4. Strong communication and prioritization skills

5. Exposure to automation tools like Selenium, Appium, or Postman scripts

🎯 Your Mission: Test a Real App (Yours or Ours)

To simulate how you’d test a real product in the wild, we want you to explore and evaluate one of the following apps:

• Blu EV App – Our real product for managing e-mobility, ride activity, and battery leasing

• Talabat – Food delivery platform

• Canva – Visual design and publishing tool

🚨 You decide which to test — and why.
We're evaluating your QA judgment, depth, and clarity — not your ability to follow scripts.

🧪 What You Should Submit

1. ✅ Test Plan

   1. Your goals, test scope, and types of testing

   2. Entrance criteria (when testing begins) and exit criteria (when it ends)

   3. Feature or area prioritization (what you’d test first and why)

   4. Test environment assumptions or limitations
      

2. ✅ Test Cases

   1. At least 10–15 cases

   2. Include: Preconditions, Test Steps, Expected Result, Status

   3. Cover normal flow, edge cases, and negative scenarios
      

3. ✅ Bug Report Example

   1. 1–3 clearly documented bugs or UX issues (can be real or hypothetical)

   2. Steps to reproduce, severity, actual vs expected, and attachments/screenshots
      

4. ✅ (Bonus)

   1. Suggest an automation idea: What would you automate first and why?

   2. Suggest a QA process improvement if you were part of the Talabat or Canva team

📝 What You Should Submit

⚠️ Real Work Over AI-Generated Answers

This challenge is designed to assess your personal QA thinking on real apps.

Submissions that are generic, templated, or misaligned with actual app behavior will be disqualified.

✅ Rough-but-real beats polished-but-fake.

1. 📄 Test Plan

2. 📋 Test Cases

3. 🐞 Bug Report(s)

4. 💡 (Bonus)

5. 📹 Video Walkthrough (3–5 min)

   1. Speak while showing your test flow

   2. Explain what you tested, what you found, and why it matters

📊 Evaluation Criteria

1. Test Plan (structure & logic) 30%

2. Test Cases (coverage & clarity) 25%

3. Bug Reporting (depth & communication) 20%

4. QA Prioritization & Mindset 15%

5. Bonus: Automation/Feedback 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 reported bugs and how you prioritize

3. Assess your QA mindset, business awareness, and communication style

👉 Final decisions will be made within 3–5 business days after your review.