About RiverX
RiverX is an AI platform for building and evolving websites and web applications. It brings model selection, coding agents, repository-backed projects, live previews, database provisioning, and publishing into a connected workflow. People should be able to move from an idea to a working application, understand what the agent changed, and keep improving it without losing control of their code.
Our product spans a Next.js and React frontend, a Node.js backend, agent and workspace services, Supabase for authentication and core application data, and Turso for project databases and the skills catalog. GitHub, Railway, Vercel, and external model providers are part of the engineering environment. Each role below owns a specific part of making that experience dependable.
The role
You will help operate the environment where RiverX projects are edited, built, previewed, and published. These workloads run application code and development processes, have uneven resource demands, and need reliable persistence and recovery. Your focus is the execution platform and its operational boundaries, working closely with backend and agent engineers.
What you will own
- Improve workspace startup, process supervision, preview health, idle lifecycle management, and cleanup without losing project work.
- Strengthen the handling of terminals, child processes, build commands, file access, network access, and runtime resource limits.
- Make snapshot creation, integrity checking, restore, and retention dependable, with recovery procedures that are exercised rather than assumed.
- Improve deployments and service configuration across the platform’s hosting integrations, including health checks, secrets, logs, and rollback procedures.
- Trace reliability problems across application processes, memory and CPU pressure, preview proxies, networking, storage, and external services.
- Define useful alerts and operating indicators for workspace readiness, failed starts, preview availability, resource consumption, and recovery outcomes.
- Work on access boundaries and least-privilege execution, reviewing the actual process and request path rather than assuming that a configured runtime provides isolation everywhere.
- Document operational changes and validate them with representative projects, bounded failure tests, and a clear rollout plan.
What you should bring
- Experience running Linux-based services, containers, developer infrastructure, or comparable production systems.
- Practical knowledge of process lifecycles, networking, HTTP proxies, filesystems, permissions, and resource management.
- Ability to write and maintain automation and service code; RiverX’s platform is primarily Node.js, with shell and infrastructure tooling around it.
- Experience diagnosing incidents from logs, metrics, traces, and reproducible tests, including memory or concurrency failures.
- An understanding of persistent data, backups, restore testing, safe cleanup, and the difference between deployment success and service health.
- Strong ownership, clear operational writing, and a preference for incremental, reviewable changes.
Useful additional experience
Docker, remote development environments, browser preview infrastructure, PostgreSQL, object storage, Railway, Vercel, CI/CD, or sandboxing untrusted workloads. MicroVM experience is welcome as relevant expertise, not a claim about RiverX’s current runtime.
Early priorities
Map the workspace lifecycle and its persistence boundaries, reproduce a meaningful reliability problem, and ship a measured improvement. Validate a snapshot restore or recovery path and leave behind a runbook another engineer can follow.
Include in your application
An infrastructure or reliability change you owned, including the failure it addressed, how you rolled it out, and how you verified recovery.
Working together
This is a full-time, remote role. We work through clear written proposals, reproducible examples, thoughtful code or design reviews, and direct collaboration when a problem needs it. You should be comfortable owning an outcome across implementation, validation, documentation, and follow-through. Please include your location and time zone in your application so we can discuss practical collaboration arrangements.
How to apply
Apply through this page with your résumé as a PDF. Add links to relevant work and a short note explaining your contribution to a project, a difficult decision you made, and what you learned. Work can come from employment, open source, independent projects, or research. Share only material you have permission to share; please do not include customer data, credentials, or confidential code.