Activity 01
Role Play: Technical Interview Simulation
Partners take turns presenting their capstone project for five minutes while the other plays a skeptical interviewer who must ask at least two clarifying questions about design choices or trade-offs. Presenters may not answer with 'I don't know'; they must reason through an answer or acknowledge the limitation explicitly.
Present the functionality and design choices of a developed software project.
Facilitation TipDuring the Technical Interview Simulation, assign roles like interviewer, interviewee, and peer observer to maximize participation and accountability.
What to look forDuring presentations, provide students with a rubric that includes sections for 'Clarity of Demonstration,' 'Explanation of Design Choices,' and 'Reflection on Challenges.' After each presentation, peers use the rubric to provide specific, actionable feedback, noting one strength and one area for improvement for each section.
ApplyAnalyzeEvaluateSocial AwarenessSelf-Awareness
Generate Complete Lesson→· · ·
Activity 02
Think-Pair-Share: Challenge and Solution Mapping
Students individually write down their three biggest obstacles during the project and how they addressed each. Partners compare lists to identify shared challenges and divergent solutions, then each pair shares one insight with the class, building a collective picture of the capstone experience.
Analyze the challenges encountered and solutions implemented during the project.
Facilitation TipDuring Challenge and Solution Mapping, provide sentence stems such as 'The hardest part was... because...' to scaffold student reflection.
What to look forAfter all presentations, facilitate a whole-class discussion using prompts such as: 'What was the most common challenge faced by multiple teams, and how did different teams approach it differently?' or 'Which design decision presented by another team do you think was particularly innovative, and why?'
UnderstandApplyAnalyzeSelf-AwarenessRelationship Skills
Generate Complete Lesson→· · ·
Activity 03
Gallery Walk: Demo Day Circuit
Projects are set up as stations around the room. Visitors and peers rotate through on a timer with a structured feedback form covering functionality (does it work as described?), design clarity (is the interface or architecture understandable?), and presentation quality (did the presenter communicate the key decisions?). Each student collects written feedback from at least four reviewers.
Evaluate personal and team growth throughout the software development lifecycle.
Facilitation TipDuring the Demo Day Circuit, place feedback stations with labeled sections for strengths and next steps to guide peer assessment.
What to look forAsk students to write on an index card: 'One specific technical challenge I overcame was ___, and the solution I implemented was ___. One thing I learned about my own development process is ___.'
UnderstandApplyAnalyzeCreateRelationship SkillsSocial Awareness
Generate Complete Lesson→· · ·
Activity 04
Structured Academic Controversy: Best vs. Most Important Feature
Each student identifies one feature they are most technically proud of and one they consider most important to users. Pairs argue for different evaluation criteria (technical achievement vs. user value), switch positions, then synthesize a shared definition of what makes a software feature worth highlighting in a presentation.
Present the functionality and design choices of a developed software project.
What to look forDuring presentations, provide students with a rubric that includes sections for 'Clarity of Demonstration,' 'Explanation of Design Choices,' and 'Reflection on Challenges.' After each presentation, peers use the rubric to provide specific, actionable feedback, noting one strength and one area for improvement for each section.
AnalyzeEvaluateCreateSocial AwarenessRelationship Skills
Generate Complete Lesson→A few notes on teaching this unit
Experienced teachers approach this topic by modeling professional communication first. They use structured peer feedback to reduce anxiety and normalize iterative improvement. They also emphasize that reflection is not just retrospective but prospective, helping students plan for future projects. Research suggests that students improve fastest when feedback is specific, timely, and tied to clear criteria rather than vague praise.
Students will leave with the ability to explain their software’s purpose, justify design choices with evidence, and reflect on their development process in ways that are useful to others. They will be able to give and receive constructive feedback that improves both technical and communication skills.
Watch Out for These Misconceptions
During a Technical Interview Simulation, students may assume that a successful demo is enough to impress the interviewer.
Remind students during the simulation that interviewers expect explanations of design choices, trade-offs, and lessons learned, not just a working demo. Use a sample rubric to show what strong responses look like.
During Challenge and Solution Mapping, students may think reflection means only listing mistakes.
During the activity, direct students to evaluate both successes and challenges. Provide sentence frames like ‘What worked well was... because...’ to guide balanced reflection.
During the Demo Day Circuit, students may treat the presentation as just a formality for the grade.
Use the event to emphasize that this is practice for real-world communication. Share examples of how engineers explain their work in code reviews and interviews, and ask students to connect their own work to those contexts.
Methods used in this brief