Senior Cloud & Distributed Systems Architect

Senior Cloud & Distributed Systems Architect at YesAstrology

The Senior Cloud & Distributed Systems Architect at YesAstrology is a full-time, fully remote role within the Core Infrastructure & Platform department, open to candidates worldwide. This is a senior individual contributor technical leadership position with significant architectural authority — not a people-management track — and it exists to safeguard the scalability, reliability, and security of a platform that powers over 170 computational tools and sophisticated AI workflows for millions of monthly users.

The platform's stack is built on Supabase (PostgreSQL / pgvector), Next.js / Node.js, Cloudflare edge networks, and modern cloud serverless environments. Traffic is genuinely global: millions of monthly page views and high-concurrency calculation requests flow across 20+ localized domains, which means every architectural decision must hold up under simultaneous load from many languages, regions, and time zones at once.

For engineers who think in systems, this role has a natural kinship with the discipline of the chart itself: a birth chart is a distributed system of interdependent bodies, each factor read in relation to the others, and the same is true of a well-architected platform. Where an astrologer weighs a Saturn transit against a Jupiter return to judge timing, an architect weighs read replicas against cache invalidation to judge latency. The work rewards the same temperament — patience, precision, and respect for slow-moving structural forces.

If the mission resonates, you can explore the wider product surface through the YesAstrology tools before applying, and read more about how the platform approaches its craft on the YesAstrology blog.

Role Overview and Key Responsibilities

The role centers on designing and optimizing distributed backend systems, multi-region edge caches, PostgreSQL database partitions, and serverless compute clusters, with explicit targets of sub-50ms query latencies, zero-downtime deployments, vector search indexing performance, and robust disaster recovery across global cloud footprints. Day to day, that translates into five core responsibility areas spanning infrastructure, data, caching, observability, and security.

Core Responsibilities

• Architect, scale, and maintain high-availability cloud infrastructure across edge networks, serverless functions, and containerized services.
• Optimize PostgreSQL / Supabase database schemas, connection pooling, indexing strategies, read replicas, and query performance.
• Design low-latency caching tiers (Redis / Cloudflare Workers KV / edge caches) to accelerate computational tools and dynamic page rendering.
• Implement robust observability, distributed tracing, telemetry monitoring, and automated incident alerting (OpenTelemetry, Datadog/Grafana).
• Lead platform security architectures, DDoS mitigation, rate-limiting frameworks, and least-privilege cloud IAM governance.

What We Are Looking For

Candidates should bring 5+ years of experience architecting and operating high-traffic cloud infrastructure, distributed systems, or SaaS backend platforms, along with deep mastery of PostgreSQL — query execution plans, indexing strategies, connection pooling, and multi-tenant isolation. Extensive experience with modern cloud ecosystems (AWS / GCP / Cloudflare / Supabase), edge computing, and infrastructure as code is essential, as is a strong background in low-latency API design, caching architectures, microservice decoupling, and asynchronous queue workers. Demonstrated leadership in site reliability engineering (SRE), high-availability design, and disaster recovery planning rounds out the profile.

Think of the difference between a Whole Sign house system and Placidus: both are valid, but they answer different questions, and choosing the wrong one for the job produces misleading results. Architecture works the same way — a read replica, an edge cache, and a queue worker each solve a distinct latency problem, and the senior architect's value lies in knowing which instrument to reach for and when. A Capricorn stellium in the 10th house and an Aquarius Sun in the 11th describe two very different working styles, and this role genuinely benefits from the second: comfort with unconventional, systems-level thinking about networks and communities of services.

This is a senior individual contributor role with real architectural authority. If you want to build infrastructure that quietly holds up millions of chart calculations a month, this is the seat.

Cloud Infrastructure Architecture and Engineering

The Senior Cloud & Distributed Systems Architect at YesAstrology owns the design, scaling, and hardening of high-availability cloud infrastructure across edge networks, serverless functions, and containerized services. This is a full-time, fully remote individual contributor role in the Core Infrastructure & Platform department, open to candidates worldwide, and it carries real architectural authority over the stack that serves millions of monthly users across 170+ computational tools and 20+ localized domains. The working foundation is Supabase with PostgreSQL and pgvector, Next.js and Node.js, Cloudflare edge networks, and modern serverless environments, with explicit targets of sub-50ms query latencies, zero-downtime deployments, and dependable disaster recovery across every cloud footprint.

