Everything runs in containers: a Go API and several worker processes on scratch images, three Next.js apps, PostgreSQL and Valkey, deployed to Kubernetes with Helm.
We want deploys to be unremarkable. That means CI that catches the right things, images that only rebuild when their own inputs change, and observability good enough that the first person to notice a problem is us.
What you would do
- Own the Helm chart, the Kubernetes manifests and the deployment path to production
- Keep CI fast and honest — per-app build scoping so one portal change cannot rebuild the customer site
- Run PostgreSQL and Valkey properly: backups that have been restored, migrations that can roll back
- Build the observability layer — metrics, logs and traces that answer questions rather than produce dashboards
- Manage secrets, certificates and the edge routing without any of it living in the repo
What we are looking for
- Kubernetes and Helm in production, not just in a tutorial cluster
- Strong Docker, including multi-stage builds and minimal base images
- CI/CD pipeline design — GitHub Actions here
- Comfortable operating PostgreSQL: backup, restore, migration safety
- Professional English, written and spoken
Nice to have
- Terraform or Pulumi
- Prometheus, Grafana, OpenTelemetry
- Cloudflare edge configuration
How we hire
- 1. Your application. CV plus a short note. We read it; it is not filtered by a keyword matcher.
- 2. A conversation. Forty minutes about what you have built and what you want to build.
- 3. Real work. A problem from this codebase, discussed together. Not a whiteboard algorithm, and not an unpaid weekend project.
- 4. Offer. With the reasoning, in writing.