AWS Multitenant Systems Architect

BCI-IT is building out a multi-tenant environment and needs a hands-on (IC) Individual Contributor / Architect to lead the effort end to end for our client— infrastructure, Dev Ops, and software development. This is not a pure software engineering lead role: the person needs to own the full stack of decisions that make multi-tenancy work, from AWS infrastructure design and CI/CD pipelines down to the application code that enforces tenant isolation.

You’ll be the single technical owner who can design the architecture, stand up the infrastructure, and write the code — not hand off pieces to separate infra and dev teams. We can work on a W2/1099 basis only. No C2C or subcontractors. Open for US Citizen, Perm Resident, Green Card, OPT EAD/STEM. No H1 or sponsorship available. Role is hybrid with the need to be in the office 1-2 days a week.

Candidates local to the NY/NJ area preferred.

• Architect the multi-tenant environment at Verisk from the ground up: tenant isolation model, data partitioning strategy, provisioning, and scaling
• Design and build the AWS infrastructure to support it (VPC design, ECS/EKS, Lambda, RDS/Aurora, S3, API Gateway, IAM boundaries between tenants)
• Own infrastructure-as-code (Cloud Formation, CDK, or Terraform) for repeatable, auditable environment provisioning
• Build and maintain CI/CD pipelines and Dev Ops practices (deployment automation, environment promotion, rollback strategy, observability)
• Develop core platform and tenant-management services in C# and Python
• Design tenant context propagation across services, APIs, databases, and background/batch jobs
• Define and enforce security and data-isolation standards across tenants (encryption, IAM scoping, network segmentation, audit logging)
• Set up monitoring and alerting that surfaces per-tenant health, not just aggregate system health (critical for catching “noisy neighbor” issues early)
• Make build-vs-buy and architecture tradeoff calls, and clearly communicate the reasoning to technical and non-technical stakeholders
• Mentor engineers on multi-tenant patterns as the team scales around this effort

• 8+ years of software development experience, with significant time spent as a hands-on architect, not purely in a management or pure-dev role
• 5+ years of hands-on experience designing and building multi-tenant SaaS environments from the ground up — this is a core, non-negotiable requirement
• Demonstrated expertise across multiple tenant isolation models (shared database/shared schema, shared database/separate schema, database-per-tenant) and the judgment to choose and implement the right one
• Strong, production-grade AWS infrastructure experience — not just “used AWS,” but designed and built it: VPCs, ECS/EKS or Lambda, RDS/Aurora, S3, API Gateway, IAM, Cloud Watch/X‑Ray
• Dev Ops ownership experience: CI/CD pipeline design and implementation, infrastructure-as-code (Cloud Formation, CDK, or Terraform), deployment automation
• Strong software development skills in both C# (.NET Core) and Python — able to write production code in both, not just read it
• Proven experience solving multi‑tenant-specific challenges: tenant onboarding/provisioning automation, noisy‑neighbor performance isolation, per‑tenant scaling, cross‑tenant data leakage prevention
• Solid understanding of relational databases (SQL Server, PostgreSQL, or Aurora) and data partitioning/isolation strategies at scale
• Strong understanding of security best practices in multi‑tenant environments (authentication, authorization, encryption, compliance considerations relevant to insurance/data‑analytics industries)
• Excellent communication skills — this role will need to represent architectural decisions directly to stakeholders

• Experience in insurance, risk analytics, or data‑heavy enterprise environments
• AWS certifications (Solutions Architect Professional, Dev Ops Engineer Professional)
• Experience with containerization and orchestration (Docker, Kubernetes)
• Experience with event‑driven architectures (SQS, SNS, Event Bridge, Kafka)
• Experience building platforms that support both pooled (self‑serve) and dedicated/siloed (enterprise) tenant tiers in parallel
• Background holding both architecture and hands‑on build responsibility simultaneously (not purely advisory/architect‑on‑paper roles)