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 opportunity
Learn how a real AI development product is built by contributing to the interfaces people use to create projects, work with an agent, and preview their applications. You will start with focused improvements in RiverX’s React and Next.js frontend, then take on a more complete interaction as you become familiar with the codebase. This is a hands-on engineering internship with an emphasis on readable code, thoughtful interfaces, and learning to verify your work.
What you will work on
- Implement small, well-defined improvements to dashboard pages, project setup, model selection, and shared interface components using React, TypeScript, HTML, and CSS.
- Improve loading, empty, error, and success states so a builder can understand what is happening and what to do next.
- Check layouts with long content, narrow screens, keyboard navigation, and both light and dark themes.
- Fix interface bugs by reproducing them, tracing the relevant component and request, and proposing a focused change.
- Learn to handle asynchronous behavior such as a project being prepared, a preview restarting, or an agent response arriving over time.
- Add or update useful checks for changed behavior and document how you tested the result.
- Participate in code reviews, explain your choices, and incorporate feedback without turning a small task into an unrelated rewrite.
What you should bring
- A working understanding of JavaScript, HTML, and CSS, with some experience building a React application.
- Familiarity with components, props, state, forms, and fetching data from an API. TypeScript experience is useful, and you should be willing to learn it.
- Comfort using Git to make a branch, inspect a diff, and describe a change.
- Interest in accessibility and the patience to examine awkward states rather than checking only the ideal screen.
- The ability to communicate a blocker clearly, share a reproduction, and ask questions when requirements are unclear.
- A small project or other example that shows how you approach building an interface. It does not need to be a commercial product.
What you can learn
Next.js rendering boundaries, reusable components, browser debugging, responsive design, accessible interactions, and the practical challenges of presenting AI work in progress. You will also see how frontend decisions depend on API behavior and runtime state.
A useful first project
Take one confusing interaction, such as an error message or project-loading state, from reproduction to an implemented improvement. Explain how it behaves for keyboard users and on a narrow screen, and demonstrate that a failed or interrupted request leaves the user in a sensible state.
Include in your application
A link to a frontend project, a few sentences about your own contribution, and one detail you would improve if you had more time. A simple, well-understood project is more useful than a large repository you cannot explain.
Internship arrangements
This is a remote internship. Please share your location, time zone, earliest start date, weekly availability, and any academic commitments in your application. Duration and working arrangements will be discussed during the application process rather than assumed from a standard academic calendar. The role is intended for students, recent graduates, and early-career applicants; prior full-time employment is not required.
You will work on scoped tasks, make your assumptions explicit, and ask for review before a change reaches users. We value clear progress updates, willingness to use feedback, and careful verification more than familiarity with every tool in the stack. This listing does not promise conversion to a full-time position.
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.