Skip to content
Free monthly webinarTech Careers 101 — one hour, live Q&A with the founder.Save your seat

Micro-Internship Work-Based Learning

Do the Work. Understand Your Role. Build Your Story.

Zero to 360 is a five-session simulated technology project in which participants take on defined roles, collaborate across a team, produce deliverables, and experience how workplace decisions move from discovery through presentation.

The journey

Five sessions. One real project.

  1. SESSION 01

    Enter the Workplace

    Learn SDLC fundamentals, form project teams, receive role assignments, and review the project brief.

    Deliverables: Role assignment · Project brief

  2. SESSION 02

    Discover and Define

    Identify the user, clarify the problem, gather needs, and define requirements.

    Deliverable: Requirements document or equivalent project artifact

  3. SESSION 03

    Build Sprint

    Teams create role-specific work such as designs, code, QA plans, user stories, or sprint-board updates.

    Deliverable: Working prototype, component, or role-specific contribution

  4. SESSION 04

    Test and Iterate

    Test the work, document findings, respond to stakeholder feedback, and improve the solution.

    Deliverables: Testing evidence · Iteration log · Stakeholder feedback

  5. SESSION 05

    Present and Translate

    Present the completed product or solution, reflect on individual contributions, and convert the experience into a career roadmap.

    Deliverables: Final presentation · Completed project package · Individual career roadmap

Role experience

Take on a real role.

Every participant is assigned a defined role with real responsibilities — not everyone performs every role, and that is what makes the teamwork real.

Business Analyst

Clarify the business need, interview stakeholders, write requirements, and keep the team pointed at the real problem.

Developer

Turn requirements and designs into a working component or prototype, and respond to what testing uncovers.

Quality Assurance

Build the QA plan, test the work against requirements, and document findings the team must act on.

User Acceptance Testing

Represent the end user, validate the solution against real needs, and deliver structured feedback.

Scrum Master

Facilitate standups and ceremonies, keep the sprint board honest, and remove blockers for the team.

Project Manager

Own the plan, the timeline, and stakeholder communication from kickoff through final presentation.

UX/UI

Research the user, design flows and interfaces, and hand off work developers can build — when included in the cohort design.

Tools of the workplace

Work with the tools teams actually use.

  • Azure DevOps
  • Agile/Scrum practices
  • Miro
  • Figma
  • GitHub
  • HTML/CSS
  • Quality-assurance tools and practices

Tools may vary by program configuration. Participants use the tools their role and project require — the goal is fluency in how the workplace uses them, not mastery of every listed tool.

Learning outcomes

What participants learn.

  • How a technology project moves from discovery to delivery
  • What their assigned role owns, produces, and depends on
  • How cross-functional teams hand work off and make decisions
  • How requirements, design, build, and testing connect
  • How to present work and translate experience into a career story

Evidence of work

What participants may produce.

  • Requirements and user stories
  • Designs, prototypes, or working components
  • QA plans and documented testing evidence
  • Sprint-board updates and iteration logs
  • A final team presentation and completed project package
  • An individual career roadmap

For organizations

What organizations receive.

  • A structured five-session micro-internship delivered for your cohort
  • Role assignment and team formation guided by facilitators
  • Participant deliverables produced inside a simulated technology project
  • Individual participant career roadmaps
  • A cohort summary report of engagement, deliverables, and observed strengths
  • Facilitation, materials, and stakeholder-review touchpoints included

Ideal cohorts

Who Zero to 360 is built for.

High school and postsecondary CTE programs building work-based learning hours.

Workforce boards and nonprofits preparing participants for technology careers.

Employers and community organizations running early-talent or upskilling cohorts.

Individuals who have explored roles — often through Zero to 180 — and want to do the work.

Facilitation and delivery

Facilitated end to end, delivered your way.

Facilitated

Zeroth Round facilitators guide every session — role assignments, ceremonies, stakeholder reviews, and the final presentation.

Virtual or on-site

Delivered live online, at your location, or as a hybrid — scheduled around your calendar and your cohort.

Adapted to the audience

Timing, project scenario, role mix, and tools are configured to the cohort and the delivery agreement.

FAQ

Common questions.

Is Zero to 360 an internship with an employer?

Zero to 360 is a micro-internship inside Zeroth Round's simulated technology workplace. It is not described as an employer-sponsored internship unless a real employer relationship exists — and the work experience, deliverables, and story participants build are real either way.

Does completing Zero to 360 guarantee a job, credit, or certification?

No. Zero to 360 does not promise employment, academic credit, or certification. Participants leave with real deliverables, a completed project package, and a career roadmap — evidence they can speak to in interviews and applications.

Will I master every tool listed?

No — and that is by design. Participants use the tools their role and project require; nobody masters every listed tool. The goal is fluency in how the workplace uses them, not tool certification.

Do participants choose their roles?

Participants express preferences, and facilitators assign roles based on the project, cohort design, and participant interests. Not everyone performs every role — that is what makes the teamwork real.

How big is a cohort?

Cohorts are sized so every participant has a real role with real deliverables. Tell us your group size in the proposal request and we will recommend a configuration.

How is this priced?

Pricing depends on cohort size, delivery format, and configuration. Request a Zero to 360 proposal and we will follow up. No payment is taken on this site.

Ready to do the work?

Bring Zero to 360 to your organization, or ask about joining a cohort as an individual.

Want to observe the workplace first? Explore Zero to 180

Ready to move from learning about technology to experiencing how it works?