Hello, volunteer! ⭐ Thanks for checking out the teacher hub and for supporting the ReDI students! ⭐
The volunteer team will consist of volunteers from different locations in Germany. If you are a continuing volunteer, the course format might be new for you. In this hub, you will find more information on each course, how it is set up, and how to support it. The resulting course offer is the following:
Founded in 2015, ReDI School of Digital Integration is a non-profit tech school providing migrants and marginalized locals free and equitable access to digital education.
We offer our learners high-quality coding and basic computer courses in combination with a unique career and mentorship program, which includes the chance to collaborate with tech companies, startups, and digital industry leaders.
We aim to provide our learners with valuable digital skills, a growth mindset, strengthened career skills, and a strong network of tech professionals to help create new opportunities for all.
We provide advanced tech skills training and career support to tech-savvy refugees and people with a forced migration background to accelerate their professional integration in the tech industry. Available in Berlin, Munich, NRW, and Hamburg.
ReDI School offers education to break down barriers and connect the leaders of tomorrow. We use technology to connect human potential with employment opportunities with dignity and humility.
To provide access to free digital education and create pathways to employment in the tech industry.
Our learners come from a wide range of backgrounds and life situations, and each semester brings a new and unique cohort. Last semester, for example:
🌍 They represented over 32 different nationalities
👩🎓 The average age was 31 years old
🎓 Their academic and professional backgrounds included Finance, Engineering, Biology, and more — with most holding at least a bachelor’s degree
40% were underemployed, looking to transition into a new career path
35% were unemployed and actively job hunting
25% were university students, preparing to enter the job market
Most students take the course with the goal of starting a career in tech. However, it’s important to remember they come with:
Different levels of prior knowledge
Varying learning speeds and styles
Personal situations, such as caring for young children — some may need to turn off their camera to protect their privacy or reduce distractions
Life transitions and challenges, including coming from conflict zones or navigating big career changes
This means that while some learners are immediately active and engaged, others may need more time or encouragement. Their engagement might look different — but their commitment is real!
Most importantly: you won’t be teaching alone. Depending on the course, you’ll be part of a teaching team — typically 6–8 teachers for our regular courses, and 12–15 for our Bootcamps.
Teamwork and communication are key to providing a great learning experience. That’s why we kindly ask you to stay active in communication:
Let us know in advance if you have any changes or can’t make a session.
After each class, please share key takeaways or notes for the next teaching team to build on. We'll have a Slackbot in your Slack teaching channel to help with that!
Active Participation: Participate in at least 50% of the sessions—either by teaching or co-facilitating—in order to receive your Volunteer Teaching Certificate.
Ownership: We encourage taking ownership of at least two sessions per semester to gain a full teaching experience.
Team Involvement: Join the team meetings, including the Planning Session (before the semester starts) and the Teacher Touchpoints (mid-semester check-in).
Collaboration & Support: Actively participate in teaching team decisions, respond promptly to student inquiries, and provide ongoing support throughout the course.
Proactive Communication: Communicate proactively with your teaching team and the ReDI Support Team if your availability or circumstances change.
Inclusive Environment: Foster an inclusive, respectful, and supportive learning environment for all students.
Content Commitment: If you’re assigned the role of moderator, we have pre-made materials available to guide you. However, part of your responsibility is to keep this content up to date. Feel free to add extra resources or adapt the materials to match your teaching style—your contributions are always welcome.
By volunteering as a teacher, you will develop and enhance a variety of valuable skills and enjoy important benefits:
Pedagogical Skills: Designing and facilitating engaging learning experiences.
Communication and Interpersonal Skills: Collaborating with team members and connecting with diverse learners.
Organizational Skills: Managing sessions, preparing materials, and balancing your commitments.
Cultural and Global Awareness: Embracing diversity and working in an inclusive environment.
Technical Skills: Applying and sharing your knowledge to help students progress.
Social Contribution: Making a positive impact by supporting underrepresented communities in tech.
Personal Development and Creativity: Growing professionally while experimenting with new teaching methods.
Access to Trainings, Workshops, and an Amazing Supportive Community to boost your growth and network.
The joy of making a difference in someone’s career journey 🧡
At ReDI, we believe career success is driven by both skills and connections. That’s why unique Career Services complement our tech training to help learners enhance soft skills and grow their professional networks. Through collaborations with companies in the German tech sector, we create direct pathways for learners to connect with industry professionals, recognizing that career transitions are about both what you know and who you know.
Here the three most impactful career services we offer to our students. More here.
Starting this semester Career Services will be divided into two parts:
Career Orientation for starters, versus intermediate and advanced tech classes
Bootcamps Career Project for Bootcamps participants (still in development)
The career services listed above are recommended to students of the courses listed below. However, we leave to our learners the choice and chance to participate in career activities, based on individual needs.
HTML / CSS
JavaScript
Python Foundations
Data Analytics
Infrastructure Basics
Machine Learning / AI
Creative Communications
Data & Full-Stack Circles
Talent Success Learner Hub: Career services info, tips and tricks, partners info
Learning Plans on IBM SkillsBuild Platform
Non-mandatory career support onboarding sessions for learners, with details about career events
Online Open Hour every week to answer questions about career services
Dedicated slack channel #25s_talent_and_career_support
Contacts: Slack user @Paulina - Email: career@redi-school.org
At ReDI, we follow the four values, which give an orientation on our behaviours and actions, both within the community and within ourselves as a team. Here what the ReDI values mean to us:
In the sense of impactful. We are a community moved by the wish to help others grow and are actively oriented towards this goal. Being helpful means trying to generate a real change in the life of others.
This is the most important value and has to do with experimenting in a fun and playful fashion. It refers to trying out new things and, if need be, making mistakes together and learning from them. It also means trying to build the "ideal learning environment" we all wanted to have in our own personal experiences.
Means trustful, in relation to the scope of our actions. We want to deliver the best quality of learning services to our learners because they are themselves relying on us for their education and deserve high-quality training from professionals like you.
We are "partners in crime" for our community to do things they didn’t even think they’d be capable of doing at the beginning. It means empowering others to understand they can cross their own limits, far beyond what they might have originally thought. Change is reflected the students also by the teachers because, through their flexibility and willingness to change, they are leading students to achieve their goals.
ReDI School aims to be a safe learning environment for all of its community members. The ReDI Code of Conduct sets the standards that allow us to keep our community safe and healthy, both online and offline. It establishes standards necessary to maintain and protect an environment conducive to learning and in keeping with the objectives of the program. The code of conduct is important to:
maintain and protect an environment conducive to learning and in keeping with the objectives of our ReDI School programs
protect our community and ensure that EVERYONE feels safe and comfortable in the online environment
By signing the Volunteer Agreement at the beginning of their teaching experience, volunteers agree to respect the ReDI Code of Conduct during their volunteer experience and interactions with students, other volunteers, as well as with the ReDI team and community.
As part of team planning and management, we kindly ask all teachers to share their availability in advance, both during the Planning Session (before the semester begins) and the Teacher Touchpoint (mid-semester check-in). This includes signing up for specific teaching sessions and also volunteering as a backup in case of any unexpected changes.
As a member of the teaching team—not just a solo teacher—your communication, commitment, and clarity around availability are incredibly valuable. This helps ensure a smooth and supportive experience for everyone involved: your students, your fellow teachers, and the ReDI Support Team When someone commits to teaching, the entire team counts on their active participation to deliver a consistent and high-quality learning experience.
What to do if you cannot teach a session
No worries—things happen! Let’s work together to find a substitute:
If it's up to one week before your session: Inform your team and request a substitute. Mention @channel in your teaching team Slack channel to make sure the message is seen.
If it’s two days before or less: Post in your team channel as soon as possible to ensure visibility, and also contact the ReDI Support Team directly for assistance.
We understand that sometimes, due to personal or professional circumstances, a teacher may make the decision to leave the class. We want to express our respect for their choice and appreciate the time and effort they have dedicated so far. We are here to support in the transition and ensure that the process is as smooth as possible for everyone involved.
Please notify someone from the ReDI Team about your decision
After that, notify your team; you can mention your reasons if you feel comfortable
You will be removed from the Course Slack Channel and Google Calendar
Let us know if you need any proof of volunteering
Finally, fill out this questionnaire
Help close the digital divide and empower others through the transformative power of technology
Make a lasting impact on individuals striving to rebuild their lives and embrace new opportunities
Join a vibrant, diverse community of dedicated volunteers—share your experiences, learn from others, and grow together
Develop valuable soft skills that enhance both your personal and professional life, and showcase your growth with a recognized certificate at the end of the course
You can ask for a recommendation letter
Always have the right to feel safe and supported, and that your work is respected
You have the right to be trained in teaching skills
You can change, amend and negotiate the class rules with your students
You don’t have to deal with every situation on your own!
Please reach out to us if you need any kind of support, regarding a student in your group who may be falling behind, technical set-up, content ideas... you name it, we are here for you!
Ask for support when needed! You find contact details here: ReDI Team
Safety Officers play a crucial role in protecting the community and ensuring that everyone feels safe, respected, and comfortable in the online environment. If you experience any situations where you feel like our community guidelines or code of conduct have been breached, or you feel uncomfortable for any reason, ask for support from the ReDI Team safety officers!
What they can do for you or our students:
Just listen if anything at ReDI is making you uncomfortable
Address complaints
Offer conflict coaching
Who to contact:
Pierluigi Delgiudice - Local Head DCP Online
Tamara Fantinato - Program Manger
Your journey as a volunteer teacher has begun! If you haven’t filled out the Volunteer Registration Form yet, we recommend doing it soon. It’s a key step to make sure you don’t miss any important info, and so we can get everything ready for your registration. It only takes 7 minutes. Don’t get left behind!
Spring Semester: Mid-December to End of January | Fall Semester: Mid-June to End of July
This friendly one-on-one interview is part of our volunteer admission process. It helps us learn about your experience, motivations, and skills, while giving you a chance to ask questions and share your expectations. We use this conversation to see if your profile, interests, and availability match our courses’ needs for the upcoming semester, ensuring a good fit so you can support students effectively.
To prepare for the call, we recommend reviewing:
The courses in your preferred track
Class format, schedules and the roles with their responsibilities
Semester timelines and key dates
Volunteer expectations and responsibilities
Your own availability
This will make the conversation smoother and more productive.
Previous teaching experience is a plus, but not required. What matters most is your availability, commitment, responsibility to the teaching team, and motivation to keep learning and share your enthusiasm with students.
Spring Semester: Mid-January to February | Fall Semester: Mid-July to August
We evaluate each profile based on the current needs of our Teaching Teams. Once your participation is confirmed, you will receive an email with the course you have been assigned to. We kindly ask you to confirm your availability as soon as possible to ensure our teams are complete.
After that, you will gain access to our Self-Onboarding process, where you’ll find all the tools, information, and materials you’ll need to facilitate your classes.
If there is no available space at the moment, we will include you on our Waiting List and consider you for future volunteer opportunities or roles within our organization.
When? Once you're admitted!
The Teacher Onboarding process includes the completion of the Self-Onboarding module. During this step, you'll gain access to our teaching tools, class materials, and important internal resources that will support you throughout the semester. You'll also receive a clear overview of your role and responsibilities as a volunteer teacher.
To confirm your participation, we’ll kindly ask you to electronically sign the Volunteer Agreement. This ensures you're officially part of the program and helps us stay aligned on expectations
This meeting marks the first time the volunteer teaching team comes together as a group.
Spring Semester: February | Fall Semester: August
The goal of this meeting is to ensure that everyone clearly understands their roles—in the classroom, within the course, and as part of the teaching team, and can collaborate effectively to provide students with the best learning experience throughout the semester.
To prepare for the session, it is recommended that you review:
The lesson content
The course structure
The roles and their responsibilities
The available tools
Reviewing these in advance will help clarify any questions or doubts from the start.
Before the meeting, please share your availability ahead of time. During this session, roles will be assigned based on your interests, experience, and availability relative to the course content.
We have allocated space for a second planning session in case it is needed.
This activity takes place during the Planning Sessions.
Spring Semester: February | Fall Semester: August
The Kick-Off is co-facilitated by the entire teaching team—not just one teacher—highlighting a supportive, team-based approach. This collaborative format ensures shared responsibility and gives all teachers first-hand experience with session facilitation. It also helps foster stronger connection with students from the very beginning.
During the Planning Session, we will start the Kick-Off Preparation, assigning roles together as a team. By that time, the agenda will already be prepared, and you can find both the Kick-Off agenda and the slides to be used in your Course Sheet.
To get ready:
Discuss Roles During the Planning Session: Each teacher will take responsibility for a segment of the Kick-Off.
Sign Up in Your Course Sheet: Confirm your participation by adding your name to the Kick-Off agenda.
Prepare Your Segment: Review and update the materials and tools for your assigned part, and be ready to lead it during the session.
We will provide you with pre-made materials to inspire you, but you are responsible for updating and adapting your part of the session.
Feel free to bring your creativity and use any additional materials that align with your teaching style and make you feel more comfortable.
The student interview is the final step in the application process to become a ReDI student.
Spring Semester: Late February | Fall Semester: Late August
Student Admission Process:
Prework
Application
Interview
Acceptance
As part of your volunteer teacher experience, we invite you to support this process by helping us interview prospective students.
The goal of the interview is to:
Get to know the applicants personally
Ensure they have enough time to commit to the course
Check their understanding of the course content
Understand their motivation to join ReDI
You help select students who are genuinely motivated and aligned with the course goals
Your involvement increases the likelihood of having committed and engaged students, which leads to a more dynamic and rewarding class experience
You gain early insight into your students' backgrounds, goals, and needs
You support ReDI’s mission to provide equal access to tech education by helping ensure a fair and thoughtful selection process
We aim to ensure the best match between the students’ skills and motivation and the course level. Based on your evaluation, we may recommend:
The course you’re teaching
A more basic or more advanced course
A different track if it suits the student better
These interviews are not exams and not professional job interviews. They are informal conversations designed to get to know the students better. We aim for a relaxed and welcoming environment while keeping a professional tone.
The interviews should reflect ReDI’s values of inclusivity, collaboration, and empowerment. Keep the conversation natural and friendly to help applicants feel comfortable and open to sharing.
Ask about their motivation and previous experience in a way that shows empathy and genuine interest. This first contact sets the tone for their ReDI experience — let’s make it a positive one.
You won’t be doing this alone. ReDI will provide:
A guideline for the interview process
A set of questions you can use as a structure
Support in case you have doubts or special situations
We want to make the process smooth and meaningful for both you and the students.
Interview Preparation
You will receive the information on this page, as well as the interview form for your course along with your calendar invite for the interviews. Please accept or decline the invitation to confirm your attendance so we can plan accordingly.
A non mandatory 30-minute briefing will also be held on interview day to review the process and address any questions before we start.
On Interview day
Join the Zoom call from your calendar invite.
The ReDI Team will welcome you and assign you to a breakout room.
A max of 6 students will be sent to you one at a time for 1:1 interviews (20 minutes total):
15 minutes conversation
5 minutes for notes and recommendation
A dedicated Slack channel will be set up for real-time communication throughout the interviews and breakout sessions. Once you complete an interview, notify the team on Slack, and the next student will be sent your way.
Spring Semester: Early March | Fall Semester: Early September
Here you’ll find materials generously shared by our trainers, who have offered their time pro bono to support the ReDI volunteer community. These resources have been thoughtfully designed and adapted to support you in your role as a teacher. We hope you find them helpful. If you're interested in exploring specific topics or would like to connect with a trainer for future semesters, feel free to reach out to us at dcp-volunteering@redi-school.org.
This engaging session covers essential topics such as teamwork, leadership, inclusion, and practical techniques to turn classroom diversity into a strength.
Training by Alejandro Reyes Alpízar, tailored specifically for ReDI's volunteer teachers.
It will equip you with valuable skills for leading groups effectively, fostering collaboration, and creating safe spaces for open discussion. You’ll learn strategies to enhance communication and promote shared responsibility within your classroom.
Additionally, you'll explore how to build trust, motivate your team, and use tools to strengthen group cohesion. Through empathy-driven approaches, you’ll gain insights on how to support both yourself and your students, fostering a more inclusive and compassionate learning environment.
Finally, the session offers techniques to appreciate and leverage the diversity of perspectives in your classroom, helping you lead inclusive sessions that inspire active participation, mutual respect, and a strong sense of belonging.
This training covers strategies to reduce Teacher Talking Time (TTT) and create learner-centered classrooms, focusing on student engagement, maximizing participation, and effectively using silence.
This session is designed to help you reduce teacher talk, build student-centered classrooms, and encourage student autonomy. With Carla Montrucchio 's vast experience in teacher training, online education, and language learning, she will share effective techniques to engage students actively and minimize unnecessary explanations.
Throughout this interactive session, you will discover practical strategies and hands-on activities to develop a classroom focused on student learning. You’ll learn how to design lessons that promote participation and assess comprehension without over-explaining. We will also cover when teacher input is most valuable and how to use intentional silence to give students time to think, process, and respond meaningfully.
Ultimately, the goal is to empower you to create an environment where students become more engaged and independent, resulting in a dynamic and inclusive classroom.
This session, designed for ReDI’s volunteer teachers, you'll explore effective strategies for giving and receiving feedback and creating a constructive feedback culture.
Through real scenarios from your own experiences, you'll learn how to deliver clear, supportive, and effective feedback. You'll also develop skills to receive feedback openly, process it constructively, and turn it into meaningful improvements—feedback that truly works!
Don’t miss this opportunity to enhance collaboration, improve communication, and create a more supportive and productive environment!
This is the first time students and teachers have come together as a group!
Spring Semester: Mid | Fall Semester: August
In this first session, we welcome the students, establish the tone for the semester, foster trust, and introduce the learning path ahead.
Create a welcoming and inclusive atmosphere
Get to know each other
Introduce the teaching team and assign responsibilities
Present the course structure and tools
Welcome & Ice Breaker Set a positive, friendly tone to help students feel comfortable.
Teacher Introductions Present yourselves as a united teaching team, emphasizing collaboration and mutual support.
Course Overview Briefly explain the course structure, timeline, key tools (like Visual Studio Code, Git, GitHub, etc.), and what students can expect after completing the course—such as potential roles and job opportunities.
Team/Class Building Activity (Working Alliance) Build trust and co-create class norms with students to establish a supportive environment.
Check-Out Question Encourage reflection and ensure everyone has a chance to speak before closing the session.
Feedback Request Collect early impressions and suggestions to enhance the learning experience.
Spring & Fall Semester: During the semester. Dates will be included on the course sheet.
The ReDI team will meet with the students to collect feedback on the course as well as suggestions from the students. The session is moderate entirely by the ReDI team and results are brought to the teaching team at the teachers' touchpoint.
These activities are managed by the Talent Success Team. We believe it’s important that you know and understand all the services the organization offers during the semester.
Spring & Fall Semester: During the semester. Dates will be included on the course sheet.
Career Week: Regular Courses & Circles The Career Week at ReDI School is a week of training webinars designed to help students connect with industry professionals, improve job-related skills, explore career opportunities, and boost their job readiness. More info: [Career Services]
✅ Students need to attend at least 2 career events during the semester (within or outside Career Week) in order to graduate. Students can choose the topics that interest them most. ✅ Other career events during the semester might include company visits, networking opportunities, and mentoring matching events. During Career Week, regular classes are on hold. We use this time to organize teaching team touchpoints.
Career Bootcamp: UX/UI & Full Stack Bootcamp We are currently adapting the format of the Final Career Project, which will take place in the final weeks of the Bootcamp—after your regular classes have ended. These weeks are already marked in your course sheet. More information will be shared with you soon!
The Teacher Touchpoint is a mid-semester session designed to bring the teaching team together in a collaborative and reflective space.
Spring & Fall Semester: During the semester. Dates will be included on the course sheet.
During the session:
Feedback Session
We’ll review student feedback and reflect on your teaching experience so far.
We’ll hold a collaborative retrospective where you can share your thoughts on volunteering — including suggestions to improve content, classroom dynamics, team collaboration, and ways the ReDI Team can better support you this semester and beyond.
Finally, we’ll prioritize improvement ideas and explore potential solutions together.
This is also a great opportunity to celebrate successes and exchange ideas to enhance the learning experience for everyone.
Project Phase & Demo Day Presentations
For some courses, we’ll outline the key topics and guidelines expected to be addressed in the final project phase.
We’ll discuss the format and expectations for the Demo Day presentations.
Availability & Role Assignments
We’ll check your availability for the second half of the semester and assign roles for upcoming and final sessions, so please add your availability in advance!
The hands-on period is where students apply their learning by building real-world projects.
Spring & Fall Semester: Date will be included on the course sheet
This phase takes place toward the end of the Beginners and Intermediate courses and is designed to help learners gain practical experience and build a strong portfolio. It also supports their growth in key areas such as:
🔹 Team Collaboration – Work with peers in a team setting, simulating real-world work environments. 🔹 Hands-on Learning – Apply coding, design, or data skills to solve real-life challenges. 🔹 Mentor Support – Receive guidance from teachers on realistic case scenarios. 🔹 Final Presentation – Present their project to classmates, mentors, and sometimes even industry professionals.
It’s a valuable step in boosting learners’ confidence, teamwork, and job-readiness.
The Class Demo Day is an internal presentation day held in the final week of the course. Each student (team) presents their project to their classmates and teachers. It’s a supportive environment focused on:
Showcasing the project
Practicing technical presentations
Sharing challenges and lessons learned
Celebrating the team’s work
🧑🏫 This day helps students build confidence and receive feedback from peers and instructors.
The Demo Day is a public, on-site event where selected student teams present their projects to the broader ReDI community, including partners.
The event highlights excellence, creativity, and collaboration
Students present in a more formal setting with networking opportunities
It’s a moment of celebration and recognition for everyone involved
📌 Attendance and presentation at the Class Demo Day are required for students to receive a certificate.
To help learners prepare their pitch, here’s a suggested format:
Length: Max. 5 minutes
Mode: Slides or Live Demonstration
Proposed Structure:
Intro – What’s the project, and what problem does it solve?
Demo – Show the live website
Challenges & Learning – What went well? What was hard? What did you learn?
🧑🏫 Encourage learners to rehearse and help each other practice!
To receive a ReDI certificate, learners must:
Attend at least 80% of the course
Complete and present the Project
Attend the Internal Class Demo Day
💬 “We grow by doing, and by helping each other.”
Foster a positive, collaborative learning
Dedicate class time to mentoring, code reviews, and feedback
Celebrate all wins—big or small—as students build real web apps
🎉 Let’s end the semester by cheering each other on!
Local Community Events at ReDI School are informal gatherings where students, alumni, mentors, and industry professionals come together to network and share quality time. These events help you connect with the tech community in your city (Berlin, Hamburg, or NRW). We’ll organize two community events per location this semester.
If you’re not yet included in our community channels and want to stay informed about upcoming events, please let us know so we can invite you based on your preferred location.
Link: The link to your Course Sheet is pinned in Slack.
Course Management: We use the Course Sheet to organize the course.
Availability & Ownership: Volunteers assign themselves to the session. They show when they are available to teach.
Feedback: Bootcamps & Circles have a feedback tab where we collect feedback about the session.
Mark it in the Course Sheet so that others can see it and let your team knows in your teaching team communication channel
We use Slack as our primary communication platform—both with your teaching team and with students. You’ll automatically be added to your teaching team channel and your student channel. Additionally, you're welcome to join our community channels in Berlin, NRW, and Hamburg to stay updated on local events and news.
Please make sure to check Slack regularly during the semester and use it to communicate with your team—especially if you’re unable to make it to a session.
We encourage you to not only use Slack for logistics or emergencies, but also to share materials, ideas, and good vibes with your team. A supportive and communicative environment makes a big difference!
After every session, a Slackbot will be released in your teaching channel. One designated team member should fill it in to ensure a smooth handover for the next session.
The Slackbot will ask:
How was the session? (What went well? Any ideas for improvement?)
Any follow-ups needed for the next session?
Did the team you supported have any recurring questions?
Anything else to share?
Additional feedback
⚠️ This is really important to help the next team come prepared. Be empathetic—imagine stepping into a class without knowing what happened before!
Zoom? It is our video conferencing tool for the classes.
Zoom Link: You find it pinned in Slack. The Zoom link is the same for the whole semester.
Use the App: Install the Zoom app for all functionality.
Recordings: We record the session. More: Recordings
Claim Host: Credentials are pinned in Slack. How to Join Zoom & Claim Host
Join early? The Zoom call opens 45 min ahead of time. Feel free to join early.
Find the link to the class meeting either in your calendar invite for the session or pinned in the teachers slack channel. Join with one click
Go to the participants list and “Claim host”. Sign in with the host key to become the host. You can find the host key (a series of 6 numbers) pinned in the teacher Slack channel.
Please make your co-teachers for the sessions co-hosts by right-clicking on their name from the participants list.
Please do not forget to record the class. We record only Input and Q&A Sessions.
Recordings automatically save into a drive students have access to as viewers. This Drive is pinned to the students slack channel. Recordings are available for whole semester. Break out rooms cannot be recorded.
When starting the meeting, audio is off, your video is off and recording is off.
Hosts are allowed to add co-hosts.
Possibility to send files via meeting chat.
Link: Attendance Tracker
Who: The teaching assistant tracks attendance
When: Every regular class (usually 20 minutes into the session)
Access: Credentials are pinned in your teaching teams' Slack channel
We ask learners to join at least 80% of the sessions to obtain a certificate. We believe students can only learn if they attend. That's why attendance tracking is essential. ReDI follows up regularly with students with low attendance to offer support.
100% – Present: Arrive on time, actively participate, and keep the camera on.
50% – Excused: Notify in advance if unable to attend
50% – Late: Arrival more than 15 minutes late. Please mark as "Excused". If no excuse is known, select "Other." No explanation from students is required.
50% – Early Leave: Leaving before the break. Please mark as "Excused". If no excuse is known, select "Other." No explanation from students is required.
0% – Absent: No prior communication of absence
Students will only be marked as "present", if they join the class with their camera on.
If a student should experience internet connection problems during the class, they should either write it in the chat or unmute themselves to inform teachers and fellow students. If this is not possible, students should inform the class through a message in their students slack channel.
Link: The link to your classroom is pinned in Slack.
Purpose: We use Google Classroom as our learning platform. We use it for two functions: Sharing material with the students and reviewing projects. You can also use it to create material.
Google Drive: Your Google Classroom is connected to a Google Drive where material is stored.
Calendar: Students are invited to the sessions through the calendar from the classroom
Go to Classwork. Go to Create. Select material to upload material, which is shared with the students. Select Topic to create a new section that can hold multiple materials.
Go to the Grades section. You find all the students; you can see who turned in the homework. Once you click on it, you can review their work, write a comment, and return it.
You should have received an email invitation from ReDI. Please check your emails and spam folder. Otherwise, please get in touch with the ReDI team via Slack.
We provide additional tools that you can use to engage students more in your sessions! At ReDI, we like to use the following tools and icebreakers:
Create live polls, word clouds, and Q&A
Perfect for:
Icebreakers: Ask students about their expectations or background knowledge.
Quick polls: Check understanding of a topic in real-time.
Exit tickets: Gather feedback at the end of a session.
Login credentials in teachers' Slack channel
Quiz-based learning with competitive elements
Perfect for Revision & Recaps - You create a quiz, and students participate live in class via browser or cell phone.
Login credentials in teachers' Slack channel
You can use quick icebreakers at the start of your sessions to energize participants, build connections, and create an engaging and interactive learning environment. Here is a list of icebreakers. They shouldn't take more than 5 minutes to run.
Description: Participants share three statements about themselves—two true and one false. The group has to guess which one is the lie.
How to Run: Use breakout rooms for smaller groups or let everyone participate in the main room.
Objective: Participants get to know each other in a fun way.
Description: Give participants a list of items to find in their home within 1-2 minutes (e.g., something red, something that makes noise).
How to Run: Ask them to bring the items back to the camera and share a quick story about one of them.
Objective: The activity is an energizer.
Description: Pose a question or statement (e.g., "How are you feeling about today’s session?") and ask participants to respond using emojis only.
How to Run: Use the chat in Zoom.
Objective: It is an easy way for participants to share how they are doing.
Here's an overview of the key tools we use for teaching and communication. Please set up these tools now to ensure effective collaboration with your team and students.
This is our main communication tool, both with teachers and with the students. You'll have access by default to your teaching team channel and the students' channel. Additionally, you can join our community channels in Berlin, NRW, and Hamburg to learn about local events. Please check Slack regularly during the semester and communicate with your teaching team via Slack if you cannot make it to class.
We use Google Calendar to send semester meeting appointments to teachers and students.
Our online sessions are running on Zoom. We highly recommend installing and updating the Zoom app on your device, as the online version doesn't cover all functionalities. Please note: The class Zoom link is the same for the entire semester.
We use Google Classroom to share material with the students and to collect and give feedback to projects and homework.
We use the Course Sheet as a tool for managing our teaching sessions, assigning roles according to the topics to be taught and the team's availability. In some courses, we also collect feedback about the students and the sessions.
Please complete all steps before going to the next section of the self-onboarding. If you face any issues, please reach out to the ReDI team via E-Mail or Slack. Once you are done, go to the next step to get your volunteer agreement!
Please complete this step to receive your Volunteer Agreement. Once signed, your onboarding will be complete!
Are you new to this course: Course Overview
Start your Onboarding: Get Started
Leads regular classes, introduces new concepts
Manages Zoom logistics and supports students during classes
Provides emergency coverage when regular teachers are unavailable
Tuesday 19:00-21:00
Thursday 19:00-21:00
New concepts introduced with theory and practice
Find out more about ReDI: About ReDI
Find out about the career services ReDI offers: Career Services
Check out: I can't teach tonight, I am dropping out, I feel uncomfortable.
Reach out to Sevval, your Course Manager, for help via Slack.
❤️ Thank you for supporting the ReDI students ❤️
Welcome to ReDI School! We really appreciate that you are part of our community. In this page, you'll find an overview of the course. By volunteering, you contribute to our main goal: help our students gain the necessary skills to find a job in tech. ReDI School has now helped over 17.000 people advance their tech skills. This is only possible with the support of our volunteers <3
Our student community brings together people from over 138 countries. Your course won't be different. Your students will come from a wide range of countries. They also come from diverse professional backgrounds - some are currently unemployed or underemployed, while others are students looking to prepare for their careers. With an average age of 32, many of our students hold a university degree and have several years of work experience. What unites all students is their passion for technology and their aim to build a career in the tech industry.
❤️ Thank you for supporting our students as they take another step in their journey! To learn more about ReDI students and our community, visit About ReDI School.
Two sessions during the course will take place on a hybrid format - students in Hamburg will have a session on site, while the other students a parallel session online. We are organizing on-site activities in our three main locations. Find out more below.
We invite you to four on-site community events throughout the semester if you are located in Berlin and the surrounding. The Onboarding will also take place in person in Berlin. You are more than welcome to join!
We invite you to four on-site community events throughout the semester if you are located in Berlin and surrounding. The Onboarding and Demo Day will also take place in person in Düsseldorf. You are more than welcome to join!
Four in-person sessions are taking place in Hamburg: Onboarding, two regular course sessions, and Demo Day. If you are based in Hamburg, it would be fantastic if you could support the course in one or more of these sessions.
We hope that by reading this, you have a better idea of the course and what it means to volunteer at ReDI. Let's explore the Timeline now 📅.
Our HTML&CSS Course is project-based - students learn by working on hands-on projects. Each project is broken into weekly milestones.
Thursday: Introduce new concepts and the next milestone
Thursday - Tuesdays: Students work on their milestone
Tuesdays: Students present their milestones in the Coaching Session
Lessons
In the GitHub repo, you find in every milestone folder a lesson.md
for each week. It contains guidelines on how to teach the session.
Student Hub
Student-facing documentation, tutorials, and concept explanations. Students use this as their main reference.
Regular Class
Use lesson.md
to teach new concepts. The file explains how to approach the session, what topics to cover, and how you can introduce the concepts with an example. You find the lesson.md files in the respective milestone folders in GitHub.
At the end of each Regular Class, we introduce the students to the next milestone (what students work on until next Tuesday). Milestone README.md
outlines the next project milestone.
We have additional resources from previous semesters, including slide decks, exercises, etc., linked in Course Content.
Further explanations and resources are shared with the students via the Student Hub.
Coaching Session
No teaching is needed. Focused on reviewing student work and providing feedback.
Reviewing the milestoneREADME.md
t helps to understand what the milestone contains students are working on.
GitHub: You can find all files in our GitHub Repo. Do you see the lessons and teacher guides?
Additional Material: Check out prior slide decks and exercises here Course Content
Student Hub: The student hub is the "knowledge base" for the students where they find extra resources about the concepts being covered in the course. It is currently under construction. We will share it with you soon!
You are free to change the material as you like! If you believe slides are needed to explain a concept, do it! If you would explain a concept differently, go for it.
We know the material is not perfect! For sure, parts are not so clear and can be improved. Please help us to improve it further! If something is unclear or missing - feel free to add it! Thanks to your contribution, we can improve the material in the future!
Prior Material?
If you taught in the past semester at ReDI, you might have existing material you would like to reuse. That is fantastic! Let's update the repository for this course with your material. Please add the content in the repo in the right milestone. If you have Google Slides, please link them to the lesson or teacher guide files. You can also reach out to us on Slack or via email (dcp@redi-school.org) for further questions on how to add or use prior material.
We share several best practices in the Course Content section. For example, the concept of "How little is enough?" or the "I Do, We Do, You Do" methodology. In the end, it is your decision how you want to teach it. We recommend to browse through the concepts before teaching a session: Course Content.
That was a lot of content! Thanks for staying with us. Let's complete the self-onboarding in the next page: Self-Onboarding.
Looking for more material? Maybe check out GitHub Repo from the Berlin HTML & CSS Course.
Prior Material? If you taught in the past semester at ReDI, you might have existing material you would like to reuse. That is fantastic! Add it to our Google Drive.
The "I Do, We Do, You Do" method is a teaching method designed to help students learn new concepts by first observing, then practicing with guidance, and finally working independently.
I Do: The teacher demonstrates the task while explaining the steps and thought process aloud. This stage is about modeling the correct way to approach the task and highlighting key concepts and techniques.
We Do: The session owner walks the students through an activity. The students follow along (code or design along). This collaborative stage allows students to apply what they've seen with support, ask questions, and receive immediate feedback.
You Do: Students work independently on the task. This stage allows them to practice the skill on their own.
Example: Introducing Javascript
I Do: The teacher introduces JavaScript and demonstrates a simple script that shows an alert when clicking a button. Key concepts like variables, functions, and events are explained briefly.
We Do: The teacher walks the students through creating a function that changes a heading's color when clicking a button. The students follow and code along. The teacher shares their screen and gives the students time to code along. Together, the teacher and the students write the function, select the element, and add an event listener, with the teacher guiding and asking questions to engage students.
You Do: Students independently write JavaScript to change the text of a paragraph when a button is clicked in a breakout room. They practice using variables, functions, and event listeners and then share their work for feedback.
Context before content - We experienced that explaining why a concept is important helps a lot in understanding what the concept is about. Why should you learn this concept? Try to give the context. Maybe explain where you use it in your daily work life. Or explain how this concept can help to solve a bigger problem
Engage with Students: Ask questions to check understanding. Use their names and keep the tone friendly and encouraging.
Be Prepared but Flexible: Have a plan but adapt based on student needs.
Feedback is Key: Provide constructive feedback to help students improve. Celebrate small wins to keep motivation high.
Ice Breakers and Energizers - Do you want to start the session with an energizer? Have a look at Class Engagement
Homework is given every Thursday session via Google Classroom
The Session Owner of the Thursday session prepares the homework
Students have until the following Tuesday session to complete the homework
The Homework Reviewer reviews their homework from Tuesday until Thursday
Homework is not graded. The goal is for students to learn by working on their homework. If it is not complete or perfect, it’s okay. We ask students to complete at least 80% of the homework.
Learning by Doing - Through homework, students practice and code more. The more they practice, the better the students get!
Students try out the concepts in homework. The review helps students to know if they are on track.
By reviewing the homework, we might better understand which concepts need further elaboration.
1. Create Homework
Session Owner creates homework.
2. Add to Google Classroom
Session Owner creates a homework assignment in Google Classroom at least 1 day before class. Template.
3. Present Homework in Class
Session Owner presents the homework assignment on Thursday
4. Students hand in homework
Students hand in the homework until the start of the next session (Tuesday)
5. Show solution
Session Owner shows the solution of the homework in the Tuesday session
6. Teachers review homework
Homework Reviewer reviews submissions until Thursday
Focus the homework on one achievable, practical problem. That means:
Give only one problem, not multiple, it would overwhelm and lower chances of completion.
Achievable - make it equally hard or slightly harder than the last practice exercise in class. Make it feasible in terms of the time required. If you need 5 minutes to solve it, it will probably take the students 30 minutes or longer. Don’t go over 5min for yourself.
Optional - to accommodate the more advanced students in the class, you can add optional extra questions.
Go to Google Classroom, Go to Create, and select Assignment.
Give title, instructions and set the due date to the next session on Tuesday (template).
Support: Video for Google Classroom.
The Final Project is the highlight of the semester and an essential part of the learning journey at ReDI. During this phase, learners apply the skills they’ve developed to create a personal or team project that showcases their knowledge in HTML & CSS.
The project phase begins after the core curriculum is completed.
Learners will:
Work individually or in small groups (up to 3 people)
Choose their own project topic with teacher guidance
Build a working website or feature relevant to the course
💡 Goal: Apply the concepts learned in class in a hands-on, creative project
Each project must include:
A code-based solution using HTML & CSS
A presentation and a live demo (showing a working website)
Students choose their own project topic with teacher guidance. Project types may include:
A personal website
A thematic landing page
A community-focused mini project
Anything aligned with the course content and realistic for the timeframe
Project Launch
Thursday, May 22
We introduce students to the project phase
Class Demo Day
Tuesday, June 17
All learners present to their class. One project will be selected for the official Demo Day.
Demo Day
Date to be confirmed.
Selected projects from each course are showcased to the full ReDI community. We aim to run an on-site Demo Day in each location.
📌 Attendance and presentation in the Class Demo Day are required for students to receive a certificate.
To help learners prepare their pitch, here’s a suggested format:
Length: Max. 5 minutes
Mode: Slides or Live Demonstration
Proposed Structure:
Intro – What’s the project, and what problem does it solve?
Demo – Show the live website
Challenges & Learning – What went well? What was hard? What did you learn?
🧑🏫 Encourage learners to rehearse and help each other practice!
To receive a ReDI certificate, learners must:
Attend at least 80% of the course
Participate in 2 Career Workshops
Complete and present a Final Project
Attend the Internal Demo Day
Complete 2 IBM SkillsBuild Courses
💬 “We grow by doing, and by helping each other.”
Encourage a supportive, collaborative learning environment.
Foster confidence through feedback.
Use class time for project work, check-ins, and guidance.
Let’s celebrate the end of the semester together 🎉
As a session owner, you lead the weekly Regular Class, introducing key concepts and guiding students through exercises. You can use prepared materials. However, you have the freedom to adapt them to your teaching style.
Review previous class feedback in Slack
Review material and test coding exercises (Course Content)
Coordinate with the teaching assistant
Add material to Google Classroom (24h before) (how to use Google Classroom")
Prepare Homework (for Thursday Sessions)
Join as co-host (5 min early)
Previous content recap (10 min)
Introduce key concepts with live coding and or exercises (45 min)
Hands-on practice (45 min)
Introduce next milestone (10 min)
Head over to the: Course Content
As a session assistant, you provide technical and administrative support during Regular Classes. You open the Zoom call, track attendance, help answer questions, and provide support in break-out rooms.
Technical setup and support
Student attendance tracking
Question moderation
Breakout room management
Before Class:
Coordinate with the session owner
Review class content
During Class:
Join Zoom Call (link pinned in Slack and Google Calendar)
Claim the host (host key pinned in Slack)
Make the Session Owner co-host on Zoom (safety measure)
Start cloud recording
Monitor student questions
Support breakout activities
Track attendance
After Class:
Share feedback on the class and student engagement in the Slack handover bot for team visibility
All essential links (attendance tracker, Zoom) are bookmarked in Slack.
Backup teachers provide emergency coverage when teachers cannot attend class. No session attendance is required unless called upon.
Absent teacher posts in #teachers Slack channel and tags @backup teacher
Backup teacher confirms availability
Role assignment:
If assistant is absent: Backup becomes assistant
If lead is absent: Assistant becomes lead, backup becomes assistant
The homework reviewer reviews the homework submissions of the students.
More about Homework
Homework are reviewed from Google Classroom. Students submissions land under the "Grades" section. Just click on the submission link and add comments for review via the chat function. Everything be kept private and only visible to the reviewer and the students themselves.
Positivity - It can happen easily that feedback only points out the mistakes, but it’s important to give positive feedback as well. Commenting on aspects that you liked about the code is crucial to make the students more confident. We also learn from what we did well.
Specific - Try to make your feedback as specific as possible so the students know which part of the code needs improvement.
Suggestions - Good feedback contains suggestions for improvement. This way, the students will have ideas on how to improve the code, and you will push them in the right direction. Keep in mind the balance between suggestions and self-study; giving away the solution is not always the best thing to do.
Weekly class where students learn new concepts and get introduced to their next project milestone.
When: Thursdays, 19:00 - 21:00
Where: Zoom (link in Slack)
Team: Session Owner leads the session and Session Assist supports
Review previous content
Introduce weekly milestone
Present new concepts
Guided practice ("We Do")
Group practice in breakout rooms ("You Do")
Get Started
Are you new to this course: Course Overview
Start your Onboarding: Get Started
Leads regular classes, introduces new concepts and practices it with the students. Creates the homework.
Manages Zoom logistics and supports students during classes
Provides emergency coverage when regular teachers are unavailable
Find out more about ReDI: About ReDI
Find out about the career services ReDI offers: Career Services
Check out: I can't teach tonight, I am dropping out, I feel uncomfortable.
Reach out to Abdullah, your Course Manager, for help via Slack.
❤️ Thank you for supporting the ReDI students ❤️
Welcome to ReDI School! We really appreciate that you are part of our community. In this page, you'll find an overview of the course. By volunteering, you contribute to our main goal: help our students gain the necessary skills to find a job in tech. ReDI School has now helped over 17.000 people advance their tech skills. This is only possible with the support of our volunteers <3
Our student community brings together people from over 138 countries. Your course won't be different. Your students will come from a wide range of countries. They also come from diverse professional backgrounds - some are currently unemployed or underemployed, while others are students looking to prepare for their careers. With an average age of 32, many of our students hold a university degree and have several years of work experience. What unites all students is their passion for technology and their aim to build a career in the tech industry.
❤️ Thank you for supporting our students as they take another step in their journey! To learn more about ReDI students and our community, visit About ReDI School.
The JavaScript Course is a 14-week program designed to build upon HTML & CSS skills, introducing students to interactive web development using JavaScript. Each cohort consists of 25 students who meet twice a week (Tuesdays and Thursdays from 19:00-21:00).
The weekly schedule consists of two regular classes. Tuesday begins with a review of the previous week’s content. Students participate in live coding exercises and problem-solving activities. Homework from the previous week is discussed and feedback is provided. On Thursday, teachers introduce new concepts. Students engage in hands-on coding demonstrations and guided exercises. The session concludes with the assignment of the weekly homework task.
Between sessions, students are expected to dedicate 10-12 hours per week to coding assignments, and independent study.
We aim to give homework each Thursday. We ask students to complete the homework by next Tuesday (before the session starts). The homework reviewer corrects the homework and returns it to the students via Google Classroom.
The course has two online sessions per week. For on-site events, check out On-site Activities. The session format differs from what you might have seen before.
Tuesday 19:00-21:00
This regular class is taught in pairs, with one person assigned as a session owner (the lecturer) and one as a teaching assistant. The class introduces the students to the new topic.
Session Owner, Session Assist
Thursday 19:00 - 21:00
This regular class is taught in pairs, with one person assigned as a session owner (the lecturer) and one as a teaching assistant. The class introduces the students to the new topic.
Session Owner, Session Assist
As a session owner, you lead the Regular Class. You prepare the session and coordinate with the teaching assistant.
4 hours per week
As a teaching assistant, you support the session owner in the input session. You open the Zoom call, track attendance, help answer questions, and provide support in break-out rooms.
3 hours per week
As a backup teacher, you are available and ready to jump in the case one of the teachers assigned for the day should have issues, or get sick. As a backup teacher, you don’t need to attend the session unless an emergency arises.
2 hours per week
Two sessions during the course will take place on a hybrid format - students in Hamburg will have a session on site, while the other students a parallel session online. We are organizing on-site activities in our three main locations. Find out more below.
We invite you to four on-site community events throughout the semester if you are located in Berlin and the surrounding. The Onboarding will also take place in person in Berlin. You are more than welcome to join!
We invite you to four on-site community events throughout the semester if you are located in Berlin and surrounding. The Onboarding and Demo Day will also take place in person in Düsseldorf. You are more than welcome to join!
Four in-person sessions are taking place in Hamburg: Onboarding, two regular course sessions, and Demo Day. If you are based in Hamburg, it would be fantastic if you could support the course in one or more of these sessions.
We hope that by reading this, you have a better idea of the course and what it means to volunteer at ReDI. Let's explore the Timeline now 📅.
GitHub: All files are in our GitHub Repo. Have you seen the lessons and teacher guides?
You are free to change the material as you like! If you believe slides are needed to explain a concept, do it! If you would explain a concept differently, go for it.
We share several best practices in the Course Content section. For example, the concept of "How little is enough?" or the "I Do, We Do, You Do" methodology. In the end, it is your decision how you want to teach it. We recommend to browse through the concepts before teaching a session: Course Content.
That was a lot of content! Thanks for staying with us. Let's complete the self-onboarding in the next page: Complete your Self-Onboarding
GitHub - Request access to the GitHub repo. Update the slide deck for your session through a pull request.
If you find good material, ReDI could use, and if you have feedback or further ideas, feel free to contact us via Slack or email dcp@redi-school.org).
The "I Do, We Do, You Do" method is a teaching method designed to help students learn new concepts by first observing, then practicing with guidance, and finally working independently.
I Do: The teacher demonstrates the task while explaining the steps and thought process aloud. This stage is about modeling the correct way to approach the task and highlighting key concepts and techniques.
We Do: The session owner walks the students through an activity. The students follow along (code or design along). This collaborative stage allows students to apply what they've seen with support, ask questions, and receive immediate feedback.
You Do: Students work independently on the task. This stage allows them to practice the skill on their own.
Example: Introducing Javascript
I Do: The teacher introduces JavaScript and demonstrates a simple script that shows an alert when clicking a button. Key concepts like variables, functions, and events are explained briefly.
We Do: The teacher walks the students through creating a function that changes a heading's color when clicking a button. The students follow and code along. The teacher shares their screen and gives the students time to code along. Together, the teacher and the students write the function, select the element, and add an event listener, with the teacher guiding and asking questions to engage students.
You Do: Students independently write JavaScript to change the text of a paragraph when a button is clicked in a breakout room. They practice using variables, functions, and event listeners and then share their work for feedback.
Context before content - We experienced that explaining why a concept is important helps a lot in understanding what the concept is about. Why should you learn this concept? Try to give the context. Maybe explain where you use it in your daily work life. Or explain how this concept can help to solve a bigger problem
Engage with Students: Ask questions to check understanding. Use their names and keep the tone friendly and encouraging.
Be Prepared but Flexible: Have a plan but adapt based on student needs.
Feedback is Key: Provide constructive feedback to help students improve. Celebrate small wins to keep motivation high.
Watch this video on how to run the Regular Class.
Student Gitbook (LINK)
Ice Breakers and Energizers - Do you want to start the session with an energizer? Have a look at Class Engagement
Homework is given every Thursday session via Google Classroom
The Session Owner of the Thursday session prepares the homework
Students have until the following Tuesday session to complete the homework
The Homework Reviewer reviews their homework from Tuesday until Thursday
Homework is not graded. The goal is for students to learn by working on their homework. If it is not complete or perfect, it’s okay. We ask students to complete at least 80% of the homework.
Learning by Doing - Through homework, students practice and code more. The more they practice, the better the students get!
Students try out the concepts in homework. The review helps students to know if they are on track.
By reviewing the homework, we might better understand which concepts need further elaboration.
1. Create Homework
Session Owner creates homework.
2. Add to Google Classroom
Session Owner creates a homework assignment in Google Classroom at least 1 day before class. Template.
3. Present Homework in Class
Session Owner presents the homework assignment on Thursday
4. Students hand in homework
Students hand in the homework until the start of the next session (Tuesday)
5. Show solution
Session Owner shows the solution of the homework in the Tuesday session
6. Teachers review homework
Homework Reviewer reviews submissions until Thursday
Focus the homework on one achievable, practical problem. That means:
Give only one problem, not multiple, it would overwhelm and lower chances of completion.
Achievable - make it equally hard or slightly harder than the last practice exercise in class. Make it feasible in terms of the time required. If you need 5 minutes to solve it, it will probably take the students 30 minutes or longer. Don’t go over 5min for yourself.
Optional - to accommodate the more advanced students in the class, you can add optional extra questions.
Go to Google Classroom, Go to Create, and select Assignment.
Give title, instructions and set the due date to the next session on Tuesday (template).
Support: Video for Google Classroom.
The Final Project is the highlight of the semester and an essential part of the learning journey at ReDI. During this phase, learners apply the skills they’ve developed to create a personal or team project that showcases their knowledge in JavaScript.
The project phase begins after the core curriculum is completed.
Learners will:
Work individually or in small groups (up to 3 people)
Choose their own project topic with teacher guidance
Build a working web app or website
💡 Goal: Apply the concepts learned in class in a hands-on, creative project
Each project must include:
A code-based solution using JavaScript
A presentation and a live demo (showing a working web app or website with interactivity)
Students choose their own project topic with teacher guidance. Project types may include:
A quiz or trivia game
A to-do list or productivity tool
An interactive landing page or form
A weather or news app using APIs
Anything aligned with the course content and realistic for the timeframe
Need inspiration? Check out these projects from previous semesters:
Project Launch
Tuesday, June 3
We introduce students to the project phase
Class Demo Day
Tuesday, June 17
All learners present to their class. One project will be selected for the official Demo Day.
Demo Day
Date to be confirmed.
Selected projects from each course are showcased to the full ReDI community. We aim to run an on-site Demo Day in each location.
📌 Attendance and presentation in the Class Demo Day are required for students to receive a certificate.
To help learners prepare their pitch, here’s a suggested format:
Length: Max. 5 minutes
Mode: Slides or Live Demonstration
Proposed Structure:
Intro – What’s the project, and what problem does it solve?
Demo – Show the live website
Challenges & Learning – What went well? What was hard? What did you learn?
🧑🏫 Encourage learners to rehearse and help each other practice!
To receive a ReDI certificate, learners must:
Attend at least 80% of the course
Participate in 2 Career Workshops
Complete and present a Final Project
Attend the Internal Demo Day
Complete 2 IBM SkillsBuild Courses
💬 “We grow by doing, and by helping each other.”
Encourage a supportive, collaborative learning environment.
Foster confidence through feedback.
Use class time for project work, check-ins, and guidance.
Let’s celebrate the end of the semester together 🎉
Leads regular classes, introduces new concepts and practices it with the students
Manages Zoom logistics and supports students during classes
Provides emergency coverage when regular teachers are unavailable
Reviews the homework
As a session owner, you lead the weekly Regular Class, introducing key concepts and guiding students through exercises. You can use prepared materials. However, you have the freedom to adapt them to your teaching style.
Review previous class feedback in Slack
Review the slides and exercises (Course Content)
Test coding exercises
Add material to Google Classroom (24h before) (how to use Google Classroom")
Prepare Homework (for Thursday Sessions)
Join as co-host (5 min early)
Previous content recap (10 min)
Introduce key concepts with live coding and or exercises (45 min)
Hands-on practice (45 min)
Introduce next milestone (10 min)
Head over to the: Course Content
Focus on core concepts introduction
Point students to additional resources for deeper learning
Use recap weeks to cover missed content
Direct students to Q&A/support sessions for extra help
As a session assistant, you provide technical and administrative support during Regular Classes. You open the Zoom call, track attendance, help answer questions, and provide support in break-out rooms.
Technical setup and support
Student attendance tracking
Question moderation
Breakout room management
Before Class:
Coordinate with the session owner
Review class content
During Class:
Join Zoom Call (link pinned in Slack and Google Calendar)
Claim the host (host key pinned in Slack)
Make the Session Owner co-host on Zoom (safety measure)
Start cloud recording
Monitor student questions
Support breakout activities
Track attendance
After Class:
Share feedback on the class and student engagement in the Slack handover bot for team visibility
All essential links (attendance tracker, Zoom) are bookmarked in Slack.
Backup teachers provide emergency coverage when teachers cannot attend class. No session attendance is required unless called upon.
Absent teacher posts in #teachers Slack channel and tags @backup teacher
Backup teacher confirms availability
Role assignment:
If assistant is absent: Backup becomes assistant
If lead is absent: Assistant becomes lead, backup becomes assistant
The homework reviewer reviews the homework submissions of the students.
More about Homework
Homework are reviewed from Google Classroom. Students submissions land under the "Grades" section. Just click on the submission link and add comments for review via the chat function. Everything be kept private and only visible to the reviewer and the students themselves.
Positivity - It can happen easily that feedback only points out the mistakes, but it’s important to give positive feedback as well. Commenting on aspects that you liked about the code is crucial to make the students more confident. We also learn from what we did well.
Specific - Try to make your feedback as specific as possible so the students know which part of the code needs improvement.
Suggestions - Good feedback contains suggestions for improvement. This way, the students will have ideas on how to improve the code, and you will push them in the right direction. Keep in mind the balance between suggestions and self-study; giving away the solution is not always the best thing to do.
Weekly class where students learn new concepts.
When: Tuesdays and Thursdays, 19:00 - 21:00
Where: Zoom (link in Slack)
Team: Session Owner leads the session and Session Assist supports
Review previous content
Introduce weekly milestone
Present new concepts
Guided practice ("We Do")
Group practice in breakout rooms ("You Do")
New to this course: Course Overview
Start your Onboarding: Get Started
Monday 19:00-21:00
Wednesday 19:00-21:00
Thursday 19:00-21:00
Find out more about ReDI: About ReDI
Find out about the career services ReDI offers: Career Services
Check out: I can't teach tonight, I am dropping out, I feel uncomfortable.
Reach out to Sevval, your Course Manager, for help via Slack.
❤️ Thank you for supporting the ReDI students ❤️
Welcome to ReDI School! We really appreciate that you are part of our community. In this page, you'll find an overview of the course. By volunteering, you contribute to our main goal: help our students gain the necessary skills to find a job in tech. ReDI School has now helped over 17.000 people advance their tech skills. This is only possible with the support of our volunteers <3
Our student community brings together people from over 138 countries. Your course won't be different. Your students will come from a wide range of countries. They also come from diverse professional backgrounds - some are currently unemployed or underemployed, while others are students looking to prepare for their careers. With an average age of 32, many of our students hold a university degree and have several years of work experience. What unites all students is their passion for technology and their aim to build a career in the tech industry.
❤️ Thank you for supporting our students as they take another step in their journey! To learn more about ReDI students and our community, visit About ReDI School.
The Full Stack Bootcamp is an 18-week intensive program that combines 14 weeks of technical training with a 4-week career project. Each cohort consists of 25 students who progress through the program together, meeting three times per week in the evenings (Monday, Wednesday, and Thursday from 19:00-21:00). The program follows a project-based learning approach where students work through three main projects: an E-Commerce Store focusing on React basics, a Twitter Clone exploring Next.js, and a Capstone Project incorporating full stack development. Each project spans four weeks and includes weekly milestones and a recap week for review.
The weekly schedule includes three distinct session types: Monday's Practice Session for exercises and Q&A, Wednesday's Coaching Session where students present their progress in small groups, and Thursday's Regular Class introducing new concepts. The teaching team consists of various roles including Session Owners who lead regular classes, Coaches who guide small groups, and Practice Session Owners who run exercise sessions. Volunteers typically commit to one role for the entire semester, investing 3-4 hours per week in direct teaching plus preparation time.
While the program is primarily conducted online via Zoom, it maintains a hybrid format with four on-site community events throughout the semester. The bootcamp is available in three locations (Berlin, NRW, and Hamburg), with local events specific to each city. Students are expected to dedicate approximately 14 hours per week to self-study in addition to attending the scheduled sessions.
Monday 19:00 - 21:00
This is a practice and Q&A session. Students can ask questions about the newly learned concepts and get support when they are stuck on the project. Furthermore, we have run exercises to practice the content.
Session Owner, Session Assist
Wednesday 19:00 - 21:00
Learners present their solutions to the weekly milestones in small groups (breakout rooms). Coaches give feedback and help the students advance.
4-5 Coaches
Thursday 19:00 - 21:00
This regular class is taught in pairs, with one person assigned as a session owner (the lecturer) and one as a teaching assistant. The class introduces the students to the new topic of the week through theory and practice.
Session Owner, Session Assist
A coach supports 4-5 students in weekly coaching sessions, providing feedback on project milestones and helping students progress. During these 2-hour sessions, students present their work and receive personalized guidance in small groups.
4 hours per week
A session owner leads the weekly regular class, introducing new concepts and guiding students through exercises using prepared materials. They have the flexibility to adapt the teaching materials to their style while ensuring all key concepts are covered.
4 hours per week
A session assistant manages the technical aspects of online classes, including Zoom setup, attendance tracking, and breakout room management. They also support students during exercises and help answer questions in the chat.
3 hours per week
A backup teacher stands ready to cover any role if a scheduled teacher is unable to attend. They don't need to attend sessions unless called upon, but should be familiar with the course content and different teaching roles.
2 hours per week
A practice session owner leads weekly sessions focused on practicing concepts from the previous class through hands-on exercises. They guide students through practice activities and answer questions about both concepts and project milestones.
4 hours per week
We are organizing on-site activities in our three main locations. Find out more below.
We invite you to four on-site community events throughout the semester if you are located in Berlin and the surrounding. The Onboarding will also take place in person in Berlin. You are more than welcome to join!
We invite you to four on-site community events throughout the semester if you are located in Berlin and surrounding. The Onboarding and Demo Day will also take place in person in Düsseldorf. You are more than welcome to join!
Four in-person sessions are taking place in Hamburg: Onboarding, two regular course sessions, and Demo Day. If you are based in Hamburg, it would be fantastic if you could support the course in one or more of these sessions.
We hope that by reading this, you have a better idea of the course and what it means to volunteer at ReDI. Let's explore the Semester Timelinenow 📅.
Our Full Stack Bootcamp is project-based - students learn by working on hands-on projects. Each project is broken into weekly milestones.
Thursday: Introduce new concepts and the next milestone
Thursday - Wednesday: Students work on their milestone
Monday: Practice session with Q&A
Wednesday: Students present their milestones in the Coaching Session
Our core teaching materials are hosted in our GitHub repository:
Lessons
In the GitHub repo, you find in every milestone folder a lesson.md
for each week. The file contains an explanation of how to approach the session, what topics to cover, and how you can introduce the concept with an example. You find the lesson.md files in the respective milestone folders in GitHub.
Teacher Guide
In the GitHub repo, you find in every milestone folder a teacher_guide.md
for each week. It contains guidelines on how to run the Practice Session on Mondays.
Student Hub
Student-facing documentation, tutorials, and concept explanations. Students use this as their main reference.
Regular Class
lesson.md -
It contains a suggested plan to structure the session. It explains which concepts to cover and how we could introduce them.
At the end of each Regular Class, we introduce the students to the next milestone (what students work on until next Wednesday). Milestone README.md
outlines the next project milestone.
Additional Resources - Previous semester materials, including slide decks and exercises
Student Hub - Further explanations and resources shared directly with students
Practice Session with Q&A
teacher_guide.md
- Guidance for practice activities and handling student questions
Coaching Session
No teaching is needed. Focused on reviewing student work and providing feedback.
Reviewing the milestoneREADME.md
t helps to understand what the milestone contains students are working on.
GitHub: You can find all files in our GitHub Repo. Do you see the lessons and teacher guides?
Additional Material: Check out prior slide decks and exercises here Course Content
Student Hub: The student hub is the "knowledge base" for the students where they find extra resources about the concepts being covered in the course. It is currently under construction. We will share it with you soon!
You are free to change the material as you like! If you believe slides are needed to explain a concept, do it! If you would explain a concept differently, go for it.
We know the material is not perfect! For sure, parts are not so clear and can be improved. Please help us to improve it further! If something is unclear or missing - feel free to add it! Thanks to your contribution, we can improve the material in the future!
We share several best practices in the Course Content section. For example, the concept of "How little is enough?" or the "I Do, We Do, You Do" methodology. In the end, it is your decision how you want to teach it. We recommend to browse through the concepts before teaching a session: Course Content.
That was a lot of content! Thanks for staying with us. Let's complete the self-onboarding in the next page: Self-Onboarding.
The material for the bootcamp is in GitHub. You can find all the material in the project folders. There is a README for every week, with a description of the concepts we introduce and the deliverables for the students.
Material
The README file in every milestone folder is for teachers to introduce the content and for students to review the material. Furthermore, it contains the "Expected Deliverables" that students are asked to complete by next Wednesday.
Teacher Guide
You can find in every milestone folder a teacher_guide.md
for each week. It contains further instructions on how to introduce the content.
Slides
If you want to use slides for teaching, you can reuse slide decks from previous semesters. However, the primary teaching resource is the material in GitHub. The slide decks are not adapted to the current content, so they might require some adaptation.
More information about the session: Regular Class.
If you are looking for more code snippets, have a look at the Berlin React GitHub Repo.
Prior Material? If you taught in the past semester at ReDI, you might have existing material you would like to reuse. That is fantastic! Please add the content to GitHub.
With the teaching team, we discussed to simplify and consolidate the material. That means, we want to have only one relevant file per milestone for the students and teachers - which is the README.
Currently, we have a README.md, a lesson.md and reference.md file per milestone. We merge them into one file (example: Milestone 1 - Project 1).
If you are the Session Owner, please consolidate the material for your session - or ask the team for support.
How we consolidate? We use the lesson.md as a baseline, and we add the learning objectives from the README at the start of the lesson, the required deliverables, and references of the README at the end of the file. If you have any questions, flag it in SLACK.
Let's improve the material together - flag mistakes, inconsistencies and improvements with issues in Github
The goal of the Practice Session on Monday is to practice the content covered in the last session. We suggest using the README.md
and teacher_guide.md
of the previous session as guidance.
More information about the session: Practice Session.
No teaching is needed. Focused on reviewing student work and providing feedback.
Reviewing the milestoneREADME.md
t helps to understand what the milestone contains students are working on.
More information about the session: Coaching Session.
If you find good material, ReDI could use, and if you have feedback or further ideas, feel free to contact us via Slack or email (dcp@redi-school.org).
The course follows a project-based learning approach. Students learn hands-on through projects the whole semester. We saw that students are more motivated to work on projects than homework and seek to apply their new skills in practical cases. Each project lasts four weeks and includes a recap week, where the previous content is recapped.
Projects are broken into manageable weekly milestones:
Students complete one part of the project each week
Each milestone applies concepts learned in Thursday's session
Progress is presented in Tuesday's coaching session
Builds toward a complete project over 4 weeks
Each week follows a structured pattern to ensure consistent learning and progress:
Monday
Practice Session with Q&A
Students practice the concepts with the teachers. They can ask questions regarding the current milestone.
Wednesday
Coaching Session
Students present their weekly milestone progress and receive feedback
Thursday
Input Session
New concepts are introduced for the next milestone
Between Sessions
Project Work
Students work independently on their milestone tasks
The Bootcamp is part of the Full Stack Track. In this Vision Board you can see how the courses are connected:
If you have any questions regarding the Learning Experience Design of the course, please contact your Course Manager.
The "I Do, We Do, You Do" method is a teaching method designed to help students learn new concepts by first observing, then practicing with guidance, and finally working independently.
I Do: The teacher explains and demonstrates a concept by explaining the steps and thought process aloud. The teacher can use live coding to show the steps. Explain why you're creating variables, choosing certain loops, or implementing specific functions. Demonstrate not only successful code but also introduce common errors and how to troubleshoot them. This helps students understand that mistakes are a normal part of the coding process and builds their debugging skills from the start.
We Do: Once students have observed your demonstration, transition to the guided practice or "We Do" phase. The teacher walks the students through an activity. You might provide partially completed code for students to finish and ask for suggestions on what comes next. The students code along. This collaborative stage allows students to apply what they've seen with support, ask questions, and receive immediate feedback.
You Do: The final phase is independent practice, or "You Do." Assign coding tasks similar to those you've demonstrated and practiced together, but allow students to work through them independently. Provide clear instructions and success criteria so students know what's expected. During this time, circulate through the classroom to offer assistance where needed, but resist the urge to take over. This is when students develop coding confidence and problem-solving abilities.
Example: Introducing Javascript
I Do: The teacher introduces JavaScript and demonstrates a simple script that shows an alert when clicking a button. Key concepts like variables, functions, and events are explained briefly.
We Do: The teacher walks the students through creating a function that changes a heading's color when clicking a button. The students follow and code along. The teacher shares their screen and gives the students time to code along. Together, the teacher and the students write the function, select the element, and add an event listener, with the teacher guiding and asking questions to engage students.
You Do: Students independently write JavaScript to change the text of a paragraph when a button is clicked in a breakout room. They practice using variables, functions, and event listeners and then share their work for feedback.
We see two ways to apply the method to a session:
You split the whole session by the method:
I Do - Introduce concepts for ~45min and try to live code them)
We Do - live code the same concepts and ask students to follow along for ~ 45min)
You Do - let students apply the concepts independently in a slightly different way for ~ 20min
You introduce every concept by the method:
Concept A (example: Intro to React) - I Do (15 min), We Do (15 min), You Do (15 min). After introducing concept A with the method, you introduce concept B once again with the method.
Concept B (example: React Components) - I Do (30 min), We Do (30 min), You Do (15 min)
Breaks Down Complexity: Coding has many rules and new concepts—seeing it done first, then trying with help, and finally doing it alone makes learning manageable.
Teaches Problem-Solving: Students learn how to approach coding problems by watching, then practicing with guidance, before solving independently.
Builds Confidence: This step-by-step method reduces frustration with coding errors and builds confidence gradually through supported practice.
Reflects Real Coding Practice: Matches how actual programmers learn—by studying examples, working with others, and then coding independently.
Start with smaller coding problems that can be completed in one session
Think about examples and exercises in advance
Connect coding concepts to everyday experiences using analogies
Show both correct solutions and common mistakes with fixes
Use color-coding to highlight syntax patterns
Incorporate visual aids and flowcharts
Celebrate debugging as learning rather than failure
Share stories of professional programmers overcoming challenges
Context before content - We experienced that explaining why a concept is important helps a lot in understanding what the concept is about. Why should you learn this concept? Try to give the context. Maybe explain where you use it in your daily work life. Or explain how this concept can help to solve a bigger problem
Engage with Students: Ask questions to check understanding. Use their names and keep the tone friendly and encouraging.
Be Prepared but Flexible: Have a plan but adapt based on student needs.
Feedback is Key: Provide constructive feedback to help students improve. Celebrate small wins to keep motivation high.
Ice Breakers and Energizers - Do you want to start the session with an energizer? Have a look at Class Engagement
The Class Demo Days are an internal presentation day held in the final week of the course. Each student presents their project in front of their classmates and teachers. It’s a supportive environment focused on:
Showcasing the project
Practicing technical presentations
Sharing challenges and lessons learned
Celebrating the team’s work
🧑🏫 This day helps students build confidence and receive feedback from peers and instructors.
The Demo Day is a public, on-site event where selected student teams present their projects to the broader ReDI community, including partners.
The event highlights excellence, creativity, and collaboration
Students present in a more formal setting with networking opportunities
It’s a moment of celebration and recognition for everyone involved
Milestone
Date
Class Demo Days
16.06.2025 18.06.2025
Demo Day
Date to be confirmed
📌 Attendance and presentation at the Class Demo Day are required for students to receive a certificate.
To help learners prepare their pitch, here’s a suggested format:
Length: Max. 5 minutes
Mode: Slides or Live Demonstration
Proposed Structure:
Intro – What’s the project, and what problem does it solve?
Demo – Show the live website
Challenges & Learning – What went well? What was hard? What did you learn?
🧑🏫 Encourage learners to rehearse and help each other practice!
To receive a ReDI certificate, learners must:
Attend at least 80% of the course
Complete and present all three Projects
Attend the Internal Class Demo Day
Complete 2 IBM SkillsBuild Courses
💬 “We grow by doing, and by helping each other.”
Foster a positive, collaborative learning
Dedicate class time to mentoring, code reviews, and feedback
Celebrate all wins—big or small—as students build real web apps
🎉 Let’s end the Bootcamp by cheering each other on!
Leads small group sessions, providing feedback on student milestone presentations
Leads regular classes, introduces new concepts and project milestones
Manages Zoom logistics and supports students during classes
Provides emergency coverage when regular teachers are unavailable
Leads practice sessions, helping students apply concepts through exercises
A coach supports 4-5 students in the Coaching session, providing feedback and guidance on project milestones. During these 2-hour sessions, students present their work and receive personalized support in small groups.
Before Session:
Review the week's project milestone and expected deliverables
Check the Students & Project Milestones tracker in the Course Sheet
During Session (2 hours):
Join Zoom 5 minutes early and claim the host
Create breakout rooms for student groups
Per student: 5 minutes presentation + 10 minutes feedback/support
Track progress in the Course Sheet
After the Session:
Complete handover in Course Sheet, "Students Progress" tab
Stay Positive: Balance constructive criticism with praise
Be Hands-on: In the 10 min feedback/support part after every presentation, we can give feedback on what to improve or use pair programming for direct code assistance.
Guide Don't Solve: Provide improvement suggestions while encouraging independent problem-solving
Students may use AI tools to support learning but must demonstrate understanding. If a student appears to rely too heavily on AI:
Ask them to explain their code's reasoning
Remind them AI should enhance, not replace, learning
Document concerns in student feedback for future coaches
Session guidelines available in Gitbook
Core Sheet for tracking progress
Coaching slides for session structure
❤️ Thank you for supporting the students' progress ❤️
As a session owner, you lead the weekly Regular Class, introducing key concepts and guiding students through exercises. We have material prepared in GitHub. We suggest using the I Do, We Do, You Do method to introduce the content. However, you can adapt the material and use your teaching style.
Review previous class feedback in Slack
Review and update material in GitHub (Course Content)
Plan how to introduce the concepts with live coding (I Do, We Do, You Do Method)
Add slides (if you use some) to Google Classroom (24h before) (how to use Google Classroom")
Join as co-host (5 min early)
Previous content recap (10 min)
Introduce key concepts with live coding and or exercises (45 min)
Hands-on practice (45 min)
Introduce next milestone (10 min)
Content: Course Content
How to Teach? I Do We Do You Do Method: Teaching Guidelines
How to Engage Students: Class Engagement Resources
As a session assistant, you provide technical and administrative support during classes. You open the Zoom call, track attendance, help answer questions, and provide support in break-out rooms.
Technical setup and support
Student attendance tracking
Question moderation
Breakout room management
Before Class:
Coordinate with the session owner
Review class content
During Class:
Join Zoom Call (link pinned in Slack and Google Calendar)
Claim the host (host key pinned in Slack)
Make the Session Owner co-host on Zoom (safety measure)
Start cloud recording
Monitor student questions
Support breakout activities
Track attendance
After Class:
Share feedback on the class and student engagement in the Slack handover bot for team visibility
All essential links (attendance tracker, Zoom) are bookmarked in Slack.
Backup teachers provide emergency coverage when teachers cannot attend class. No session attendance is required unless called upon.
Absent teacher posts in #teachers Slack channel and tags @backup teacher
Backup teacher confirms availability
Role assignment:
If assistant is absent: Backup becomes assistant
If lead is absent: Assistant becomes lead, backup becomes assistant
As Practice Session Owner, you lead a 2-hour weekly session. The goal of the Practice Session on Monday is to practice the content covered in the last session. We suggest using the README.md
and teacher_guide.md
of the previous session as guidance. The focus is on hands-on exercises and clarifying questions
Review concepts from the previous class
Prepare practice exercise
Start Zoom session (5 min early)
Claim host and start recording
Guide students through practice exercises
Address questions about concepts and milestone
Document key points covered in Slack afterward
Balance exercise time with Q&A
Use breakout rooms for group practice
Provide additional examples when needed
Head over to Course Content
❤️ Thank you for helping the students progress ❤️
The Project Reviewer reviews the project submissions of the students.
Project are reviewed from Google Classroom. Students submissions land under the "Grades" section. Just click on the submission link and add comments for review via the chat function. Everything be kept private and only visible to the reviewer and the students themselves.
Why to work in projects?
💡Learning by Doing - The best way to learn about a concept is by applying and trying it out yourself. Let’s help the students to fully understand the concepts by actively working on them.🚀 Grow through Practice - Through projects students practicing, coding, crafting and revising the material. The more they practice, the better the students get! Let’s help them grow. ❓Get Feedback - Students try out the concepts in milestones. In the project submissions, teachers might get a better understand which concepts need further elaboration. Project Submission & Feedback Process
Assign the project submission in Google Classroom, including a specific date and time.
Review the submitted project and provide constructive feedback.
Positivity - It can happen easily that feedback only points out the mistakes, but it’s important to give positive feedback as well. Commenting on aspects that you liked about the code is crucial to make the students more confident. We also learn from what we did well.
Specific - Try to make your feedback as specific as possible, so the students know which part of the code or result needs improvement.
Suggestions - Good feedback contains suggestions for improvement. This way, the students will have ideas on how to improve the code, and you will push them in the right direction. Keep in mind the balance between suggestions and self-study; giving away the solution is not always the best thing to do.
Students practice concepts from the previous class and get answers to their questions about projects and course content.
When: Mondays, 19:00 - 21:00
Where: Zoom (link in Slack)
Format: Guided practice and Q&A
Team: Practice Session Owner leads session, Session Assist supports.
Practice exercises on recent concepts
Address questions
Project support as needed
Practice Session Owner: Leads exercises and answers questions
Students: Participate in practice and ask questions
This VIDEO explains the Session Formats.
Students present their weekly milestone solutions in small groups (4-5 students), receiving feedback and support from coaches.
When: Wednesdays, 19:00 - 21:00
Where: Zoom (link in Slack)
Format: Breakout rooms with one coach per group
Who: The Coaches run the Coaching Sessions. Read the instructions for the Coach.
Welcome and breakout room setup
Student presentations (15 minutes each)
Break halfway through
Remaining presentations
Extra time for additional support if needed
5 minutes: Project presentation
10 minutes: Feedback and support
For the last session of each project, students present their complete project instead of weekly milestones.
This VIDEO explains the Session Formats.
Weekly class where students learn new concepts and get introduced to their next project milestone.
When: Thursdays, 19:00 - 21:00
Where: Zoom (link in Slack)
Team: Session Owner leads the session and Session Assist supports
Review previous content
Introduce weekly milestone
Present new concepts
Guided practice ("We Do")
Group practice in breakout rooms ("You Do")
This VIDEO explains the Session Formats.
Are you new to this course: Course Overview
Start your Onboarding: Get Started
Monday 19:00 - 21:00
Project Session
We meet for two weekly online sessions to support the students work step-by-step on the project. Agenda: General standups, updates in main room, then breakout rooms
Guides
Wednesday 19:00 - 21:00
Project Session
Agenda: General standups, updates in main room, then breakout rooms
Guides
As a guide, you find ways to support learners at best. You drive students through the project and strategise with the other teammates to diagnose any issues.
Find out more about ReDI: About ReDI
Find out about the career services ReDI offers: Career Services
Check out: I can't teach tonight, I am dropping out, I feel uncomfortable.
Reach out to Caro, your Course Manager, for help via Slack.
❤️ Thank you for supporting the ReDI students ❤️
Welcome to ReDI School! We really appreciate that you are part of our community. In this page, you'll find an overview of the course. By volunteering, you contribute to our main goal: help our students gain the necessary skills to find a job in tech. ReDI School has now helped over 17.000 people advance their tech skills. This is only possible with the support of our volunteers <3
Our student community brings together people from over 138 countries. Your course won't be different. Your students will come from a wide range of countries. They also come from diverse professional backgrounds - some are currently unemployed or underemployed, while others are students looking to prepare for their careers. With an average age of 32, many of our students hold a university degree and have several years of work experience. What unites all students is their passion for technology and their aim to build a career in the tech industry.
❤️ Thank you for supporting our students as they take another step in their journey! To learn more about ReDI students and our community, visit About ReDI School.
The Full Stack Circle is a 14-week advanced program designed for students with solid HTML, CSS, JavaScript, and basic React skills who want to gain development experience by working on team-based projects. Each cohort consists of 25 students who collaborate in small teams to build a full-stack application, simulating a professional software development environment.
Primary goal: Employability through hands-on experience
Focus on real-world project work rather than traditional lectures
Emphasis on production-quality code and team experience
Encourages self-learning and independent problem-solving
One main project for the entire semester
The class operates like a development team
Students are divided into feature teams
3-week sprint cycles
Gradual transition from teacher-led to student-led project organization
Soft Skills: Teamwork, Task management, Project communication, Self-learning
Technical Skills: React, Frontend/Backend development, Testing, Git, Clean code practices, Debugging, Documentation
The students choose at the beginning of the semester a platform they like to clone. The previous project was an AirBnb Clone.
Weeks 1 - 3: Tools configuration, development environment setup, project management process overview
Remaining weeks: Split into 3-week sprints. Each sprint contains a focus topic according to the project type that needs to be completed. Milestones will break down the project into smaller deliverables. Expect weekly homework (project work) during this period.
Demo Day: At the end of the semester, each team will present their projects to the audience of ReDI course community members.
Sprint Kickoff
Day 1
Sprint Planning, Refinement, Work Time
Sprint
Weeks 1-3
Standups, Work Time, Optional Lessons
Sprint Conclusion
Week 3 Day 2
Demo, Retrospective, Next Sprint Brainstorming
The course has two online sessions per week. For on-site events, check out On-site Activities. The session format differs from what you might have seen before.
Tuesday 19:00 - 21:00
We meet for two weekly online sessions to support the students work step-by-step on the project. Agenda: General stand ups, updates in main room, then breakout rooms
Thursday 19:00 - 21:00
Agenda: General stand ups, updates in main room, then breakout rooms
The volunteers (guides) take on the head of basically two roles:
Product Manager: Runs meetings (standups, planning, refinement), Prepares and prioritizes tasks
Mentor: Performs code reviews, Provides one-on-one guidance, Answers student questions
As a guide, you are both a PM and a Mentor within the sessions :)
We are organizing on-site activities in our three main locations. Find out more below.
We invite you to four on-site community events throughout the semester if you are located in Berlin and the surrounding. The Onboarding will also take place in person in Berlin. You are more than welcome to join!
We invite you to four on-site community events throughout the semester if you are located in Berlin and surrounding. The Onboarding and Demo Day will also take place in person in Düsseldorf. You are more than welcome to join!
Four in-person sessions are taking place in Hamburg: Onboarding, two regular course sessions, and Demo Day. If you are based in Hamburg, it would be fantastic if you could support the course in one or more of these sessions.
We hope that by reading this, you have a better idea of the course and what it means to volunteer at ReDI. Let's explore the Timeline now 📅.
The Full Stack Circle focuses entirely on working on a project. That also means there is little content being shared with the students. The first three sessions help introduce students to concepts (how to collaborate, team building, and setup). Besides that, we share material ad-hoc if needed to solve a specific issue.
Students can choose which platform or website to clone. This approach allows teams to work on a project they're genuinely interested in while learning essential full-stack development skills. Last semester, the students cloned Airbnb (GitHub Repo).
A project with a frontend communicating with a backend connected to a data store, transmitting data back and forth and modifying data on the backend
The project represents an understanding of testing, debugging and clean code principles
One meaningful visual test and one meaningful behavior/unit test set
One meaningful complexity level apart from a plain backend/frontend communication (ex.: maps, complex auth, 3rd party API integration, realtime comms)
Log of tickets/cards/milestones in the project
Once a platform is selected (in the first 3 weeks), we define the initial set of tickets and establish the project structure, ensuring a solid foundation for development (a volunteer PM named Stefan helps us with this!). The project will be broken down into manageable sprints, each focusing on recreating specific features of the chosen platform.
Let's complete the self-onboarding now: Complete your Self-Onboarding
The Full Stack Circle focuses entirely on working on a project. That also means there is little content being shared with the students. The first three sessions help introduce students to concepts (how to collaborate, team building, and setup). Besides that, we share material ad-hoc if needed to solve a specific issue.
Students can choose which platform or website to clone. This approach allows teams to work on a project they're genuinely interested in while learning essential full-stack development skills. Last semester, the students cloned Airbnb (GitHub Repo).
A project with a frontend communicating with a backend connected to a data store, transmitting data back and forth and modifying data on the backend
The project represents an understanding of testing, debugging and clean code principles
One meaningful visual test and one meaningful behavior/unit test set
One meaningful complexity level apart from a plain backend/frontend communication (ex.: maps, complex auth, 3rd party API integration, realtime comms)
Log of tickets/cards/milestones in the project
Once a platform is selected (in the first 3 weeks), we define the initial set of tickets and establish the project structure, ensuring a solid foundation for development (a volunteer PM named Stefan helps us with this!). The project will be broken down into manageable sprints, each focusing on recreating specific features of the chosen platform.
If you find good material, ReDI could use, and if you have feedback or further ideas, feel free to contact Julian via Slack or email (julian@redi-school.org).
Here is a list of topics of subjects we think are important to try and hit for the continued education as well as employability of our students. When we’re doing sprint brainstormings and plannings, or any changes to the course itself, we should keep these goals in mind and push for things that accomplish them. Skills we want our learners to achieve:
Teamwork
Task management
Task specification
Feature specification as a stretch goal
Project management negotiation
Proactive communication (speaking their mind/don't be afraid to ask)
Self-learning (Career descriptors & expectations as a stretch goal)
React
Client/server comms
Reusable components
Dataflow
Complex data manipulation (useReducer, redux)
Storage options on client
Session
Cookies
indexedDB
axios/fetch
Node.js / express
REST APIs
Mentioning different js runtimes
SQLite NoSQL
Web frontend
Implementing common and consistent design
Important UI/UX concepts
Responsive Design
Testing
Manual
Automated (Unit + UI)
Tooling
Vscode extensions
Package managers/registries (how to deal with unforeseen circumstances?)
Git merging
Debugging
Clean code
DRY
Naming & conventions (code, docs)
Documentation (README.md, Changelogs)
A project with a frontend communicating with a backend connected to a data store, transmitting data back and forth and modifying data on the backend
The project represents an understanding of testing, debugging and clean code principles
One meaningful visual test and one meaningful behavior/unit test set
One meaningful complexity level apart from a plain backend/frontend communication (ex.: maps, complex auth, 3rd party API integration, realtime comms)
Log of tickets/cards/milestones in the project
We provide additional tools that you can use to engage students more in your sessions! At ReDI, we like to use the following tools and icebreakers:
Create live polls, word clouds, and Q&A
Perfect for:
Icebreakers: Ask students about their expectations or background knowledge.
Quick polls: Check understanding of a topic in real-time.
Exit tickets: Gather feedback at the end of a session.
Login credentials in teachers' Slack channel
Quiz-based learning with competitive elements
Perfect for Revision & Recaps - You create a quiz, and students participate live in class via browser or cell phone.
Login credentials in teachers' Slack channel
You can use quick icebreakers at the start of your sessions to energize participants, build connections, and create an engaging and interactive learning environment. Here is a list of icebreakers. They shouldn't take more than 5 minutes to run.
Description: Participants share three statements about themselves—two true and one false. The group has to guess which one is the lie.
How to Run: Use breakout rooms for smaller groups or let everyone participate in the main room.
Objective: Participants get to know each other in a fun way.
Description: Give participants a list of items to find in their home within 1-2 minutes (e.g., something red, something that makes noise).
How to Run: Ask them to bring the items back to the camera and share a quick story about one of them.
Objective: The activity is an energizer.
Description: Pose a question or statement (e.g., "How are you feeling about today’s session?") and ask participants to respond using emojis only.
How to Run: Use the chat in Zoom.
Objective: It is an easy way for participants to share how they are doing.
The "I Do, We Do, You Do" method is a teaching method designed to help students learn new concepts by first observing, then practicing with guidance, and finally working independently.
I Do: The teacher demonstrates the task while explaining the steps and thought process aloud. This stage is about modeling the correct way to approach the task and highlighting key concepts and techniques.
We Do: The session owner walks the students through an activity. The students follow along (code or design along). This collaborative stage allows students to apply what they've seen with support, ask questions, and receive immediate feedback.
You Do: Students work independently on the task. This stage allows them to practice the skill on their own.
Example: Introducing Javascript
I Do: The teacher introduces JavaScript and demonstrates a simple script that shows an alert when clicking a button. Key concepts like variables, functions, and events are explained briefly.
We Do: The teacher walks the students through creating a function that changes a heading's color when clicking a button. The students follow and code along. The teacher shares their screen and gives the students time to code along. Together, the teacher and the students write the function, select the element, and add an event listener, with the teacher guiding and asking questions to engage students.
You Do: Students independently write JavaScript to change the text of a paragraph when a button is clicked in a breakout room. They practice using variables, functions, and event listeners and then share their work for feedback.
Context before content - We experienced that explaining why a concept is important helps a lot in understanding what the concept is about. Why should you learn this concept? Try to give the context. Maybe explain where you use it in your daily work life. Or explain how this concept can help to solve a bigger problem
Engage with Students: Ask questions to check understanding. Use their names and keep the tone friendly and encouraging.
Be Prepared but Flexible: Have a plan but adapt based on student needs.
Feedback is Key: Provide constructive feedback to help students improve. Celebrate small wins to keep motivation high.
Watch this video on how to run the Regular Class.
Ice Breakers and Energizers - Do you want to start the session with an energizer? Have a look at Class Engagement
The Class Demo Day is an internal presentation day held in the final week of the course. Each student (team) presents their project to their classmates and teachers. It’s a supportive environment focused on:
Showcasing the project
Practicing technical presentations
Sharing challenges and lessons learned
Celebrating the team’s work
🧑🏫 This day helps students build confidence and receive feedback from peers and instructors.
The Demo Day is a public, on-site event where selected student teams present their projects to the broader ReDI community, including partners.
The event highlights excellence, creativity, and collaboration
Students present in a more formal setting with networking opportunities
It’s a moment of celebration and recognition for everyone involved
Milestone
Date
Class Demo Day
17.06.2025
Demo Day
Date to be confirmed
📌 Attendance and presentation at the Class Demo Day are required for students to receive a certificate.
To help learners prepare their pitch, here’s a suggested format:
Length: Max. 5 minutes
Mode: Slides or Live Demonstration
Proposed Structure:
Intro – What’s the project, and what problem does it solve?
Demo – Show the live website
Challenges & Learning – What went well? What was hard? What did you learn?
🧑🏫 Encourage learners to rehearse and help each other practice!
To receive a ReDI certificate, learners must:
Attend at least 80% of the course
Complete and present the Project
Attend the Internal Class Demo Day
Complete 2 IBM SkillsBuild Courses
💬 “We grow by doing, and by helping each other.”
Foster a positive, collaborative learning
Dedicate class time to mentoring, code reviews, and feedback
Celebrate all wins—big or small—as students build real web apps
🎉 Let’s end the Circle by cheering each other on!
In the Full Stack Circle, guides support students in building real-world projects. Rather than traditional teaching, guides help students develop practical skills through hands-on project work and agile development practices.
As a guide, you basically have two roles in one :) You support the students as a product manager and as a mentor in the sessions.
Runs team meetings (standups, planning, refinement)
Prepares and prioritizes tasks for sprints
Conducts code reviews
Provides one-on-one support during work sessions
Helps students discover solutions independently
Identifies areas where students may need additional support
Standup meetings (15 minutes)
Work time with active mentoring
Optional micro-lectures as needed
Team-based project work
Sprint planning and kickoff
Regular refinement sessions
Demo presentations
Retrospectives
Allocate a responsible to track attendance
Facilitate team meetings
Provide hands-on guidance
Review code and give feedback
Support student collaboration
Answer questions via Slack
Review pull requests
Prepare for upcoming sprints
Share relevant resources
Encourage self-learning
Guide rather than provide direct solutions
Foster team collaboration
Maintain consistent communication
Help break down tasks into manageable pieces
Ensure clear acceptance criteria
Monitor progress and address blockers
Facilitate effective team discussions
Team communication via Slack
Additional support from ReDI React teachers when needed
Weeks 1 - 3: Tools configuration, development environment setup, project management process overview
Remaining weeks: Split into 3-week sprints. Each sprint contains a focus topic according to the project type that needs to be completed. Milestones will break down the project into smaller deliverables. Expect weekly homework (project work) during this period.
Demo Day: At the end of the semester, each team will present their projects to the audience of ReDI course community members.
Tuesday 19:00 - 21:00
Project Session
We meet for two weekly online sessions to support the students work step-by-step on the project. Agenda: General stand ups, updates in main room, then breakout rooms
Thursday 19:00 - 21:00
Project Session
Agenda: General stand ups, updates in main room, then breakout rooms
Sprint Kickoff
Day 1
Sprint Planning, Refinement, Work Time
Sprint
Weeks 1-3
Standups, Work Time, Optional Lessons
Sprint Conclusion
Week 3 Day 2
Demo, Retrospective, Next Sprint Brainstorming