أسئلة المقابلات التقنية وتصميم الأنظمة في الخليج

إجابة نموذجية

Service boundaries defined by business domain (DDD); API contracts with OpenAPI/Protobuf; independent deployment; database per service (no shared schemas); async event-driven communication (Kafka/RabbitMQ) for workflows and sync (gRPC/REST) for queries; centralized telemetry (OpenTelemetry); circuit breakers (Resilience4j) and transactional outbox for consistency.

إجابة نموذجية

Resource-based nouns (/api/v1/orders); correct HTTP verbs (GET, POST, PUT, PATCH, DELETE); standard status codes (200, 201, 400, 401, 404, 429); cursor-based pagination; OAuth2 JWT auth; rate limiting; idempotency headers for POST transactions; structured error envelopes; comprehensive OpenAPI specs.

إجابة نموذجية

SQL (Postgres) for structured data requiring ACID transactions, complex joins, and financial ledger integrity. NoSQL (Mongo, DynamoDB) for unstructured documents, high write velocity, or key-value caching. In modern architecture, polyglot persistence (SQL primary + Redis cache + Elasticsearch search) is standard.

إجابة نموذجية

Passwords hashed with Argon2id or bcrypt (cost 12); stateless JWT access tokens (short TTL ~15m) paired with httpOnly secure refresh token rotation in Redis; OAuth2/OIDC for SSO; granular Role-Based Access Control (RBAC); MFA enforcement on sensitive routes; never rolling custom cryptography.

إجابة نموذجية

1. Mitigate immediate impact (rollback deploy, flip feature flag, add capacity); 2. Check telemetry dashboards, error spikes, and distributed traces; 3. Formulate data-backed hypothesis before touching code; 4. Replicate in staging; 5. Deploy fix through CI/CD; 6. Publish blameless postmortem with preventive backlog items.

إجابة نموذجية

Identify read-heavy, low-mutation data; implement multi-tier caching (browser HTTP cache, CDN edge, Redis in-memory); choose invalidation strategies (TTL expiration vs event-driven purge); guard against cache stampedes using distributed locks or probabilistic early expiration.

إجابة نموذجية

Automated pre-commit hooks (ESLint, Prettier, TypeScript strict); mandatory CI test coverage thresholds; required 2-engineer peer reviews with clear guidelines; Architecture Decision Records (ADRs); blameless retrospectives.

إجابة نموذجية

Git push triggers GitHub Actions / GitLab CI; runs unit & integration tests in parallel; static analysis (SonarQube) and dependency CVE audit (Snyk); builds immutable Docker image pushed to private registry; deploys automatically to Staging; releases to Production via automated canary / blue-green with automated rollback on error spikes.

إجابة نموذجية

Strict input validation with Zod schemas; parameterized ORM queries preventing SQL injection; Context-aware escaping against XSS; secrets managed in HashiCorp Vault or AWS Secrets Manager (never in git); TLS 1.3 encryption in transit and AES-256 at rest; strict CSP and security headers in proxy middleware.

إجابة نموذجية

Functional requirements (shorten, redirect); Traffic estimation (100M URLs/mo, 100:1 read ratio); Base62 encoding (6-7 chars = trillions of combinations); Distributed ID generator (Snowflake); Database (Postgres for persistence + Redis for hot redirects); 301 vs 302 redirect strategy; rate limiting per IP.

إجابة نموذجية

Validate use-case necessity; structure prompts with versioned schemas; enforce JSON schema output validation; implement semantic caching (Redis) to reduce latency and token costs; guard against prompt injections; ensure sensitive PII is redacted before sending to third-party LLMs; maintain deterministic fallbacks.

إجابة نموذجية

Start with a well-structured modular monolith. It provides fast iteration, simple transactions, and low operational overhead. Split into microservices only when organizational scaling (independent team domains) or distinct scalability bottlenecks demand it.

إجابة نموذجية

Verify functional correctness and edge cases first; assess readability and adherence to team conventions; ask questions to understand intent rather than giving commands; clearly label blocking issues vs non-blocking 'nits'; praise clever, elegant solutions.

إجابة نموذجية

Decompose requirements into subtasks under 1–2 days each; apply three-point estimation (optimistic, nominal, pessimistic); add contingency buffer for external dependencies; communicate estimates as confidence intervals rather than fixed promises; calibrate retrospectively.