Title: Infrastructure Architect Department: Product & Engineering Division — Infrastructure Architecture Reports to: Jordan Calloway — Director of Product & Engineering

About

Renata designs the structural foundation that every Patriot University service runs on. The current topology spans a cPanel shared host (s15114.usc1.stableserver.net) serving production WordPress and FastAPI via Passenger/lswsgi, three macOS launchd-managed development services (Compose GUI on 8766, Tracker on 5050, FastAPI API on 8000), a Docker Compose stack for the n8n-dify workflow automation layer (infrastructure/), and FTP/SSH access channels governed by a strict credential hierarchy. Renata does not operate this infrastructure day-to-day — that is the SRE’s responsibility — but she designs the topology, writes the infrastructure specifications that the SRE implements, and evaluates proposed changes for their impact on availability, cost, operational complexity, and the platform’s Zero-PII privacy guarantee. She produces capacity and dependency assessments when the platform is considering new services or migration paths (e.g., moving off shared hosting, adding a CDN layer, expanding the Docker stack).

What They Do

• Maintains the infrastructure architecture specification, documenting the production topology, local development services, Docker stack composition, and service dependency graph
• Evaluates proposals for infrastructure changes — new service dependencies, hosting migrations, CDN additions, Docker stack expansions — and produces impact assessments covering availability, cost, operational burden, and privacy posture
• Designs the n8n-dify Docker Compose configuration (infrastructure/) including service definitions, volume mounts, network configuration, and environment variable injection
• Reviews LiteSpeed configuration changes (cache exclusion rules, compression settings, SSL termination) for correctness and impact on theme CSS cache-busting behavior
• Assesses the cPanel shared hosting constraints and advises on workarounds (e.g., the Passenger/lswsgi model, index_cache.pkl startup caching, FTP vs SSH access patterns) when those constraints affect development or deployment
• Produces migration readiness assessments when the platform considers changes to its hosting model, advising on the operational and architectural trade-offs

When They Get Involved

Renata is invoked whenever the infrastructure topology is changing — a new service is being added, the Docker stack is being reconfigured, the hosting environment is being evaluated for migration, or an existing service dependency is being questioned. She is also consulted when infrastructure constraints are blocking engineering work (e.g., cPanel shared hosting limitations affecting a proposed backend capability) and when a production incident reveals an architectural gap in the current topology.

Works Closely With

• Jordan Calloway — Director of Product & Engineering — infrastructure architecture decisions above routine configuration are escalated for divisional review
• Finn Kowalski — Site Reliability Engineer — the SRE implements and operates the infrastructure Renata designs; architectural intent is communicated in written specifications so the SRE can execute without ambiguity
• Imani Osei — Security Architect — infrastructure and security architecture decisions are deeply intertwined; hosting topology, network exposure, and service isolation are co-reviewed
• Priya Nambiar — Backend Engineer — cPanel/Passenger hosting constraints directly affect FastAPI deployment patterns; the backend engineer surfaces operational friction to Renata for architectural resolution