Staff-Level Cloud Platform Engineering in NYC

Skills used and tools used: #Cloud-Architecture, #Cloud-Platform-Engineering, #Cloud-Engineering, #Site-Reliability, #NYC, #Kubernetes, #Observability, #DevOps

Written by Tyler La Fronz on August 19, 2026

Cloud architecture as a New York City-based practice

I lead site reliability engineering out of New York City, working at a staff-level scope across cloud architecture and platform engineering. That means the job isn’t just writing infrastructure code — it’s setting the technical direction other engineering teams build on: how services are architected for resilience, how reliability gets measured, and how incidents get caught and resolved before they become outages.

What staff-level cloud platform engineering looks like day to day

Roadmap and technical direction — partnering with program and product leadership to define where cloud infrastructure investment goes next, and proposing the initiatives that get us there.
Cross-team reliability standards — driving SLO/SLA definition, incident response automation, and postmortem processes across distributed systems, reducing mean time to resolution (MTTR) and giving every team clearer visibility into system health.
Production-readiness tooling — building internal tools that aggregate stability and readiness signals from 10+ data sources, so feature teams know whether a launch is actually safe before it ships.
Observability as infrastructure — implementing monitoring, alerting, and logging pipelines (NewRelic, CloudWatch) that turn raw telemetry into something engineers can act on, not just dashboards to stare at.
AI-assisted delivery — applying spec-driven development practices with AI tooling to move reliability and platform engineering work faster without sacrificing rigor.

The cloud engineering toolset

The architecture underneath all of this runs on Google Cloud Platform and Kubernetes (both certifications I hold — GCP and Kubernetes and Cloud Native Associate), with microservices and API-first design as the default shape for new systems. The constant across every stack: build for the failure mode you haven’t seen yet, not just the one from the last incident.

Why this matters for NYC teams

New York’s engineering market has no shortage of “cloud engineer” job titles, but staff-level cloud architecture is a different scope — it’s about making the infrastructure decisions that other teams inherit for years. If you’re building or scaling cloud platform engineering capability in NYC, that’s the level I operate at, and the contact details on this site are the fastest way to reach me.