Of the ten postings, PubNative's SRE listing is the most technically revealing. Most others are generic "we need Rails devs" or mission-driven pitches (PIF, CMS, Ad Hoc). PubNative actually names its infrastructure primitives — and those names tell a story.

The stack: Kubernetes across both AWS and Packet, observed via Prometheus, with CI/CD pipelines the SRE is expected to build. This is a very specific combination.

• Packet (now Equinix Metal) is bare-metal-as-a-service. Companies pick it when AWS margins on compute become intolerable at scale — typically ad-tech, crypto, or anyone burning through EC2 for latency-sensitive workloads.
• Running Kubernetes across two clouds simultaneously is not a résumé flex; it's a cost-arbitrage or latency play. Ad exchanges need sub-100ms bid response globally, and Packet gives them cheaper predictable-throughput boxes for the hot path while AWS handles bursty or managed-service workloads.
• Prometheus (not Datadog, not New Relic) means they're cost-conscious about observability too — self-hosted metrics at their request volume is a deliberate choice against six-figure SaaS bills.

What it reveals about the company: "High volume of requests around the world, 24/7/365" is ad-tech code for millions of RPS with hard latency SLOs. Mobile ad monetization is a brutal margin business — every millisecond and every dollar of infra cost compounds across billions of bid requests. Hiring an SRE (singular) to own K8s lifecycle across two providers suggests a lean infra team stretched thin, likely 1-3 people total. The role bundles cluster ops + observability + CI/CD, which at a bigger company would be three separate teams.

Skills/trends highlighted: The 2020-era ad-tech consensus is now visible — Kubernetes has won as the abstraction layer, and multi-cloud is less about vendor lock-in fear and more about workload-specific cost optimization. Packet/Equinix Metal is the tell that "cloud native" doesn't mean "hyperscaler only" anymore.

Green flags: Specific tooling named (not "modern stack" hand-waving), clear scope, ownership implied. Red flags: Berlin onsite only with no remote option (unusual for SRE work, and dated even for the era). "Work alongside other teams on infrastructure-related tasks" is a catch-all that suggests scope creep — the SRE will also be the ops helpdesk. No salary band, no team size, no on-call expectations disclosed for a role that will absolutely carry a pager.