Senior/Staff Backend Engineer — Data & Platform

About NearSync

NearSync is an AI-native business operating system for SMBs across the GCC — CRM, HR, finance, operations, communications and commerce in a single multi-tenant platform, with an AI assistant at the core. We're growing fast and building for scale, security, and enterprise-grade compliance from the ground up.

The role

You'll own our backend, data architecture, and platform layer. This is the most senior engineering seat on the data side: you set the standards for how we model data, enforce multi-tenant isolation, run our services, and ship to production. You'll work close to the metal on PostgreSQL and our serverless compute layer, and you'll define the security and reliability bar as we scale toward regulated and enterprise customers.

High ownership, real scope, direct line to the founder. If you want to design and defend the hardest part of a fast-moving SaaS platform, this is it.

What you’ll do

• Design and own our multi-tenant PostgreSQL architecture — schema, row-level security, data isolation, and performance at scale.
• Build and harden the serverless/edge service layer (TypeScript) and our public API surface.
• Stand up CI/CD, migrations, environments, and observability to a standard the whole team ships against.
• Drive security and compliance engineering — least-privilege access, tenant isolation guarantees, and readiness for formal review (data-protection, SOC 2 / ISO-style audits).
• Own our AWS data-plane and its residency and reliability posture as we scale in-region.

What we’re looking for

• Deep PostgreSQL in production — Row-Level Security, policy design, privilege and search_path hardening, query performance, migrations at scale. Not "I use an ORM."
• Proven experience designing and defending multi-tenant SaaS isolation — you know the failure modes and how to prove isolation actually holds.
• Strong with a Postgres + serverless-function stack (Supabase / PostgREST / Deno, or clearly equivalent).
• A security-first instinct — you reason about the system from the perspective of a low-privilege attacker, not just the happy path.
• You’ve built the CI/CD pipeline, not just used one. Comfortable with AWS (RDS a plus).

Strong plus

• GCC data-protection context (UAE / KSA PDPL) or having taken a product through a real security/compliance audit.
• pgvector / RAG, PostGIS, or accounting / e-invoicing (PEPPOL) domain experience.
• Comfortable setting guardrails around AI-assisted development.

How we hire

No take-home busywork. One live technical conversation centered on a real problem: design a multi-tenant isolation model, and find the leak in one that’s subtly wrong. That tells us what we need to know.

• Not a fit: frontend-first engineers, or anyone who hasn’t owned tenant isolation and a production deploy pipeline.