SaaS Infrastructure Architect (PostgreSQL/ AWS ECS)

Job ID: 40256342

Budget: $2 – $8 USD

Principal SaaS Infrastructure Architect (PostgreSQL RLS / Multi-Tenant / AWS ECS)

About the Project:
We are rebuilding a production multi-tenant SaaS platform operating in a regulated environment. The system processes sensitive user-generated content and must meet strict tenant isolation, auditability, and compliance standards.

This engagement is for the architecture phase only. A separate engineering team will implement under your direction.

We are seeking a Principal Infrastructure Architect who has designed secure, compliance-ready multi-tenant SaaS systems in production. This is not a coding role. This is a system design and enforcement role.

Critical Requirement (Mandatory):
You must have implemented PostgreSQL Row-Level Security (RLS) in production for a multi-tenant SaaS system. If you have not deployed RLS in a live production environment, please do not apply.

Current Context:
Our existing system enforces tenant isolation primarily at the application layer. This is insufficient for long-term scalability and compliance requirements. We are rebuilding from the ground up with strict enforcement across:
- Application layer
- Infrastructure layer
- Database layer (PostgreSQL RLS)

The goal is to establish a defensible, audit-ready architecture that prevents cross-tenant leakage and supports long-term scale.

Target Stack (Locked):
- Backend: NestJS (Node.js / TypeScript)
- Database: PostgreSQL (single database, RLS enforced)
- Infrastructure: AWS (ECS Fargate, SQS, S3, Redis, RDS)
- Architecture style: Event-driven, multi-tenant SaaS

Scope of Work (Architecture Deliverables):
1. Multi-Tenant Isolation Model - PostgreSQL RLS policies, Tenant context propagation (JWT to DB session), Cross-tenant leakage prevention strategy, Internal multi-tenant staff access model
2. Immutable Audit Logging - Append-only audit schema, Before/after JSON state capture, Actor ID, tenant ID, IP logging, Retention and archive strategy
3. Server-Controlled Workflow State Machine - Strict backend-enforced status transitions, Transition validation model, Prevention of frontend mutation
4. Infrastructure Blueprint - ECS autoscaling strategy, Database connection pooling strategy, Queue and worker design (SQS), Backpressure handling, Failure isolation and retry patterns
5. Role & Permission Matrix - Tenant users, Internal staff, Cross-tenant access rules, Defense-in-depth enforcement

All deliverables must be written, structured, and implementation-ready.

Engagement Structure:
- 4-6 week engagement
- 15-25 hours per week
- Milestone-based payments

To Apply, Please Include:
1. Description of a production system where you implemented PostgreSQL RLS
2. How tenant context was enforced between application and database
3. Example of an immutable audit logging architecture you designed
4. Confirmation you are comfortable working within the defined stack