Full-Stack Cloud Architect

Position: Lead Full-Stack Cloud Architect
Level: Senior / Lead
Location: 100% Remote, Miami-based
Compensation: Competitive Hourly Rate, 12+ month contract
Reports to: Product Owner 
Job Number: 7381
 

Overview

We’re building a subscription, multi-tenant HR platform, engineered to financial-industry-grade cloud standards, with proprietary client HR data held in strict per-client silos. This is the architect seat: you decide the stack — AWS or Azure, and whatever persistence/load-balancing approach each client actually needs — not just build to spec. You’re expected to bring “here’s how I’d build it,” not ask for one.

What You’ll Build

• The web client (your framework choice — justify it)
• The overall cloud architecture: cloud provider decision (AWS or Azure), persistence tier strategy (MongoDB vs. relational, decided per client where it matters), load-balancing topology, authentication approach, containerization strategy
• Technical decision-making for a “mission control” style backend that isolates proprietary client HR data in silos, not a shared multi-tenant table

Must Have

• 7+ years full-stack, with real ownership of architecture decisions (not just implementation) on multiple large-scale systems
• Deep AWS or Azure experience — genuine infrastructure ownership, not just deployment; if AWS, hands-on Lambda architecture experience
• Experience from large-scale financial or regulated institutions (JPMorgan-caliber environments or equivalent) — the product is HR software, but the uptime and data-isolation discipline this role needs comes from that kind of environment
• Demonstrated experience running different persistence/scaling configurations per customer or tenant in a single platform
• Strong, defensible opinions on stack choices, backed by tradeoff reasoning

Explicitly Not Looking For

• NOT looking for an AI-centric dev who lacks real hands-on programming chops
• NOT looking for Node.js as primary backend stack
• PROBABLY NOT C#/.NET-centric backgrounds (strong preference against)
• Order-takers — if you ask what stack to use instead of proposing one, it’s a no

Nice to Have

• Strong contract/consulting work where you’ve owned architecture for an external client 
• Experience building HR-adjacent or people-data platforms