Infrastructure Engineer

About Engineering at Fonoa

Engineering is central to how we build the business. We focus on solving real customer problems, not just shipping features. We work in small, high-trust teams, with full ownership across the lifecycle, from design to production and beyond.

We value:

• Ownership – engineers own what they build end-to-end

• Simplicity – we break down complex problems into clear solutions

• Thinking Big - we innovate with modern technologies (LLMs, AI Agents, etc.) to solve meaningful problems

• Quality – scalable, maintainable systems are non-negotiable

• Speed & iteration – we ship fast, learn, and improve continuously

• Collaboration – we win as a team, not as individuals

Position Overview

Following a recent acquisition, Fonoa now runs two infrastructure estates, and we're migrating the acquired product's infrastructure onto Fonoa's own.

We're looking for an Infrastructure Engineer to join our SRE team as the first line for everything that lands on it: handling requests and interruptions, keeping the acquired product's infrastructure running day-to-day, and making sure planned work actually gets planned instead of quietly eating the team's week.

Yes, there's operational work here, and the role's purpose is to reduce it. Every recurring request is a candidate for automation, self-service, or documentation, and every manual migration step is a candidate for a script.

You'll work closely with product engineering teams and the rest of the SRE team, evolve our Kubernetes and cloud environments, and help bring the acquired product onto Fonoa's platform in a way that's repeatable, automated, and as uneventful as possible.

We're looking for someone who's comfortable in a fast-moving environment, likes bringing order to messy inputs, and wants infrastructure that stays reliable, simple, and delightfully boring as the company grows.

What you will be doing

• Owning the team's intake: triaging incoming requests and interruptions, resolving the quick ones, and turning the rest into planned work together with the team.

• Operating the acquired product's infrastructure day to day while we migrate it.

• Taking part in migrating the acquired product's infrastructure onto Fonoa's platform and automating the repeatable parts.

• Turning recurring requests into self-service tooling, automation, or documentation.

• Participating in an on-call rotation for the services the team owns.

You would be a great fit if

• You are fully proficient in English, written and spoken. We're a bunch from around the world, and we work in English.

• You communicate clearly and asynchronously, including telling someone "not now, but here's when" without damaging the relationship.

• You're comfortable with frequent context switching and stay organised while doing it.

• You're comfortable working in systems you didn't build and don't fully understand yet, and you enjoy figuring them out.

• You have an automation mindset focused on streamlining daily operations.

• You manage infrastructure as code. It doesn't exist if it's not in git.

• You have programming skills in at least one language, or can learn more if the opportunity arises.

• You strongly favour simplicity over complexity.

• You solve problems with other people. You're a team player, not a hero. We share the knowledge (and sometimes the pain).

• You use data over opinions to make decisions, and you're fine with finding the data yourself when it's missing.

• You have a strong sense of ownership and care about what you build.

• You are comfortable with changes in priorities, goals, and deadlines. You see this more as an opportunity than a hurdle. You are also comfortable challenging the status quo and pushing for change yourself.

Key projects you’ll work on

• Bringing the acquisition home. Help move the acquired product's infrastructure onto Fonoa's platform and automate the hell out of it along the way, so the last service migrates as boringly as the first.

• Shrinking the ticket inbox. Find the requests that keep coming back to the team and make them self-service, so engineers get what they need without waiting on an SRE.

• Keeping Kubernetes boring. Operate and improve our Kubernetes runtime across cloud providers using Terraform, CRDs, and common sense.

• Observability that covers everything. Keep our observability stack (Grafana, Prometheus, Datadog) lean and useful, and extend it to cover the acquired product's estate so nothing runs unwatched.

API Documentation

For engineers, API design and structure are an important part of evaluating a role. You can explore our API and how we build products here:

Tech Stack

We use these technologies today, but we don’t hire for specific tools. We care about engineers who can understand problems, make good technical decisions, and choose the right tools for the job.

• Backend: Node.js, Go

• Frontend: React, TypeScript

• Infrastructure: GCP, k8s, Terraform, Postgres

Note:
If you don’t think you have the full experience we’re looking for, but you could be a fit and are willing to learn, do apply anyway! We are building a diverse and inclusive team.

As part of the recruitment process at Fonoa, we process your personal data in accordance with our Privacy Notice for Job Applicants. This notice explains how and why your data is collected and used, and how you can contact us if you have any concerns.