Europe or Latin America or United States · Remote · Full-time
Backend Software Engineer
OllyGarden Insights analyzes our customers’ OpenTelemetry® data, finds telemetry problems, and scores every service. The services you will own sit between our detectors and our customers. They discover the services in each organization’s telemetry, store the insights our detectors publish, and deliver them through our REST API, our MCP server, and webhooks. They also share one database schema, and you will own it, from its migrations to its tenant isolation. You will work in Go with NATS JetStream, Postgres on Supabase, and Kubernetes on AWS, as part of a small team.
What you’ll own
- Own our public REST API end to end: new endpoints, versioning and deprecation, latency, and the per-tenant limits that keep one customer from affecting another
- Own our database schema and its migration pipeline: evolve it as features need, review every change, test it in CI against a fresh database, and apply it through automation
- Keep tenant isolation enforced in the database as the schema and the number of services that use it grow
- Keep webhook delivery trustworthy: filtering, retries, idempotency, and a delivery history customers can rely on
- Keep service discovery and insight persistence correct and fast as telemetry volume grows: deduplication, consumer backpressure, and caching
- Run what you build in production: dashboards, alerts, and incident follow-ups for the services you own
- Work with our frontend and Rose engineers on the data and APIs their features need
Outcomes that matter
- Schema changes land safely: reviewed, tested against a fresh database, applied by automation, and never at the cost of tenant isolation
- API changes ship without breaking the integrations customers already run
- Failed webhook deliveries retry predictably, and customers can see exactly what was delivered and when
- Service discovery and insight persistence keep pace with telemetry growth
What we’re looking for
- Senior backend engineering experience, including Go services you shipped to production and kept running
- Strong Postgres skills: schema design, online migrations, indexes, transactions, and row-level security
- Experience with event-driven systems: streams or queues, at-least-once delivery, idempotency, and retries
- Experience designing public APIs that customers build on: authentication, pagination, versioning, and backward compatibility
- A habit of instrumenting what you build, and of using traces, metrics, and logs to debug production
- AI-native development, knowing how software is developed in the companies of the future, coordinating multiple agents and using AI-related engineering skills to get quality work from them. Your main IDE nowadays is Claude Code, Codex, Amp, or Conductor.
- Based in Europe, or Latin America, or USA
Bonus points
- Experience instrumenting services with OpenTelemetry, or working on observability tooling
- Production experience with NATS JetStream, or similar
- Experience designing and operating multi-tenant PostgreSQL schemas, including row-level security, roles and grants, production migrations, and query performance
- Experience building APIs designed for AI agents
- Experience maintaining an open source project, especially in the OpenTelemetry or Prometheus ecosystems
- Kubernetes on AWS, Flux, or Terraform
- Enthusiasm for sharing your work in public, from blog posts to conference talks
Interview process
Show us what you run
The process is practical. We want to see backend systems you have shipped and operated, how you handled them when they failed, and how you think about a real problem from our codebase.
- 01
A conversation with an engineer from our backend team about your background and why OllyGarden interests you
- 02
A technical deep dive into a backend system you shipped and operated: architecture, data model, failure modes, and how you knew it was healthy
- 03
Potentially, a paid, self-contained exercise based on a real problem from our services, such as an online schema migration or an idempotent event consumer
- 04
A conversation with our CEO, Juraci Paixão Kröhling, followed by reference calls