Platform Engineer
Own the infrastructure and reliability of Fluxer end-to-end: deployment pipelines, databases, observability, capacity, and incident response.
Future role, not open
No roles listed here are currently open. You can still send an application now, and we will keep it for a future hiring round.
Listed March 1, 2026
About this future role
This role is not currently open. We keep this page to show the platform work we may hire for later, and we accept applications now for a future hiring round.
When this role opens, the platform engineer will look after the systems Fluxer runs on, and the habits that keep it humming along. We don't draw a hard line between infra and SRE; the same person tuning the deployment pipeline is the one writing the runbook, looking at the dashboard, and walking through the post-incident review the next morning. The breadth is half the appeal.
The stack is polyglot, on purpose: actor-based concurrency for connection handling and message routing, relational and wide-column databases, caching layers, object storage, and a media tier of its own. Everything is open source, so you can poke around the production code before you decide to apply. If you enjoy the kind of complexity that rewards making things both readable and resilient, this is your kind of role.
What you'll do
- Design and run the CI/CD pipelines that move our polyglot codebase to production
- Look after container orchestration and the deployment flow end-to-end
- Operate, tune, and recover production databases (relational and wide-column)
- Help set service reliability targets, error budgets, and capacity plans, and keep them grounded in reality
- Build observability that people actually use: metrics, logs, traces, alerts, and the glue between them
- Make incident response feel less stressful: runbooks, on-call rotations, escalation paths, the lot
- Track down performance bottlenecks wherever they're hiding
- Improve the day-to-day developer experience, from local setup to production debugging
- Look after secrets, certificates, and security hardening across environments
- Run post-incident reviews and make sure the follow-ups actually land
What we're looking for
- 3+ years of time spent in infrastructure, platform engineering, SRE, or production operations
- Comfort with Linux systems administration and shell scripting
- Hands-on experience with containerisation and deployment automation
- Experience running production databases at non-trivial scale
- A good working relationship with monitoring, alerting, and modern observability tools
- A real feel for distributed systems and the ways they tend to misbehave
- Calm, methodical debugging when something's on fire
Nice to have
- Experience with reproducible build systems (such as Nix)
- Familiarity with deploying and operating actor-model runtimes in production
- Experience with S3-compatible object storage and CDN configuration
- Working knowledge of network security, TLS, and DNS
- Familiarity with distributed tracing and modern observability standards
- Background in real-time communication infrastructure (WebSocket, WebRTC, media servers)
- On-call experience under structured incident management
How to apply
Send your CV as a PDF (not a Word .doc or .docx file), or include a publicly accessible website URL to your CV, a link to your GitHub or portfolio, and a short note about why you're interested to careers@fluxer.app. This role is not open right now, so we are not reviewing or replying to applications yet. We will keep your application on file for a future hiring round.
Send an application for later?
Send your application to careers@fluxer.app with your CV as a PDF (not a Word .doc or .docx file), or include a publicly accessible website URL to your CV. This role is not open now; we will keep your application for a future hiring round.
We are not reviewing or responding to applications right now. We will review saved applications when a relevant future hiring round opens.