👋 We are CloudComTogether, empowering businesses across MEA, Gulf, LATAM, and beyond with scalable, secure, and AI-driven CPaaS solutions.
Our platform fuels business growth, retention, and customer lifetime value through personalized, omni-channel communication — enabling real-time learning, segmentation, engagement, and analytics.

We’re now hiring a Senior Software Developer (.NET + Angular, 5–7 YOE) to design and build core modules that power our omni-channel communication platform.

• 🕓 Start Date: October (latest November)

• 🌍 Location: Hybrid (3 days WFH after probation)

• 💰 Salary: Based On The Experience

🛠 How the Hiring Quest Works

1. Register for the quest

2. Receive full instructions via email after registration closes

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 roles

🔍 Who We’re Looking For

1. 5–7 years of professional software development experience

2. Strong in .NET Core (C#) with solid OOP and Clean Architecture practices

3. Proficient in SQL Server (schema design, indexing, performance optimization)

4. Comfortable with NoSQL for logs or analytics

5. Skilled in Angular 2+, HTML5, CSS3, TypeScript

6. Experienced in JWT authentication, RBAC, and secure REST APIs

7. Solid understanding of scalability, caching, and performance optimization

8. Bonus: background jobs, SignalR/WebSockets, or microservices

🎯 Your Mission: Design a mini CPaaS

Business Context

Design a mini CPaaS (Communication Platform as a Service) that allows enterprise customers to send SMS, WhatsApp, and Email messages for both OTPs and bulk campaigns.

Part #1: Your design should answer (only Design):

1. Architecture Overview

   1. Show a high-level diagram of the main components and how they interact.

   2. Use a clear architecture pattern

2. Message Flow

   1. Walk through how an OTP request is handled, including fallback if WhatsApp fails.

   2. Show how a bulk campaign (1M messages in 2 hours) would be processed.

3. Data & Storage

   1. What are the core entities (e.g., tenants, messages..etc)?

   2. Where are messages and events stored, and for how long?

4. Analytics & Logging

   1. Compare 3 possible systems you could use for logging events and generating delivery reports.

   2. Choose one and justify your decision.

5. Scalability & Reliability

   1. Where are the bottlenecks?

   2. How will you handle retries, provider rate limits, and webhook chaos (duplicates, out-of-order events)?

6. Infrastructure Sketch

   1. Describe briefly how you’d deploy this (compute, DB, queues/streams, cache).

   2. Mention one or two key SLOs/alerts you’d enforce.

Constraints

1. Traffic: 1,000 OTP/s peak, campaigns up to 1M messages over 2h.

2. Multi-tenancy: strict data isolation per tenant.

3. Providers: webhooks may be duplicated or arrive out-of-order.

Part 2 — You Decide the MVP & Implement It (Coding)

Add to the repo your MVP implementation and /docs/MVP.md (≈1 page) that states:

1. MVP Goal: the smallest slice that proves value for a mini-CPaaS

2. Scope now: features/endpoints/UI you will deliver

3. Out of scope: what you’ll defer and why

4. Assumptions & Risks

5. Time plan for a ~1–2 day focused effort

🧰 Tech Stack

• Backend: .NET Core (C#)

• Frontend: Angular 2+, TypeScript

📝 What You Should Submit

1. Repo with:

   1. /docs/ARCHITECTURE.md (Part 1)

   2. /docs/MVP.md (Part 2)

   3. Codebase

   4. SQL migrations + seeds

   5. Updated README with setup/run instructions

2. Short Demo Video (≈10 min total):

   1. 3 minutes – Introduce yourself and share two technical challenges you’ve faced in your career that you’re most proud of solving.

   2. 7 minutes – Walk us through your system architecture and demonstrate your MVP flow (end-to-end).

📊 Evaluation Criteria

1. System Design & Decisions – 50%

   1. Clarity of architecture & modules — 15%

   2. Data/storage reasoning — 10%

   3. Auth & security awareness — 10%

   4. Scalability/reliability thinking — 10%

   5. Extensibility & trade-offs — 5%

2. MVP Definition & Implementation – 50%

   1. MVP judgment (minimal yet valuable) — 15%

   2. Code quality & Architecture fidelity — 15%

   3. API correctness, validation & auth — 10%

   4. Developer experience (README, Swagger, seeds, demo) — 10%

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