Infrastructure engineering here is layered rather than monolithic. The architect tunes PostgreSQL and Supabase schemas, connection pooling, indexing strategies, read replicas, and query performance; designs low-latency caching tiers on Redis, Cloudflare Workers KV, and edge caches to accelerate computational tools and dynamic page rendering; and leads platform security architecture spanning DDoS mitigation, rate-limiting frameworks, and least-privilege cloud IAM governance. Observability is treated as a first-class deliverable, built on distributed tracing and telemetry through OpenTelemetry with Datadog or Grafana, so the team sees degradation before users do.

Astrologically, this is Capricorn-and-Saturn work: structural, load-bearing, and slow to change by design. Where a Capricorn stellium in the 10th house describes a career built on earned authority and durable frameworks, a Saturn transit rewards the architect who hardens a schema before traffic spikes rather than after. Contrast that with an Aquarius Sun in the 11th house, which supplies the appetite for unconventional, systems-level thinking about networks and communities of services — the two temperaments together describe the role precisely. The same discipline appears in chart calculation itself: a birth time determines house cusp degrees, and whether the engine applies Placidus, Whole Sign, or Equal House changes what a placement means, just as choosing a read replica, an edge cache, or a queue worker changes which latency problem gets solved.

Under the hood, the platform's calculation layer is grounded in high-precision Swiss Ephemeris astronomical data combined with comprehensive astrological synthesis for accurate planetary coordinates — and infrastructure decisions directly shape how fast that output reaches a visitor. When exact birth time is missing, a solar-noon chart default preserves planetary sign and aspect accuracy even without precise cusps, and the architecture must serve both full and partial-data requests without degrading the experience. If the mission resonates, explore the wider product surface through the YesAstrology reports before applying.

Distributed Systems Design and Scalability

Distributed systems design at YesAstrology means architecting and optimizing distributed backend systems, multi-region edge caches, PostgreSQL database partitions, and serverless compute clusters so that millions of monthly page views and high-concurrency calculation requests hold up across 20+ localized domains simultaneously. The role demands 5+ years architecting and operating high-traffic cloud infrastructure, distributed systems, or SaaS backend platforms, deep mastery of PostgreSQL including query execution plans, indexing, connection pooling, and multi-tenant isolation, and a strong background in low-latency API design, caching architectures, microservice decoupling, and asynchronous queue workers. Demonstrated leadership in site reliability engineering, high-availability design, and disaster recovery planning completes the profile.

Scalability is a matter of instrument selection, not brute force. A read replica, an edge cache, and a queue worker each answer a different latency question, and the senior architect's value lies in knowing which to reach for and when — much as an astrologer distinguishes the 10th house of career from the 6th house of daily work and the 2nd house of income, reading each in its own register rather than collapsing them together. Aspect dynamics offer a useful parallel: a trine between Jupiter and the Midheaven describes smooth, expanding visibility, while a square between Saturn and Mars describes friction that must be engineered around. Multi-tenant isolation across localized domains is the technical equivalent of keeping each chart's factors distinct while still reading the whole configuration.

Timing cycles make the scalability mandate concrete. Traffic to horoscope and transit pages swells around Mercury retrograde announcements, eclipse seasons, and New Moon windows, and the architecture must absorb those surges without breaching latency targets. The same principle governs the product: planetary transits, solar arcs, and progressions activate a chart's potential over time, and the compute layer must recalculate those cycles on schedule for every user. Vector search indexing performance through pgvector, partition strategy, and cache invalidation policy all determine whether a returning visitor sees a freshly computed transit report or a stale one.

For instance, if a localized domain serves a Whole Sign chart by default while another applies Placidus, the calculation service must resolve house cusps per request without duplicating the entire ephemeris workload — a decoupling problem before it is an astrology problem. This is senior individual contributor work with genuine architectural authority, and it rewards the temperament that respects slow-moving structural forces. If you want to build infrastructure that quietly holds up millions of chart calculations a month, this is the seat.

High Availability, Reliability, and Fault Tolerance

