Junior Dev Docs

Introduction

It is not a course. It is not a bootcamp. You do not need experience to join. You need the willingness to show up, learn what you need as you go, and contribute to something real with people who are counting on you.

Most developer programmes teach you alone. You watch videos, complete exercises, and finish with a certificate that represents work you did by yourself. Junior Dev is built around a different belief — that the hardest skill in tech is not writing code, it is building something with people you did not choose, under a real deadline, with real accountability. That is what every job puts you in from day one. That is the environment Junior Dev creates.

What actually happens

You create an account, complete your profile, and when a season opens you pay a small activation fee that locks in your team slot. Teams are formed randomly by the platform. Within 72 hours of team formation, your team reviews the available project briefs and votes on which one to build. Each brief comes with a recommended tech stack, a project guide that breaks the build into components, and a learning path that tells you exactly what to study to complete your assigned tasks.

Over six weeks your team submits weekly milestones. At weeks three and five, another team reviews your work and gives you feedback. Week six is Demo Day — every team presents their work to the community live, and the community votes for their favourite project.

Every participant who activates their slot gets a Certificate of Participation. Every participant who finishes the full season gets a Certificate of Completion, a permanently hosted portfolio profile, and coins redeemable across the Looping Binary ecosystem. The best teams get scholarships, mentorship, and direct recruiter visibility.

Who this is for

Junior Dev is for anyone who wants to build real things with real people. Complete beginners, intermediate developers, self-taught builders, students, career switchers. The only requirement is that you commit to your team and see the season through.

Getting Started

Getting into Junior Dev takes less than five minutes to set up.

How Teams Work

Team structure

Teams are flat. There is no assigned leader. Your team decides how you organise. Some teams elect a lead, others rotate responsibilities, others split the work equally. All of these can work. What kills teams is not deciding at all.

Have your first meeting within 48 hours of team formation. Agree on three things early — how you will communicate, when you will meet each week, and how you will divide the work. Write it down somewhere everyone can see.

Communication

How your team communicates is up to you. Most teams use WhatsApp for quick messages and Google Meet or Discord for weekly calls. Whatever you choose, commit to it. The number one reason teams fall apart is not skill gaps — it is silence.

If a teammate goes quiet, reach out directly before escalating. If they remain unresponsive for more than a week, report it through the platform. The Junior Dev team will follow up.

Decision making

You will disagree on things. That is healthy. When your team cannot agree on a direction, make a decision and move. A wrong decision that gets made is better than a perfect decision that never does. You can correct course. You cannot recover time.

When things get difficult

Can I bring my own teammates?

No. Team formation is always random for first-time participants. This is non-negotiable — it is the core of what makes Junior Dev different from building something with your friends.

The one exception is returning participants. If you have completed two or more seasons you can toggle an alumni matching preference on your profile before registration closes. This puts you in a pool with other returning participants rather than first-timers.

Projects & Challenges

At the start of every season a set of project briefs is released. Your team reviews them together and votes on which one to build. Once selected and confirmed, your team is locked into that project for the season.

What a project brief contains

• A real-world problem to solve with context, goals, and core features expected in the final product.
• Optional stretch features for teams that want to go further.
• A recommended tech stack — your team can adopt it or build with whatever you know best.
• A project guide breaking the build into individual components and tasks.
• A learning path pointing you to the exact resources and courses to complete your assigned task.

Choosing your project

Once teams are formed your team has 72 hours to review the available briefs and submit your selection. Each member votes, and the majority decides. If there is a tie, discuss and resubmit. Treat the 72-hour window as your first real team meeting — it is the first decision you make together.

Scope and expectations

Junior Dev is not asking you to build a billion-dollar product. It is asking you to build something that works, solves the problem in the brief, and that your team can explain and defend on Demo Day. A clean working project that does less will always beat an ambitious project that does not run.

Milestones & Submissions

The six-week programme is broken into weekly milestones. Each milestone has a deadline and specific deliverables. Milestones keep your team on track and are how you earn coins.

The milestone schedule

How to submit

All submissions go through your dashboard. Go to your milestones page, find the active milestone, and submit the required links or files before the deadline. Only one team member needs to submit on behalf of the team, but every member is responsible for making sure it happens.

Late submissions

If your team is falling behind, reach out to the Junior Dev team as early as possible. We would rather work with you to find a path forward than have you quietly miss deadlines until it is too late to recover.

Peer Review

Peer review is when your team reviews another team's work — and another team reviews yours. It runs twice during the season, at week 3 and week 5, after your milestone submission.

How it works

• After your team submits a milestone, the platform assigns you a team to review.
• A different team is assigned to review yours at the same time.
• You never review yourself and you never review the same team twice in a season.
• Look at what the assigned team submitted — their build, their repo, their notes.
• Fill out a short structured review: what is working well, what needs improvement, and a score out of 10.

Why it exists

For the team being reviewed — you get a perspective from outside your own heads. When you have been staring at the same project for three weeks you stop seeing its problems. Another team sees them immediately.

For the team doing the reviewing — reading someone else's code or approach forces you to think critically about quality. You will go back to your own project and see things you missed. Peer review scores also feed into the final evaluation alongside your Demo Day presentation.

Rules

Why We Charge

Last season we learned something important.

Not from the teams that showed up. From the ones that didn't.

Season 1 had teams where one or two members simply stopped showing up. No warning. No message. Just gone. And the teammates left behind — the ones who paid attention, hit every milestone, stayed up late to submit — had to carry the weight or watch their team fall apart.

