Getting Started

Junior Dev is a team-based developer programme run by Looping Binary where five developers are matched, choose a real project, and have six weeks to build and ship together.

It is not a course or a bootcamp. It is built to mirror real product collaboration before your first tech job.

Most programmes teach in isolation. Junior Dev focuses on the real skill interviews test most: working with other people under deadlines.

Developers at any level can join. The key requirement is commitment, communication, and follow-through.

Step 1 — Create your account on juniordev.loopingbinary.com and verify your email.

Step 2 — Complete your profile with your skill level, preferred technologies, and weekly availability.

Step 3 — Join the community WhatsApp: https://chat.whatsapp.com/IhJ0e6geHy21UhVtpy9hd7?mode=gi_t.

Step 4 — Wait for the season open announcement.

Step 5 — Enrol once season registration opens and lock in your spot before the deadline.

Step 6 — Receive your randomly assigned team and begin introductions immediately.

Each team has five members and is assigned randomly by design. This simulates real-world collaboration.

Teams are flat by default. You can elect a lead, rotate responsibilities, or split work equally.

Hold your first team meeting within 48 hours and agree on communication channel, meeting rhythm, and task split.

Silence breaks teams faster than skill gaps. If someone goes inactive for over a week, report it early so support can intervene.

When decisions stall, pick a direction and move. Iteration beats indecision.

At season start, project briefs are released. Teams review and vote for one brief.

Briefs explain what to build and why, not how. Stack and implementation choices remain with your team.

Teams have 72 hours after formation to discuss and submit project selection.

After confirmation, the six-week build clock starts and your milestone schedule becomes active.

Start small, ship working increments, then expand scope.

Week 1: kickoff and initial plan. Week 2: project foundation. Week 3: core build. Week 4: progress checkpoint. Week 5: feature complete. Week 6: demo-ready final delivery.

All submissions happen through the platform milestone page. One teammate can submit, but everyone is accountable.

Late submissions are accepted up to 24 hours with penalties. More than 24 hours is marked missed.

Peer review rounds occur in weeks 3 and 5 to strengthen delivery quality and feedback habits.

If your team is slipping, communicate early so support can help before recovery becomes difficult.

Junior Dev uses a coin economy. Actions like profile completion, on-time milestones, peer review, and Demo Day participation earn coins.

Team-earned coins are split across team members.

Coins can be redeemed across the Looping Binary ecosystem, including Intellex discounts.

Coins carry over between seasons while your account remains active.

Top teams and completion participants receive additional rewards and recognition each season.

Demo Day is the final event where each week-six team presents what they built.

Presentation slots are short and focused: problem, solution, product walkthrough, decisions, and lessons learned.

You are expected to show a real product, not a perfect product.

Prepare a short backup demo video to avoid technical disruptions.

Community voting determines People’s Choice while judges select top teams.

Show up consistently and communicate when your situation changes.

Be honest about your skill level so team formation remains fair.

AI-assisted work is allowed; replacing your full team output with generated content is not.

Respect everyone. Harassment, discrimination, and gatekeeping are not tolerated.

Mistakes are expected in a learning programme. Conduct rules exist to protect the community, not punish growth.

Junior Dev uses paid season activation tiers (Starter, Builder, Pro).

You do not need to know other participants before joining.

One team per season is allowed.

Certificates are for full season completion.

If your question is not covered, ask in the WhatsApp community or contact support directly.