High availability, reliability, and fault tolerance at YesAstrology mean that the platform keeps serving chart calculations and dynamically rendered pages even when individual components fail. The Senior Cloud & Distributed Systems Architect owns this guarantee across edge networks, serverless functions, and containerized services, holding explicit targets of sub-50ms query latencies, zero-downtime deployments, and dependable disaster recovery across every cloud footprint. In practice, availability is engineered as redundancy plus graceful degradation: no single database, cache tier, or compute region is allowed to become a single point of failure for millions of monthly users across 20+ localized domains.

Astrologically, this is Saturn's domain rather than Jupiter's. Saturn in the 10th house brings responsibility and earned mastery — the architect who hardens a schema and rehearses failover before a traffic spike, not after. Jupiter in the 10th, by contrast, expands public visibility and can tempt a team toward growth without structural reinforcement; the reliable platform needs both impulses, but the fault-tolerance mandate belongs to Saturn. A Saturn–Mars square describes exactly the friction this role engineers around: contention, retry storms, and cascading timeouts that must be bounded by circuit breakers, backoff policies, and asynchronous queue workers that absorb load instead of collapsing under it.

How Redundancy Is Designed and Verified

Reliability is built in layers that mirror the chart's own hierarchy of factors. PostgreSQL and Supabase read replicas absorb read-heavy calculation traffic while the primary handles writes; connection pooling prevents tenant isolation from degrading under concurrency; multi-region edge caches on Cloudflare Workers KV and Redis keep repeated requests from ever reaching the database. Observability through OpenTelemetry with Datadog or Grafana turns distributed tracing into early warning, so degradation is visible before users report it. Each layer answers a distinct failure question, just as the 6th house of daily operations differs from the 10th house of public standing — reading one as the other produces misleading conclusions in both astrology and architecture.

Disaster recovery planning is where the role's rigor shows most clearly. Because the calculation layer is grounded in high-precision Swiss Ephemeris astronomical data, a regional outage must never mean lost ephemeris capacity; failover targets, backup restoration drills, and documented recovery objectives are treated as deliverables, not documentation. When exact birth time is missing, the solar-noon chart default preserves planetary sign and aspect accuracy even without precise cusps — and the availability design must serve both full and partial-data requests without letting one degrade the other. For instance, a surge in transit-page traffic during eclipse season should be absorbed by edge caching and queue workers while full chart calculations continue at their latency target.

This is senior individual contributor work with genuine architectural authority inside the Core Infrastructure & Platform department, full time and fully remote worldwide. If you want to build infrastructure that quietly holds up millions of chart calculations a month, you can explore the wider product surface through YesAstrology products before applying.

Cloud Security, Data Protection, and Compliance

The Senior Cloud & Distributed Systems Architect at YesAstrology leads platform security architecture end to end: DDoS mitigation, rate-limiting frameworks, and least-privilege cloud IAM governance across every cloud footprint the platform operates. This is a full-time, fully remote individual contributor role in the Core Infrastructure & Platform department, open to candidates worldwide, and it carries real architectural authority over a stack serving millions of monthly users across 170+ computational tools and 20+ localized domains. Security here is not a perimeter bolted onto the platform — it is a layer that must hold while Supabase with PostgreSQL and pgvector, Next.js and Node.js, Cloudflare edge networks, and modern serverless environments all scale together.

Data protection begins with the birth data itself. A chart calculation depends on date, time, and place of birth, and the platform's calculation layer is grounded in high-precision Swiss Ephemeris astronomical data combined with comprehensive astrological synthesis for accurate planetary coordinates. That means the architect must reason about where sensitive inputs live at every hop: request validation at the edge, encrypted transport into serverless functions, multi-tenant isolation inside PostgreSQL, and retention policy on cached results in Redis, Cloudflare Workers KV, and edge caches. Least-privilege IAM governance is the practical instrument — service roles scoped to the minimum tables and partitions they touch, no shared credentials across localized domains, and audit trails on every privileged operation.

Astrologically, this is Saturn work in its purest form: boundaries, structure, and consequences for what crosses them. Where a Saturn–Mars square describes friction that must be engineered around rather than wished away, a security posture assumes hostile traffic and designs for it — rate limiting tuned to absorb surges around Mercury retrograde announcements, eclipse seasons, and New Moon windows without locking out legitimate visitors. Contrast a Capricorn stellium in the 10th house, which builds durable, load-bearing frameworks, with an Aquarius Sun in the 11th house, which thinks in networks and communities of services; the security architect needs both, because a control that protects one service but breaks the mesh is not a control at all.