We listened to those complaints. And we did something about it.

Starting Season 2, every participant pays a small activation fee before they are assigned to a team. Not because we need the money. Because we need to know you mean it.

What we learned about commitment

When something costs you nothing it is easy to treat it like nothing. When you put something in — even something small — you show up differently. You answer messages. You hit your milestones. You care what happens to your team because you have skin in the game.

The activation fee is not a barrier. It is a filter. It separates the people who are genuinely ready to build from the people who are just curious whether they might be interested someday.

What the fee actually gets you

This is not just an entry ticket. Depending on the tier you choose, your activation fee unlocks real value from day one.

The fee does not just buy you accountability. It buys you tools, visibility, and a direct line to opportunities that do not exist outside this programme.

What happens if a teammate still goes inactive

We have not just relied on the fee to solve the problem. The platform now tracks activity automatically.

The short version

Tiers & Pricing

Junior Dev has three activation tiers. Every tier includes a team slot, milestone access, coin eligibility, a Certificate of Participation, and a Certificate of Completion if you finish.

You can upgrade from Starter to Builder or Pro at any point during an active season by paying the difference. You never lose what you already paid for.

Upgrading Your Tier

You can upgrade your tier at any point while the season is active. You pay only the difference between your current tier and the new one.

Once payment is confirmed your new features unlock immediately. Your Intellex access, Perplexity access, recruiter directory placement, and community channel access all update in real time. Nothing you already paid for is lost.

Rules

• You can only upgrade, never downgrade.
• You can upgrade at any point while the season is active.
• If the season has ended you cannot upgrade retroactively.
• Your tier applies to the current season only — next season you register fresh at whatever tier you choose.

Coins & Rewards

Junior Dev runs on a coin economy. You earn coins by completing milestones, engaging with the programme, and finishing the season. Coins are real — they are redeemable across the Looping Binary ecosystem including on Intellex for course discounts.

How you earn coins

Team milestone coins are split equally per member. Individual coins (marked above) go to that person only. Coins do not expire and carry across seasons.

Deductions

Coins move in both directions. You earn them by completing milestones and participating. You lose them by missing commitments, going inactive, or skipping peer reviews. This is intentional — your coin balance is a record of how seriously you took the season.

What coins can do

Redeem coins on Intellex for course discounts ranging from 15% to 30% depending on your balance. More redemption options are added each season as the Looping Binary ecosystem grows.

Season awards

Streak rewards

• Complete two consecutive seasons → Returning Builder badge
• Complete three consecutive seasons → Junior Dev Veteran status with permanently elevated profile ranking

Certificates

Junior Dev issues two types of certificate.

• Both certificates are digitally verifiable and permanently linked to your Junior Dev public profile.
• You can download them, share them, and link to the verification page from your LinkedIn or CV.
• Certificates are issued within 48 hours of the season closing.

Demo Day

Demo Day is the final event of every Junior Dev season. Every team that reaches week six presents what they built. The community watches, votes, and the best teams are recognised.

What Demo Day looks like

Demo Day is held online. Each team gets a ten-minute presentation slot to walk through their project — show the working product, explain the problem it solves, talk through the decisions your team made, and take a couple of questions.

What to prepare

Your week six submission includes everything you need — your final build, a 3–5 minute demo video, and a presentation deck. The deck should cover:

• The problem your project solves
• Your solution and how it works
• How you built it (stack, architecture decisions)
• What you would do with more time
• What each person personally learned

Community voting

After all teams present, the community votes for their favourite project. This is the People's Choice award — entirely separate from the judging panel's Top Team selection. Everyone in the Junior Dev community — participants, alumni, spectators — can vote. You are allowed to campaign.

After Demo Day

• Results announced at the end of the event.
• All completion coins and certificates distributed within 48 hours.
• Top Team rewards distributed within one week.
• Every Demo Day is recorded and added to the season archive — your presentation and project stay publicly accessible permanently.

Portfolio & Visibility

Every participant who activates a season slot gets a permanently hosted public profile at juniordev.loopingbinary.com/u/your-name.

What your profile shows

• Your name, location, skill level, and tech stack
• Every season you participated in
• The projects your team built with links to live products
• Your specific contributions — which tasks you completed and which milestones you hit
• Your awards and badges
• Your certificates with verification links
• Links to your GitHub, LinkedIn, and portfolio
• A downloadable CV if you have uploaded one

The recruiter talent directory

Companies and hiring managers can browse all participant profiles filtered by skill, tech stack, season, country, and completion status. They see your project history, your milestone consistency, and your peer review scores — not just what you claim to know.

Post-season recruiter newsletter

After every Demo Day, Looping Binary sends a curated newsletter to its hiring partners featuring standout participants from the season. Pro tier participants are automatically considered. Top Team and People's Choice winners are always included.

Profile visibility rules

• Your profile is visible to recruiters as long as your account has at least one active or completed season registration.
• If you complete a season your profile stays visible permanently — even between seasons.
• If you abandon a season without completing it and have no prior completed seasons, your profile is hidden until you return and complete one.

Rules & Conduct

Junior Dev is a community built on respect, honesty, and commitment.

On inactivity

What happens when rules are broken

Minor issues are handled with a direct conversation first. Repeated or serious violations — harassment, deliberate cheating, persistent non-communication — result in removal from the season without coin eligibility.

FAQ