Senior Backend Engineer

Role overview Own backend architecture and delivery for client engagements where reliability, data integrity or regulatory constraints are central. You’ll shape schemas, service boundaries, integrations and operations, while working directly with client architects. Engagements last long enough for design decisions to meet real production conditions, so sound judgment about generated code and complexity is part of the job.

Responsibilities - Define and document data models, service boundaries and the reasoning behind architecture decisions. - Implement critical backend components and establish patterns for the wider system. - Plan legacy migrations that let old and new systems operate together until a safe transition is possible. - Build operational foundations, including observability, backups and runbooks for incident response. - Review designs and code, identifying unnecessary complexity and explaining trade-offs. - Evaluate AI-generated code carefully, deciding what to validate, adapt or remove.

Requirements - At least five years of backend development experience with TypeScript, Go, Python or a comparable language. - Strong Node.js and TypeScript knowledge, including the ability to make and explain framework choices. - Production experience with PostgreSQL under load, including transactions, query performance, locking, pooling, partitioning and migrations. - Durable API design skills, including versioning, pagination and idempotency. - Understanding of event-driven patterns, authentication, authorization, secrets, personal data handling and audit trails. - Production ownership experience, with structured logs, traces, metrics and calm incident response.

Nice to have - Experience in regulated industries such as finance or healthcare, or with strict tenant data isolation. - Familiarity with event sourcing or CQRS, along with judgment about when those patterns are appropriate.

Benefits and work setup - Remote work across the MENA region, with hours arranged around team overlap. - Small teams with early client contact and responsibility from initial discussions through handover. - Budget for equipment and tools, plus a learning budget with time to use it. Paid time off is encouraged, and timesheets are not used.