Compliance and resilience are inseparable from availability. Zero-downtime deployments and dependable disaster recovery are explicit targets, and both depend on tested restore paths, partitioned backups, and observability through OpenTelemetry with Datadog or Grafana so anomalies surface before users report them. The same discipline governs partial data: when exact birth time is missing, a solar-noon chart default preserves planetary sign and aspect accuracy even without precise cusps, and the architecture must serve those requests without weakening isolation between tenants. For instance, if one localized domain applies Placidus while another defaults to Whole Sign, house cusp resolution happens per request — and the security model must ensure that resolution never exposes another user's stored chart. If this combination of rigor and reach appeals to you, explore the wider product surface through the YesAstrology products before applying.

Infrastructure Automation, Monitoring, and Performance Optimization

Infrastructure automation, monitoring, and performance optimization at YesAstrology means treating observability and repeatability as first-class deliverables rather than afterthoughts: the architect builds automated provisioning and deployment pipelines, instruments the platform with distributed tracing and telemetry through OpenTelemetry with Datadog or Grafana, and holds explicit targets of sub-50ms query latencies and zero-downtime deployments across every cloud footprint. This is a full-time, fully remote individual contributor role in the Core Infrastructure & Platform department, open to candidates worldwide, and the automation mandate spans Supabase with PostgreSQL and pgvector, Next.js and Node.js, Cloudflare edge networks, and modern serverless environments serving millions of monthly users across 20+ localized domains.

Automation is layered by design. Infrastructure as code governs edge networks, serverless functions, and containerized services; PostgreSQL and Supabase schemas, connection pooling, indexing strategies, read replicas, and query performance are tuned as versioned, reviewable changes rather than manual interventions; and low-latency caching tiers on Redis, Cloudflare Workers KV, and edge caches are provisioned and invalidated programmatically. Automated incident alerting closes the loop, so a regression in query execution plans or a cache stampede surfaces in telemetry before a visitor notices a slow chart calculation.

Astrologically, this is Saturn-and-Mercury work: Saturn supplies the structure, the scheduled job, the audit trail, and the discipline of hardening a schema before traffic spikes rather than after; Mercury supplies the measurement, the instrumentation, and the precise language of traces and dashboards. Contrast a Capricorn stellium in the 10th house, which builds durable, load-bearing frameworks, with an Aquarius Sun in the 11th house, which thinks in networks and communities of services — automation is where those two temperaments meet. A Saturn–Mars square describes the friction this role engineers around: retry storms, contention, and cascading timeouts bounded by circuit breakers, backoff policies, and asynchronous queue workers that absorb load instead of collapsing under it.

Performance optimization follows the same instrument-selection logic as chart interpretation. A read replica, an edge cache, and a queue worker each answer a different latency question, just as the 10th house of career, the 6th house of daily work, and the 2nd house of income each describe a distinct domain and must not be collapsed together. Timing cycles make the mandate concrete: traffic to horoscope and transit pages swells around Mercury retrograde announcements, eclipse seasons, and New Moon windows, and the automation layer must scale capacity ahead of those surges. Because the calculation layer is grounded in high-precision Swiss Ephemeris astronomical data, performance budgets are measured against real ephemeris workloads — and when exact birth time is missing, the solar-noon chart default preserves planetary sign and aspect accuracy even without precise cusps, so partial-data requests must stay fast without degrading full-chart latency. If the mission resonates, you can explore the wider product surface through the YesAstrology blog before applying.

Required Technical Skills and Qualifications

The role requires 5+ years of experience architecting and operating high-traffic cloud infrastructure, distributed systems, or SaaS backend platforms, deep mastery of PostgreSQL including query execution plans, indexing strategies, connection pooling, and multi-tenant isolation, and extensive experience with modern cloud ecosystems such as AWS, GCP, Cloudflare, or Supabase alongside edge computing and infrastructure as code. Candidates also need a strong background in low-latency API design, caching architectures, microservice decoupling, and asynchronous queue workers, plus demonstrated leadership in site reliability engineering, high-availability design, and disaster recovery planning. This is a senior individual contributor position with significant architectural authority, not a people-management track.

