Senior Cloud/Backend Engineer
Triple Whale · New York City or Columbus, OH
$160,000–$187,000from the description
Jul 11, 2026
New York City or Columbus, OH
Jul 21, 2026
What this job asks for AI summary
A senior backend/infrastructure engineering role focused on deploying and maintaining service infrastructure in Kubernetes, optimizing databases, building internal developer tooling, and helping other teams design scalable systems. The position includes a recurring weekend on-call rotation for production incident response. It suits an experienced, hands-on engineer comfortable owning complex cloud infrastructure end-to-end, working primarily with GCP, Node.js/TypeScript, and a broad mix of relational and non-relational databases.
Senior level · 6+ years · New York-Newark-Jersey City, NY-NJ-PA · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 750 people in the New York-Newark-Jersey City, NY-NJ-PA area plausibly meet what this posting asks for (software developers). range 320–1,350
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $170,499 (middle half $133,523–$210,499). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (7)
The role sits at the boundary between software development (building internal tooling, scaling systems, coding role explicitly stated) and infrastructure/SRE (Kubernetes operations, on-call, observability). It was classified as Software Developers (15-1252) because the JD explicitly calls it 'a coding role' and emphasizes building systems end-to-end; 15-1244 is the runner-up given the heavy operational and on-call framing.
Location is hard-gated: candidates must be in the New York tri-state area. The role is not remote.
GCP is listed as required under 'Major Cloud platforms (GCP, AWS, Azure)' with a note that GCP is an advantage; AWS and Azure are captured as alternatives since any major cloud platform satisfies the gate.
Monitoring systems (DataDog, Grafana, Groundcover) are listed in the required experience section; DataDog is used as the primary name with the others as alternatives since all three are named as interchangeable examples of the same requirement.
Streaming systems, message queues, relational and non-relational databases are listed as required experience but name no specific technology in the requirements section — they are retained as named capability gates. The specific products (ClickHouse, MongoDB, Redis, Postgres, etc.) appear only in the 'Technologies we use' stack narrative and are therefore marked preferred.
Knative and ClickHouse are listed under 'Bonus Skills' and are marked preferred accordingly. All other items in 'Technologies we use' are also marked preferred as stack context.
GitHub Actions appears only in the 'Technologies we use / Tooling' stack narrative section, so it is marked preferred.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.