The challenge structure
Four weeks. Four identities.
Each week unlocks a new identity and a new set of challenges. Click any week to see the full daily schedule. Complete Week 1 to unlock Week 2.
🔭
0% → 25%
▼
Week 1 — Explorer
"Show us who you are."
Both tracks, same tasks. Week 1 is about showing up and showing who you are. Your track shapes how you approach each gate.
| Day | Date | Task | What to do | +% |
|---|---|---|---|---|
| Day 1 | Dec 1 | Register & Introduce Yourself | Create your account and post your intro in the community feed. | +5% |
| Day 2 | Dec 2 | Complete Your Profile | Add your track, background, and the one tool you want to master. | +10% |
| Day 3 | Dec 3 | Explore Workspace + EDU | Tour your workspace. Start your Week 1 EDU class. Explore the Arena. | +15% |
| Day 4 | Dec 4 | Show Your Best Work | Submit one project — GitHub repo, live site, script, campaign, or workflow. | +20% |
| Day 5 | Dec 5 | Join the Community Session | Attend or watch the sync. Post your key takeaway in the feed. | +22% |
| Day 6 | Dec 6 | Give Peer Feedback | Review two other challengers' Day 4 submissions. Be specific. | +24% |
| Day 7 | Dec 7 | Week 1 Reflection | What did you learn? What surprised you? What changes in Week 2? | +25% |
⚡
25% → 50%
▼
Week 2 — Creator
"Build something real."
Tracks diverge here. Dev analyzes and improves antcpu.cloud. Marketing analyzes and improves antcpu's reach. Same analytical muscle — different domains.
| Day | Date | Task | What to do | +% |
|---|---|---|---|---|
| Day 8 | Dec 8 | W2 Brief + Workspace Tour | Review the open PRs on antcpu.cloud. Pick your target: feat/arena-uifix, feat/ad-ranking, feat/tier-upgrade. | +30% |
| Day 9 | Dec 9 | Analyze Something | Find a real bug or UX issue in antcpu.cloud. Document it clearly. | +33% |
| Day 10 | Dec 10 | Why Does It Fail? | Write a proper bug report — steps to reproduce, expected vs actual, severity. | +36% |
| Day 11 | Dec 11 | Improve It | Draft a fix or PR. Even a partial solution with clear reasoning counts. | +40% |
| Day 12 | Dec 12 | Explain Your Thinking | Document your approach. Not just what you did — why you did it. | +44% |
| Day 13 | Dec 13 | Feedback Day | Review another dev's work. Give one specific improvement suggestion. | +47% |
| Day 14 | Dec 14 | Week 2 Reflection | What did you build? What would you do differently? | +50% |
| Day | Date | Task | What to do | +% |
|---|---|---|---|---|
| Day 8 | Dec 8 | W2 Brief + Arena Tour | Explore the Arena. Understand the Map of Pi campaign. Pick your country. | +30% |
| Day 9 | Dec 9 | Analyze the Audience | Who is antcpu for? Research your country's dev/marketing community. Document what you find. | +33% |
| Day 10 | Dec 10 | Why Isn't It Reaching Them? | Identify one gap in antcpu's current reach. Write a clear problem statement. | +36% |
| Day 11 | Dec 11 | Build the Campaign | Create your first live content piece — post, thread, video, or graphic. Publish it. | +40% |
| Day 12 | Dec 12 | Explain Your Thinking | Document your strategy. Not just what you posted — why you chose that angle. | +44% |
| Day 13 | Dec 13 | Feedback Day | Review another marketer's content. Give one specific improvement suggestion. | +47% |
| Day 14 | Dec 14 | Week 2 Reflection | What did you build? What would you do differently? | +50% |
🤝
50% → 75%
▼
Week 3 — Collaborator
"Work with the team."
⚡ Week 3 is where the tracks meet.
You've spent two weeks building in your own lane. Now you explain your work to someone who built in the other lane.
💻 Dev → Marketing: Walk your partner through what you built. No jargon. Explain it like they'll have to sell it.
📣 Marketing → Dev: Walk your partner through your campaign. Ask: what do you need from the product to make this work?
You've spent two weeks building in your own lane. Now you explain your work to someone who built in the other lane.
💻 Dev → Marketing: Walk your partner through what you built. No jargon. Explain it like they'll have to sell it.
📣 Marketing → Dev: Walk your partner through your campaign. Ask: what do you need from the product to make this work?
| Day | Date | Task | What to do | +% |
|---|---|---|---|---|
| Day 15 | Dec 15 | Teams Announced | Meet your Marketing partner. Read their Week 2 work before you talk. | +52% |
| Day 16 | Dec 16 | Dev Explains the Build | Walk your Marketing partner through what you built. No jargon. Explain it like they'll have to sell it. | +55% |
| Day 17 | Dec 17 | Marketing Explains the Campaign | Listen to your Marketing partner. Ask: what do you need from the product to make this campaign work? | +58% |
| Day 18 | Dec 18 | Improve Based on Feedback | Take one piece of feedback from your Marketing partner and act on it. Show the change. | +61% |
| Day 19 | Dec 19 | Document the Collaboration | Document what your Marketing partner changed and why it makes the product stronger. | +64% |
| Day 20 | Dec 20 | Joint Submission | One shared deliverable. Both names on it. A product with a campaign, or a campaign with a product. | +70% |
| Day 21 | Dec 21 | Week 3 Reflection | What did working with a Marketer teach you? What would you build differently? | +75% |
| Day | Date | Task | What to do | +% |
|---|---|---|---|---|
| Day 15 | Dec 15 | Teams Announced | Meet your Dev partner. Read their Week 2 work before you talk. | +52% |
| Day 16 | Dec 16 | Dev Explains the Build | Listen to your Dev partner. Ask: what does this product do that my audience needs to know? | +55% |
| Day 17 | Dec 17 | Marketing Explains the Campaign | Walk your Dev partner through your campaign. Explain the audience, the message, the channel. | +58% |
| Day 18 | Dec 18 | Improve Based on Feedback | Take one piece of feedback from your Dev partner and act on it. Show the change. | +61% |
| Day 19 | Dec 19 | Document the Collaboration | Document what your Dev partner built and why it makes your campaign stronger. | +64% |
| Day 20 | Dec 20 | Joint Submission | One shared deliverable. Both names on it. A campaign with a product, or a product with a campaign. | +70% |
| Day 21 | Dec 21 | Week 3 Reflection | What did working with a Dev teach you? What would you campaign differently? | +75% |
Dec 20 — Joint Submission. One deliverable. Both names on it. This is the most important submission of the challenge.
🚀
75% → 100%
▼
Week 4 — Leader
"Own something."
| Day | Date | Task | What to do | +% |
|---|---|---|---|---|
| Day 22 | Dec 22 | Mission Briefing | Dev + Marketing united. One mission. Read the brief. Understand the full scope. | +78% |
| Day 23 | Dec 23 | Planning Day | Define the build plan. What are you shipping? What does Marketing need from you? | +80% |
| Day 24 | Dec 24 | Build + Prepare | Build the thing. Real code. Real feature. Aimed at shipping. | +83% |
| Day 25 | Dec 25 | Handoff | Hand off the build to Marketing. Document what it does and how to talk about it. | +86% |
| Day 26 | Dec 26 | Launch | Support the launch. Answer Marketing's questions. Fix anything that breaks. | +88% |
| Day 27 | Dec 27 | Community Interaction | Engage with feedback. Respond to questions. Iterate if needed. | +90% |
| Day 28 | Dec 28 | Final Polish | Clean up the code. Write the docs. Make it presentable. | +93% |
| Day 29 | Dec 29 | Final Submission | Submit everything. Code, docs, reflection, and your honest assessment of the collaboration. | +95% |
| Day 30 | Dec 30 | Final Review | Review your submission. Answer any questions from the antcpu team. | +97% |
| Day 31 | Dec 31 | Selection Day | Interns announced. Builders Network opens. Whatever happens — you showed up for 31 days. | +100% |
| Day | Date | Task | What to do | +% |
|---|---|---|---|---|
| Day 22 | Dec 22 | Mission Briefing | Dev + Marketing united. One mission. Read the brief. Understand the full scope. | +78% |
| Day 23 | Dec 23 | Planning Day | Define the campaign plan. What are you launching? What do you need from Dev? | +80% |
| Day 24 | Dec 24 | Build + Prepare | Build the campaign assets. Copy, visuals, channels. Aimed at launching. | +83% |
| Day 25 | Dec 25 | Handoff | Receive the build from Dev. Understand it well enough to explain it to anyone. | +86% |
| Day 26 | Dec 26 | Launch | Launch the campaign. Own the message. Track what happens. | +88% |
| Day 27 | Dec 27 | Community Interaction | Engage with responses. Amplify what's working. Document results. | +90% |
| Day 28 | Dec 28 | Final Polish | Tighten the copy. Update the analytics. Make the results presentable. | +93% |
| Day 29 | Dec 29 | Final Submission | Submit everything. Campaign assets, results, reflection, honest assessment of the collaboration. | +95% |
| Day 30 | Dec 30 | Final Review | Review your submission. Answer any questions from the antcpu team. | +97% |
| Day 31 | Dec 31 | Selection Day | Interns announced. Builders Network opens. Whatever happens — you showed up for 31 days. | +100% |
Dec 31 — Selection Day. Interns announced. Builders Network opens for everyone else. The internship runs January 2027 – April 2027, fully remote.
Cohort 1 · August 2026
The founding interns.
Two people showed up, did the work, and earned the first Human in the Loop Internship. Your name could be next.
CC
Chase C.
🏆 Human in the Loop Intern
AM
Amanda M.
🏆 Human in the Loop Intern
December 1 is — days away.
Register now. Your dashboard unlocks automatically at midnight on December 1.