Read the requirements as a set of instruments rather than a checklist. Deep PostgreSQL mastery is the read-replica-and-index work of a Saturn in the 10th house: responsibility, earned mastery, and consequences that arrive on schedule. Low-latency API design and caching architectures belong to Mercury, where precision in measurement and naming determines whether a cache invalidation policy is correct. Microservice decoupling and asynchronous queue workers describe the Aquarius Sun in the 11th house temperament — comfort with unconventional, systems-level thinking about networks and communities of services — while disaster recovery planning is pure Saturn, the rehearsal of failure before it happens.

For instance, a candidate who can explain why one localized domain defaults to Whole Sign while another applies Placidus, and how the calculation service resolves house cusp degrees per request without duplicating the entire ephemeris workload, is demonstrating exactly the decoupling judgment this role needs. Likewise, someone who can articulate when a read replica beats an edge cache beats a queue worker is reasoning the way an astrologer distinguishes a Jupiter–Midheaven trine (smooth, expanding visibility) from a Saturn–Mars square (friction that must be engineered around). The platform's calculation layer is grounded in high-precision Swiss Ephemeris astronomical data combined with comprehensive astrological synthesis for accurate planetary coordinates, and the architect must protect both accuracy and latency under that load.

Practical familiarity with the working stack rounds out the profile: Supabase with PostgreSQL and pgvector, Next.js and Node.js, Cloudflare edge networks, Redis and Cloudflare Workers KV caching tiers, and observability through OpenTelemetry with Datadog or Grafana. Because the platform serves 170+ computational tools across 20+ localized domains, vector search indexing performance and multi-tenant isolation are not optional refinements — they are baseline expectations. If this combination of rigor and reach appeals to you, the full responsibilities and application steps are set out in the role overview.

How to Apply for the Senior Cloud & Distributed Systems Architect Position

To apply for the Senior Cloud & Distributed Systems Architect position at YesAstrology, submit your application for the full-time, fully remote role in the Core Infrastructure & Platform department, which is open to candidates worldwide. Because the position carries real architectural authority over a platform serving millions of monthly users across 170+ computational tools and 20+ localized domains, the strongest applications make the five connected layers of the role legible at a glance: cloud infrastructure architecture, distributed systems design and scalability, high availability and fault tolerance, cloud security and compliance, and automation, monitoring and performance optimization. Treat the application the way you would treat a schema migration — versioned, deliberate, and reviewed before it ships.

Your written materials should demonstrate instrument selection rather than tool-name accumulation. Show where you chose a read replica over an edge cache, or a queue worker over a synchronous call, and explain the latency question each answered. Candidates who can articulate why one localized domain might default to Whole Sign while another applies Placidus — and how a calculation service resolves house cusp degrees per request without duplicating the entire ephemeris workload — are demonstrating exactly the decoupling judgment this role requires. Equally valuable is evidence of Saturn-style rigor: a hardened schema deployed before a traffic spike, a rehearsed failover, a documented recovery objective treated as a deliverable rather than documentation.

Concrete examples carry more weight than adjectives. Describe a PostgreSQL optimization you owned — a query execution plan rewritten, an indexing strategy revised, connection pooling tuned under multi-tenant isolation — and quantify the latency it recovered against a sub-50ms target. Describe an observability practice you built with OpenTelemetry and Datadog or Grafana, and name the degradation the team caught before users reported it. If you have absorbed a surge around Mercury retrograde announcements, eclipse seasons, or New Moon windows without breaching latency targets, that is precisely the timing-cycle pressure this platform runs under, and it belongs in your application.

Before submitting, spend time inside the product you would be protecting. Exploring the wider surface through the YesAstrology platform gives you a working sense of how 170+ computational tools, dynamically rendered pages, and high-concurrency calculation requests meet in a single visitor session — and how much depends on the infrastructure layer beneath them. The calculation layer itself is grounded in high-precision Swiss Ephemeris astronomical data combined with comprehensive astrological synthesis for accurate planetary coordinates, and when exact birth time is missing, a solar-noon chart default preserves planetary sign and aspect accuracy even without precise cusps. An architect who understands that both full and partial-data requests must stay fast, isolated, and accurate is already reasoning like a member of the team.