Platform Engineer (PHP)

Turno has a growing set of foundational engineering work that no one explicitly owns today: runtime upgrades, dependency management, observability for async workloads, test confidence, integration patterns, and application architecture. This work affects every team, but it competes invisibly with feature delivery and rarely gets sustained attention. We need someone to own it.

This role sits on the Platform Services team, which builds shared infrastructure for Turno’s engineering org: queues, workers, cache, auth, event-driven pipelines, and internal tooling, all on TypeScript (Hono, Bun) and GCP (GKE, Pub/Sub, Cloud Run). You’ll split your time between improving the PHP monolith’s foundations and building new platform services in TypeScript.

You need to be comfortable in both worlds. Some weeks you’ll be refactoring Laravel service providers and adding Sentry breadcrumbs to queue jobs. Other weeks you’ll be designing Pub/Sub pipelines and writing Hono services. The common thread is that your work removes friction for other engineers and makes the whole system more reliable.

• Own the PHP runtime and dependency lifecycle: track EOL dates, run upgrades (we need to get to PHP 8.4+), set up Dependabot, and keep things from drifting into emergency-upgrade territory.

• Make changes less scary. That means improving test coverage systematically, wiring up automation, and figuring out where AI-assisted tooling can help.

• Build observability for the things that break quietly: cronjobs, queue workers, background processing. Sentry breadcrumbs, structured logging, dashboards.

• Standardize how we talk to external services. Right now Google API integrations, for example, are scattered Guzzle calls with no shared auth model. Fix that.

• Push the monolith toward better architecture: clearer domain boundaries, event-driven flows, formalized contracts between modules.

• Speed up the app where it matters. Refactor kernel loading, reduce unnecessary DB hits on hot paths, add caching where it makes sense.

• Work with QA to make on-demand environments actually reliable and usable.

• Build shared TypeScript services and SDKs (Hono, Bun) that other teams consume for queues, workers, cache, and auth.

• Design and run event-driven pipelines on GCP Pub/Sub, Cloud Run, and Kubernetes (GKE).

• Create and maintain software templates and scaffolding in Backstage so teams can spin up new services without reinventing patterns.

• Wire in reliability patterns: idempotency, retry/backoff, DLQ handling, rate limiting.

• Define internal APIs and service contracts that work cleanly across the PHP and TypeScript stacks.

• Contribute to CI/CD, GitOps (ArgoCD), and deployment automation.

• Join architecture reviews. Have opinions about how things should be built.

• Reduce drift between services: align frameworks, library versions, and patterns so maintenance doesn’t scale linearly with the number of repos.

• Review code, write design docs, and help when things break.

• Mentor other engineers, especially on platform patterns and reliability practices.

• 6+ years of backend engineering, with real depth in both PHP and TypeScript/Node.js.

• You know Laravel well enough to work on its internals: service providers, queues, console kernel, testing infrastructure.

• Hands-on with GCP (GKE, Pub/Sub, Cloud Run, Cloud SQL) or the AWS/Azure equivalents.

• You’ve built or operated event-driven systems with message queues and understand the failure modes.

• Comfortable with Kubernetes and containerized workloads. You’ve dealt with CI/CD pipelines in production.

• You’ve done cross-cutting technical work before: the kind that touches many teams and requires you to build consensus, not just code.

• You understand observability (structured logging, tracing, Sentry) and have opinions about what to measure.

• Solid with SQL/PostgreSQL and schema design.

• Strong English communication, written and verbal.

• Experience with Hono, Bun, or other modern TypeScript server frameworks.

• You’ve used Backstage, ArgoCD, or similar developer portal / GitOps tooling.

• Familiarity with Protobuf, OpenAPI, or schema-first API design.

• Background in DDD or domain modeling.

• Experience with Dependabot, Renovate, or similar dependency automation.

• You’ve built internal platforms, shared SDKs, or developer tooling before.

Turno connects short-term rental hosts with cleaners, automating the turnover workflow. As an Airbnb software partner, we support tens of thousands of hosts worldwide through advanced data-driven solutions.

LATAM Operations

This is a full-time contract role based in Brazil (fully remote) or Argentina (hybrid from our Buenos Aires office). We communicate primarily in English, so strong written and verbal skills are required. Work hours are flexible but require consistent availability from 10 AM–3 PM local time. The position offers up to 15 days of annual PTO plus paid local public holidays, subject to company discretion.