Platform Engineer

We’re a funded, stealth startup modernizing overlooked assets within the hospitality industry.

We’re putting together a distributed, low-headcount, founding engineering team. This role reports to our CTO (who has extensive venture-building experience) and touches every service we run: you’ll be the person who gives us wings.

If you’re an infrastructure-minded engineer who:

1. keeps systems boringly reliable—CI/CD, observability, and infrastructure-as-code that the rest of the team can trust,
2. has been more than “just tinkering” with LLMs and codegen (“AI-pilled”, if you will), and reaches for AI tooling to move fast across both infra and application code, and
3. wants platform work to be the start of the story rather than the whole of it—you’re genuinely aiming to grow into building product…

…and you can work 4+ hours overlapped with UTC-04:00, we’d love to hear from you.

Note: we care more about demonstrable talent and trajectory than “perfect” candidates who check every box below. If this describes you, we very much encourage you to apply.

About This Role (read this part)

Today this is a platform/DevOps role. You’ll own our build, deployment, and observability layers as a proactive line of defense.

It’s also a growth role. We’re specifically looking for someone whose aspiration is lean into product/application AI-based engineering. We’ll build a real, planned path to get you there—pairing on feature work, picking up application tickets as you go, and expanding your scope over time.

While the platform work comes first, the app-dev growth is something we’ll invest in deliberately and immediately. Not someday—from day one.

What You’ll Do

1. Own our deploy pipeline and cloud infrastructure across every service (Fly.io + GCP + Other Vendors)
2. Codify everything as infrastructure-as-code (OpenTofu)—no click-ops, reproducible environments
3. Build and maintain observability—metrics, traces, logs, and alerting that catch problems before customers do (Grafana Cloud + OpenTel)
4. Harden CI/CD so engineers ship confidently and fast (GitHub Actions)
5. Use AI tooling heavily—Claude Code, pi.dev, codegen, and LLM agents are part of how we work, across infra and application code
6. Keep identity, secrets, and access sane—least-privilege, keyless auth where we can (Workload Identity Federation / OIDC)
7. Grow into application development—pair with product engineers, pick up feature work, and expand your scope over time

What We’re Looking For

Technical Chops

• 3–5 years of engineering experience (mid-level)—you’ve operated real systems, not just spun up demos, in a 24/7 all-year environment (with limited seasonality)
• Cloud and containers in production (GCP, AWS, or Azure; Docker)
• Infrastructure-as-code experience (OpenTofu/Terraform, Pulumi, or similar)
• CI/CD pipelines you’ve built or meaningfully owned
• Observability fundamentals—you instrument first and debug from data, not vibes
• Comfortable reading and writing application code in at least one backend language (we run Go, mostly)—because growing into product work is the point
• Some hands-on experience and strong opinions (weakly held) about LLMs and automated codegen as part of a modern engineering team

Working Style

• Founding team mentality - you thrive in ambiguous, rapidly-changing environments
• Systems thinking - you weigh reliability, security, and operability from day one
• Ownership mindset - you own the outcome, not just the ticket
• Self-directed - you work independently while staying aligned with the team
• Quality-focused - you leave systems more reliable and better documented than you found them
• Communication skills - you can explain trade-offs clearly to technical and non-technical folks alike

Helpful, but not necessary

• Experience in hospitality and travel (e.g., integrations with OHIP, MEWS, etc.)
• Hands-on with our specific stack (Fly.io, Grafana Cloud, OpenTofu)
• Security and identity work (WIF, OIDC, IAP, least-privilege IAM)
• PostgreSQL operations and data modeling
• Prior application/product development experience—since that’s where you’re headed
• Previous startup experience, especially at the founding stage

Our Tech Stack

This is what we actually run today—we’re opinionated but not dogmatic:

• Cloud: Google Cloud Platform (incl. Vertex AI, Workload Identity Federation)
• Compute: Fly.io
• Storage: Fly.io, Postgres, Turso, S3-compatible storage
• Infra-as-code: OpenTofu (Cloudflare for DNS)
• Observability: Grafana Cloud (Prometheus, Loki, Tempo) via OTLP
• Containers: Docker (for now)
• CI/CD: GitHub Actions
• Backend: Go + PostgreSQL
• Frontend: TypeScript
• AI: LLM-backed services on Vertex, with Claude Code / codegen in our daily workflow

We’re on a SOA, so some details from the above change by application (for instance, some apps are pure go + HTMX rather than TS on the frontend)

Ready to Apply?

Send us your resume along with:

• A 50-word note: something you’ve automated or made reliable that you’re proud of, and what you want to build next
• Links to your GitHub and any recent infra or application work
• (Optional) a pipeline, IaC, or config snippet you’re proud of

We’re committed to diversity and inclusion. All qualified applicants will receive consideration regardless of race, religion, gender, sexual orientation, age, disability, or veteran status.

We review applications on a rolling basis for platform engineers.