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 own experiments that help the right builders discover RiverX and reach a useful first outcome. The work spans audience selection, acquisition, onboarding, and ongoing engagement. You will connect marketing activity to the product journey rather than treating traffic or signups as a complete result, and you will collaborate with engineers when a growth problem is actually a confusing or unreliable workflow.
What you will own
- Define initial audience and use-case hypotheses with product and sales, using actual builder needs and the platform’s current strengths.
- Develop a prioritized experiment plan across appropriate channels such as useful search content, demonstrations, partnerships, communities, referrals, lifecycle communications, or paid acquisition where warranted.
- Establish clear event definitions and measurement boundaries with engineering, covering acquisition, project creation, first useful build, publishing, and continued engagement where those signals are available.
- Improve landing pages and onboarding messages so the promise made before signup matches the experience inside the product.
- Design lifecycle communication that helps users finish a meaningful task, recover from friction, and discover relevant capabilities while respecting communication preferences.
- Use cohort analysis, qualitative feedback, and funnel evidence to identify where builders lose momentum and propose a focused experiment.
- Set an explicit hypothesis, audience, resource budget, acceptance criteria, and review point for each experiment. Scale, revise, or stop it based on the evidence.
- Coordinate content, design, product, and sales contributions without creating a disconnected campaign around every release.
- Maintain honest attribution and reporting: explain uncertainty, distinguish correlation from evidence of an effect, and avoid unsupported performance claims.
What you should bring
- Experience planning and running growth work for a software product, with responsibility for outcomes beyond reach or impressions.
- Strong analytical judgment and comfort with funnels, cohorts, experiment design, attribution limitations, and product analytics.
- The ability to produce or direct clear messaging, landing-page changes, and practical onboarding content.
- Experience working with engineers and designers to turn a hypothesis into an implemented, measurable change.
- Good prioritization when data is incomplete and there are more possible channels than the team can use well.
- Examples of experiments you owned, including an unsuccessful one and what you changed afterward.
Useful additional experience
Self-serve SaaS, developer products, AI tools, product-led adoption, technical content, lifecycle messaging, SEO, or a combination of qualitative research and quantitative analysis. Familiarity with PostHog or comparable analytics tools is useful.
Early priorities
Use RiverX end to end, audit the available measurement and onboarding journey, and identify a concrete activation obstacle or acquisition mismatch. Run a small set of focused experiments with documented baselines and interpretation, then propose where the next effort should go.
Include in your application
A growth case study explaining the audience, problem, experiment, evidence, and your own contribution. Share the limits of the result as well as what worked; do not include private account access or confidential customer data.
Working together
This is a full-time, remote role. We work through clear written plans, direct collaboration, and feedback tied to evidence. You should be comfortable owning an outcome from preparation through execution, measurement, and follow-up. Please include your location and time zone so we can discuss practical collaboration arrangements.
How to apply
Apply through this page with your résumé as a PDF and a short note about why this work interests you. Include relevant project, writing, portfolio, or campaign links and explain what you personally contributed. Coursework, community work, independent projects, and open-source contributions are welcome evidence. Share only work you have permission to share; do not include confidential customer information, credentials, or private business records.