Backend Developers
APIs, databases, auth, deployment pipelines. Practice system design in a real sprint, not a whiteboard interview.
For Developers
Ship code with a team. Master Git. Build for production.
Whether you’re backend, frontend, or full stack, you’ll work the same way real teams do: pull requests, standups, retros, and a deployed product at the end.
If you can build something solo, you’re ready for a team.
Frontend Developers
Use HTML, Tailwind CSS, JS/Typescript and React to manage states and flows for a responsive, interactive UI.
Full Stack Developers
Own a feature end-to-end — from Figma handoff to live URL. Negotiate the API contract with your own backend teammate.
The things tutorials skip.
- Git & GitHub in a team. Feature branches, code review, merge conflicts, rebase vs. merge — the gap between solo and team Git is wide, and this is where you close it.
- Pull request culture. Writing a PR that someone else can review. Reviewing a PR without being a jerk. Shipping code through the gauntlet.
- Sprint rhythm. Standups, sprint planning, retros. The cadence that keeps remote teams aligned.
- Production-grade practices. Testing, CI/CD, deployment. Your code runs on the internet and your team relies on it.
- Cross-functional communication. Talking to designers about handoff. Talking to a PO about scope. The work that hiring managers actually care about.
- Remote collaboration. Async-by-default. Writing things down. Respecting timezones that aren’t yours.
Real teams, real tools.
Teams self-select tech stacks. You’ll see Voyages running on every combination below — and if you want exposure to something new, you can team up around it.
ReactNext.jsTypeScriptNode.jsExpressPythonDjangoFastAPIGoPostgreSQLMongoDBRedisDockerGitHub ActionsVercelSupabaseReact NativeFlutter
“Six weeks of collaborative coding changed how I think about building software.”
Find your path into the Voyage.
See how the seven weeks work, or apply now for the next cohort.